Re: gnome-keyring vs. nodm

It turns out that one must indeed do the seahorse steps as mentioned above, as there is no known batch job method. The result is an unencrypted ~/.../keyrings/Default_keyring.keyring file. OK thanks everybody. ___ gnome-keyring-list mailing list

Re: gnome-keyring vs. nodm

I suppose I must reverse engineer the seahorse actions to see what it does. 0) Take a snapshot of my home directory. 1) install seahorse. 2) Do the changes mentioned earlier. 3) do find -mmin -5 to see what changed. 4) compare the changes with my snapshot.

Re: gnome-keyring vs. nodm

> "WZ" == Weiwu Zhang writes: WZ> Synchronising data across multiple seahorse installations That is not what I am trying to do! I am just talking about doing what I want to do on one isolated machine. Then doing the same thing on another isolated machine, and

Re: gnome-keyring vs. nodm

> "NHW" == Neal H Walfield writes: NHW> You can use seahorse to set the password to be the empty string. NHW> (Start seahorse, right click on the login keyring, and choose change NHW> password.) Then GNOME Keyring won't prompt you for a passphrase. Thanks but I want to

Re: gnome-keyring vs. nodm

On Sun, 06 Aug 2017 04:38:10 +0200, 積丹尼 Dan Jacobson wrote: > > I use nodm. > nodm never asks for a password, hence autologin for gnome-keyring is > impossible. > > I wish instead to put > echo mypassword|something > into my .xsession file. > > Please advise on what will work. You can use

gnome-keyring vs. nodm

I use nodm. nodm never asks for a password, hence autologin for gnome-keyring is impossible. I wish instead to put echo mypassword|something into my .xsession file. Please advise on what will work. Related discussion: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869399