public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andrey Repin <anrdaemon@yandex.ru>
To: Chris Rodgers <ctr28@cam.ac.uk>, cygwin@cygwin.com
Subject: Re: ssh-pageant
Date: Thu, 23 Apr 2020 23:51:19 +0300	[thread overview]
Message-ID: <150670600.20200423235119@yandex.ru> (raw)
In-Reply-To: <d165e827-49ac-e2c6-908c-b58d88c5395e@cam.ac.uk>

Greetings, Chris Rodgers!

> Thanks for the detailed reply. Interesting!

>> It's not that simple. You can't blindly restart agent every time you wish
>> without notifying other programs, `--reuse` is a very bad idea and there's
>> no easy way to set/change an environment variable globally for an entire
>> user session.

> May I ask, why do you say "--reuse" is a very bad idea? I'd be 
> interested to know in general, not just when considering this change.

With --reuse you're using predictable name, and not checking its permissions.
You can never know if that socket was actually created by you or left there by
accident. If you noticed, I trash both socket and agent configuration before
activating the agent anew. That gives me a little more control on what's going
on in the system.


-- 
With best regards,
Andrey Repin
Thursday, April 23, 2020 23:46:25

Sorry for my terrible english...


      reply	other threads:[~2020-04-23 21:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-23 13:50 ssh-pageant Chris Rodgers
2020-04-23 14:11 ` ssh-pageant Thomas Wolff
2020-04-23 18:31   ` ssh-pageant Andrey Repin
2020-04-23 18:59     ` ssh-pageant Thomas Wolff
2020-04-23 20:27       ` ssh-pageant Bill Stewart
2020-04-23 16:40 ` ssh-pageant Chris Rodgers
2020-04-23 16:47   ` ssh-pageant Chris Rodgers
2020-04-23 19:44     ` ssh-pageant Chris Rodgers
2020-04-23 18:33 ` ssh-pageant Brian Inglis
2020-04-23 20:02 ` ssh-pageant Andrey Repin
2020-04-23 20:20   ` ssh-pageant Chris Rodgers
2020-04-23 20:51     ` Andrey Repin [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=150670600.20200423235119@yandex.ru \
    --to=anrdaemon@yandex.ru \
    --cc=ctr28@cam.ac.uk \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).