Re: [gcmd-dev] [NEW] Use of GNOME authentication manager for user's security credentials

[Piotr Eljasiak]

> Oct 28 14:05:26 gandalf gnome-keyring-daemon[18188]: couldn't read 4 bytes 
> from client:
> 
> gkd:
> read(6, 0x7fff2103304f, 1)              = -1 EAGAIN (Resource temporarily 
> unavailable)
> 
> 
> 
> this is what valgrind reports for gnome-commander:
> 
> 
> ==18505== Thread 1:
> ==18505== Syscall param write(buf) points to uninitialised byte(s)
> ==18505==    at 0xA0D0E7B: (within /lib/libpthread-2.6.1.so)
> ==18505==    by 0x844ED7E: (within /usr/lib/libX11.so.6.2.0)
> ==18505==    by 0x8453A5E: (within /usr/lib/libX11.so.6.2.0)
> ==18505==    by 0x84549C9: _XEventsQueued (in /usr/lib/libX11.so.6.2.0)
> ==18505==    by 0x84412DC: XPending (in /usr/lib/libX11.so.6.2.0)
> ==18505==    by 0x6746EAE: (within /usr/lib/libgdk-x11-2.0.so.0.1200.1)
> ==18505==    by 0x67472ED: (within /usr/lib/libgdk-x11-2.0.so.0.1200.1)

(sigh...)



Ok, the right approach then is to allow user to decide him(her)self. The
last rev (#1257) adds the new tab 'Network' to Options dlg, where it's
possible to switch off the usage of GNOME auth daemon. The default value
is to USE g.k.d.

Additionally I've added the widget for anonymous ftp password, as it
seems right to me to be here.


What's left to be done?

1. Some code tweaking in 'Remote servers' dlg to handle g.k.d &
non-g.k.d connections (presentation + not allowing g.k.d connection when
not using GNOME auth daemon)
2. Complete redesign of 'Edit remote connection' dlg, some parts of that
are already done (see attached screenshot).


More news to come soon,
Piotr

Remote Server.png
Description: PNG image