Fedora: Difference between revisions

Line 210:

keyring stores the passwords encrypted with the according keyring-password, and automatic unlocking works by getting the password through pam on login through gdm and then use it to unencrypt the passwords - and that can only work if your login-password is the same as the keyring-password

why doesn't gnome 3 display "interactive dialogs" when applications ask for input

yes, also from gnome 3

when you run the shell script from nautilus, it doesn't display a dialog

"Enter passphrase for ..."

you can use zenity for that

try moving /usr/share/gdm/autostart/LoginWindow/gnome-session-check-accelerated.desktop somewhere else

didn't know you needed anything additional for that.. was it always like that or did gnome 2 have that by default?

maybe thats the seahorse/keyring integration, that stuff has changed quite a bit in 3.0

but i thought you meant a more generic approach of showing dialogs from scripts

i'm actually doing the ssh-add from a process spawned by a pygtk app

if it is only this specific case, you should probably still use keyring/seahorse (whatever should do that now) as it would not be passing around passwords unencrypted between processes (at least afaik)

worked!

do you somehow run gdm with a different driver or some weird setup like that?

so it's not possible to get the old behavior, and it needs some additional code to get it to work with seahorse/keyring?

which distro is this?

fedora 15 beta

i've tested the same code on fedora 14 and linuxmint (both gnome 2)

when the ssh-add {key_path} process is spawned, the GUI dialog appears asking you to type in your passphrase

ssh-add succeeds, and them the rest of the pygtk app continues

it doesn't even care whether the key is password protected or anything

i think there needs a daemon to be running that doesn't get started by fedora

this happens both in standard and fallback mode

try launching seahorse-daemon

====Install VirtualBox_fedora14 to f15 gnome3-shell====

@@ Line 210: / Line 210: @@
   keyring stores the passwords encrypted with the according keyring-password, and automatic unlocking works by getting the password through pam on login through gdm and then use  it to unencrypt the passwords - and that can only work if your login-password is the same as the keyring-password
+ why doesn't gnome 3 display "interactive dialogs" when applications ask for input
+ yes, also from gnome 3
+ when you run the shell script from nautilus, it doesn't display a dialog
+ "Enter passphrase for ..."
+ you can use zenity for that
+ try moving /usr/share/gdm/autostart/LoginWindow/gnome-session-check-accelerated.desktop somewhere else
+ didn't know you needed anything additional for that.. was it always like that or did gnome 2 have that by default?
+ maybe thats the seahorse/keyring integration, that stuff has changed quite a bit in 3.0
+ but i thought you meant a more generic approach of showing dialogs from scripts
+ i'm actually doing the ssh-add from a process spawned by a pygtk app
+ if it is only this specific case, you should probably still use keyring/seahorse (whatever should do that now) as it would not be passing around passwords unencrypted between processes (at least afaik)
+ worked!
+ do you somehow run gdm with a different driver or some weird setup like that?
+ so it's not possible to get the old behavior, and it needs some additional code to get it to work with seahorse/keyring?
+ which distro is this?
+ fedora 15 beta
+ i've tested the same code on fedora 14 and linuxmint (both gnome 2)
+ when the ssh-add {key_path} process is spawned, the GUI dialog appears asking you to type in your passphrase
+ ssh-add succeeds, and them the rest of the pygtk app continues
+ it doesn't even care whether the key is password protected or anything
+ i think there needs a daemon to be running that doesn't get started by fedora
+ this happens both in standard and fallback mode
+ try launching seahorse-daemon
 ====Install VirtualBox_fedora14 to f15 gnome3-shell====