Re: [qubes-users] ssh keys gui not working / password no longer stored (deb8)

2016-12-17 Thread raahelps
On Tuesday, December 13, 2016 at 9:35:40 PM UTC-5, Marek Marczykowski-Górecki 
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> On Tue, Dec 13, 2016 at 12:11:43AM +, Unman wrote:
> > On Mon, Dec 12, 2016 at 11:53:25PM +0100, cubit wrote:
> > > Heia
> > > 
> > > Since using Qubes (debian 8 template) back to R3.1 when ever I used ssh I 
> > > would get a gui prompt asking for my key password and it would be 
> > > remembered for all subsequent ssh sessions until I restart the AppVM.
> > > 
> > > With a recent template update this has broken, now what happens is in the 
> > > terminal window I am asked for the keys password but the password is no 
> > > longer stored and I must retype for every new session.
> > > 
> > > Is there an easy way to get the gui / password managed option back?
> > > 
> > > Cubit
> > > 
> > >
> > 
> > Debian uses ssh-agent by default. Just use ssh-add to store the key
> > before opening the ssh session.
> 
> For the record, this was intended change, reasoning here:
> https://github.com/QubesOS/qubes-issues/issues/2351
> And this discussion:
> https://groups.google.com/d/msgid/qubes-devel/2016110829.GS22572%40mail-itl
> 
> If you want to restore old behaviour, add to your ~/.profile in
> appropriate AppVM:
> 
> eval `gnome-keyring-daemon -c ssh`
> export SSH_AUTH_SOCK
> 
> - -- 
> Best Regards,
> Marek Marczykowski-Górecki
> Invisible Things Lab
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2
> 
> iQEcBAEBCAAGBQJYUK/4AAoJENuP0xzK19csGGIH/0zsGswJ1Xa4uiJ25wyrvHcw
> TBCiOgJAiune4+o89p5A2WuaDstoIK9B91QfNxGRip3V8yoDFKKPExMSdAip6sVI
> +4HHJZOMJjPdvRNSgVYfIAsjbqcMlApDEeWbQzuFc5S0pzKYYyFUnKxngfygg1sg
> 4Lr4xFQ1XK/z2nlAJTzCD+YSCcdnx+YQixHpT0NGDteY591UWqc5QHtAVr9OGRcp
> x2ZqJzcs+A8t4/nh9rgMZe+LO1iIIXcC4bV79LS2VvK/kmLX1PFtomPwpMbBJovF
> gS84AJFUP4wNNh+K2iD/a8R02XaLe/gwGKYWY9wYO5UoZINhgqjKq7oIGg6I9Q0=
> =zPOt
> -END PGP SIGNATURE-

I noticed this change too.   I never stored the password.  but I stopped 
getting the popup bubble to enter it past couple weeks.  glad to know it wasn't 
just me lol. no big deal though.  I'm sure forcing me to use terminal is more 
secure.  I was thinking that all along anyways.

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/d45e9279-5f22-4322-8fe4-7c3c7c097a09%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] ssh keys gui not working / password no longer stored (deb8)

2016-12-12 Thread Unman
On Mon, Dec 12, 2016 at 11:53:25PM +0100, cubit wrote:
> Heia
> 
> Since using Qubes (debian 8 template) back to R3.1 when ever I used ssh I 
> would get a gui prompt asking for my key password and it would be remembered 
> for all subsequent ssh sessions until I restart the AppVM.
> 
> With a recent template update this has broken, now what happens is in the 
> terminal window I am asked for the keys password but the password is no 
> longer stored and I must retype for every new session.
> 
> Is there an easy way to get the gui / password managed option back?
> 
> Cubit
> 
>

Debian uses ssh-agent by default. Just use ssh-add to store the key
before opening the ssh session.


-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/20161213001143.GA27064%40thirdeyesecurity.org.
For more options, visit https://groups.google.com/d/optout.