public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: ssh-pageant
Date: Thu, 23 Apr 2020 12:33:35 -0600	[thread overview]
Message-ID: <c3fd2c28-7f9a-9611-c595-5be88b508d7c@SystematicSw.ab.ca> (raw)
In-Reply-To: <5f24168f-61d7-848b-677d-bf0d5aea303a@cam.ac.uk>

On 2020-04-23 07:50, Chris Rodgers wrote:
> I find the ssh-pageant package helpful to enable cygwin ssh to interact
> seamlessly with PuTTY's Pageant SSH agent. One small issue is that after
> installing, one has to add the lines:
>	# ssh-pageant
>	eval $(/usr/bin/ssh-pageant -r -a "/tmp/.ssh-pageant-$USERNAME")
> (see https://github.com/cuviper/ssh-pageant)
> to .bashrc for each user.
> Would it be acceptable to update the ssh-pageant package to add a file
> /etc/profile.d/ssh-pageant.sh that does this automatically?
> Or is there another preferred way to do this, e.g. a postinstall script?
> I'd be happy to draft a script file for review.

For the general case, you may want to suggest that the maintainer include
instructions about this in each upgrade notice, but nothing should be done in
the package as it assumes too much about users' environments.

For example: what if their default shell/s is/are not bash, or they don't
already have a .bashrc, and shouldn't you do that setup in whatever their shell
profile is, if they have one, and what if they don't; what if Pageant or Cygwin
don't use Cygwin /tmp/ but some other TMPDIR e.g. Windows ~/AppData/Local/Temp/;
what if your users run ssh from cmd without starting Cygwin; etc.?

You may do what your users allow you on their systems, but you have to ensure
that your Putty/Pageant and ssh setup additions work flawlessly on all of them,
coordinating between what you do for Pageant and what you do for ssh.

You may want to consider doing whatever is required in each user's ssh_config if
possible, or /etc/ssh_config to provide users defaults, as those depend least on
each user's environment.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

  parent reply	other threads:[~2020-04-23 18:33 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 ` Brian Inglis [this message]
2020-04-23 20:02 ` ssh-pageant Andrey Repin
2020-04-23 20:20   ` ssh-pageant Chris Rodgers
2020-04-23 20:51     ` ssh-pageant Andrey Repin

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=c3fd2c28-7f9a-9611-c595-5be88b508d7c@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).