Re: ssh-agent no longer being started

2017-11-07 Thread René J . V . Bertin
On Tuesday November 07 2017 12:17:25 Mihai Moldovan wrote: > The former gpg-agent port installed a LaunchAgent, which started gpg-agent via > launchd on user login. Not quite on-demand. Let's put it this way: I didn't notice any loss of functionality after unloading that plist (stopping the runn

Re: ssh-agent no longer being started

2017-11-07 Thread Mihai Moldovan
On 11/06/2017 04:29 PM, René J.V. Bertin wrote: > Ah, thanks. I was already looking into what other ports I had to upgrade to > do this. > > I have the impression that gnupg2 2.0.30 already launched the agent > on-demand, at least I didn't notice any loss of functionality after unloading > the

Re: ssh-agent no longer being started

2017-11-06 Thread René J . V . Bertin
On Monday November 06 2017 15:54:04 Rainer Müller wrote: > The gpg-agent port used to provide this LaunchAgent, but it was recently > marked as obsolete and replaced by gnupg2 [1]. Just uninstall the > gpg-agent port and switch to gnupg2. gpg-agent will now be launched > on-demand by gpg itself.

Re: ssh-agent no longer being started

2017-11-06 Thread Rainer Müller
On 2017-11-05 23:44, René J.V. Bertin wrote: > I do have a SSH_AUTH_SOCK var in the launchctl env, but it points to a socket > that's used only by launchd itself and by gpg-agent . I see that gpg-agent is > started from > ${prefix}/etc/LaunchAgents/org.macports.gpg-agent/org.macports.gpg-agent.p

Re: ssh-agent no longer being started

2017-11-06 Thread René J . V . Bertin
On Sunday November 05 2017 19:19:55 Kastus Shchuka wrote: >The Listeners key in ssh-agent plist creates a randomly named socket and >exports in SSH_AUTH_SOCK to the user’s shell. It should not be shared with >gpg-agent to the best of my knowledge. gpg-agent is definitely involved though. Its pl

Re: ssh-agent no longer being started

2017-11-05 Thread Kastus Shchuka
> On Nov 5, 2017, at 2:44 PM, René J.V. Bertin wrote: > > Hi, > > I've grown accustomed to be able to call `ssh-add -A` periodically to import > all certificates stored in my keychain into a running ssh-agent instance that > I didn't have to start. After a forced reboot last Friday (the syste

ssh-agent no longer being started

2017-11-05 Thread René J . V . Bertin
Hi, I've grown accustomed to be able to call `ssh-add -A` periodically to import all certificates stored in my keychain into a running ssh-agent instance that I didn't have to start. After a forced reboot last Friday (the system had been up for 94 days) I find that ssh-agent no longer starts.