From: Andrew Schulman <schulman.andrew@epa.gov>
To: cygwin-apps@cygwin.com
Subject: Re: cygport upload
Date: Sun, 29 Mar 2020 08:08:56 -0400 [thread overview]
Message-ID: <j4318f1pkbqllqfvkmc39d7pnvv1orrbl8@4ax.com> (raw)
In-Reply-To: <555ac0bb-0984-f320-c240-df9e165ca062@dronecode.org.uk>
> > OK, works. Can lftp or cygport be configured so that lftp does not ask
> > for a password? Or to use sftp instead?
>
> I don't know of any configuration for lftp to turn off that behaviour
> (which is arguably a defect in lftp), but that's probably something you
> could investigate for yourself.
>
> I am not sure why lftp is used instead of sftp, possibly it is
> insufficiently scriptable to do what cygport wants to do.
I wrote the upload command for cygport, with review by Yaakov. Yes, it is harder
to script than you might guess. I originally proposed to offer sftp and lftp
options, but he said to strip it down to just lftp.
The logic is in /usr/share/cygport/lib/pkg_upload.cygpart. If the SSH_KEY
environment variable isn't set, then lftp connects with the connect string
sftp://cygwin@cygwin.com
which will prompt for a password. To use an ssh key, set SSH_KEY equal to the
file name of the key. You can do that in ~/.cygport.conf, for example:
SSH_KEY=~/.ssh/id_dsa
Then if the key is already loaded in a running ssh_agent, or if it's
unencrypted, you shouldn't get a password prompt. Note that SSH_KEY is
documented in the cygport docs.
Good luck!
Andrew
prev parent reply other threads:[~2020-03-29 12:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 10:17 Thomas Wolff
2020-03-27 12:21 ` Jon Turney
2020-03-27 14:35 ` Thomas Wolff
2020-03-27 15:41 ` Jon Turney
2020-03-27 16:15 ` Thomas Wolff
2020-03-27 16:27 ` Jon Turney
2020-03-27 17:31 ` Thomas Wolff
2020-03-27 18:25 ` CLDR pkg-config (was: cygport upload) Brian Inglis
2020-03-29 12:08 ` Andrew Schulman [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=j4318f1pkbqllqfvkmc39d7pnvv1orrbl8@4ax.com \
--to=schulman.andrew@epa.gov \
--cc=cygwin-apps@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).