SSH key for John Zaitseff

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

SSH key for John Zaitseff

John Zaitseff
Name: John Zaitseff
Package: trader
---- BEGIN SSH2 PUBLIC KEY ----
AAAAB3NzaC1yc2EAAAADAQABAAACAQDO22+n2oFc0zw/opwCTH9D+YLJMIoFDPnXDhW3oI
AOIrlKZy0zYKJQFRqUYvdcReRVETkic0pDYVZMJa+vYR9L9HUbpExfKmlaj5rgS8t//Fgf
ZJr8y1POfbsSXJLFI5uVUoM3FMTZPwiY/qWYd9DgU8SKa9UFNrDCanM3c0oV9Yn1tzoGa5
+WtVxJRzeg18R0FQekLKlCpKJG9GvQ775q3M6I9gdqqJYO551sn8jCyncrqPry8C4/zR62
x+IQe6Q7gNYDPAKBdt1U4wR2cXbwpURR8cU7TjZ7Wu5zqAXxXhsHGqGj7e/6khBgesP/dr
EfR0OnC+jZs4IsuUd7sD8JmTqKzYx9WxEvgyv5pxiu4Kb/xrm66X7XXwtM+M1zQwRC7rUW
XbP/QS+Qzp14lYr46OnPPnxFX4LRuZlebDDUOw72HhdHiwtYizhb1F362X0ayrVULnkFCU
Zhlrf4acfIBij1dWWMNJfVhl4Q65Z70PFroyRURIlIAohhINm9UpwzVM7rJxjotll8mxHs
oSta6L6F8hzE4ZsiMpJSupek4a/3eb6bg8bySet6BE+RYdOzQAuxjPSpAAtjP7bSZ6fxIL
N2wi3eQr7UtJeb/vLhS7q6tb4n5Yk79fJrmJC7qpeY8vbZD/NMcq8LbB1hJzKDaKm2CYpO
t4MDC4g08JJYIQ==
---- END SSH2 PUBLIC KEY ----
Reply | Threaded
Open this post in threaded view
|

Re: SSH key for John Zaitseff

Jon TURNEY
On 01/12/2019 20:52, John Zaitseff wrote:
> Name: John Zaitseff
> Package: trader

Done.  Thanks.
Reply | Threaded
Open this post in threaded view
|

Re: SSH key for John Zaitseff

John Zaitseff
Hi, Jon et al,

> > Name: John Zaitseff
> > Package: trader
>
> Done.  Thanks.

Thank you.  When I use sftp to connect to [hidden email] (as per
the instructions at https://cygwin.com/package-upload.html), I do
not see the file "!packages".  Consequently, when I try to upload my
trader package, as soon as I try to copy across any tar file, the
connection is closed.  Is the missing "!packages" file an oversight,
or am I simply being too eager and the file will be created in due
course? :-)

Yours truly,

John Zaitseff
Reply | Threaded
Open this post in threaded view
|

Re: SSH key for John Zaitseff

Jon TURNEY
On 03/12/2019 21:14, John Zaitseff wrote:

>>> Name: John Zaitseff
>>> Package: trader
>>
>> Done.  Thanks.
>
> Thank you.  When I use sftp to connect to [hidden email] (as per
> the instructions at https://cygwin.com/package-upload.html), I do
> not see the file "!packages".  Consequently, when I try to upload my
> trader package, as soon as I try to copy across any tar file, the
> connection is closed.  Is the missing "!packages" file an oversight,
> or am I simply being too eager and the file will be created in due
> course? :-)

The !packages files are updated by a separate process which runs at 0400
UTC daily (mkpkgdir, which is a bit of a misnomer now, as it's only
remaining useful function is to identify for removal the upload
directories of maintainers who have given up all their packages)

But the !packages file is only there for historical and informational
purposes, it's not involved in the upload authorization.

Furthermore, the restriction is not applied to the filenames you can
upload, but to the processing we do on them after the sftp session has
closed, so I think something else must be the cause of your connection
being closed.
Reply | Threaded
Open this post in threaded view
|

Re: SSH key for John Zaitseff

Brian Inglis
On 2019-12-03 16:52, Jon Turney wrote:
> On 03/12/2019 21:14, John Zaitseff wrote:
>>>> Name: John Zaitseff
>>>> Package: trader

>> Thank you.  When I use sftp to connect to
>> [hidden email] (as per
>> the instructions at https://cygwin.com/package-upload.html), I do
>> not see the file "!packages".  Consequently, when I try to upload my
>> trader package, as soon as I try to copy across any tar file, the
>> connection is closed.  Is the missing "!packages" file an oversight,
>> or am I simply being too eager and the file will be created in due
>> course? :-)

> Furthermore, the restriction is not applied to the filenames you can upload, but
> to the processing we do on them after the sftp session has closed, so I think
> something else must be the cause of your connection being closed.

I also had problems with sftp, but none with lftp, or cygport <pkg> upload:
the last should be considered preferred nowadays, as it handles ssh auth, lftp
transfer, and setting flag files, and may be updated to accommodate any calm
requirements change.

Make life easier with appropriate settings in ~/.cygport.conf:

        SSH_KEY=... # for upload
        DISTDIR=... # for download
        SMTP_...=... # for announce

--
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.
Reply | Threaded
Open this post in threaded view
|

Re: SSH key for John Zaitseff

John Zaitseff
Hi, everyone,

> I also had problems with sftp, but none with lftp, or cygport
> <pkg> upload: the last should be considered preferred nowadays, as
> it handles ssh auth, lftp transfer, and setting flag files, and
> may be updated to accommodate any calm requirements change.

Thanks.  Using lftp from my Linux system worked.  I'll try cygport
in my Windows VMs on the next release of my package.

Yours truly,

John Zaitseff