Brian White [EMAIL PROTECTED] wrote:
[...]
I've avoided changing to OpenSSH at home because I'm unsure how to
convert the keys from the SSH2 format to the OpenSSH format.
[...]
Afaict ssh-keygen from OpenSSH can do that:
-i This option will read an unencrypted private (or public) key file
Brian White [EMAIL PROTECTED] wrote:
[...]
I've avoided changing to OpenSSH at home because I'm unsure how to
convert the keys from the SSH2 format to the OpenSSH format.
[...]
Afaict ssh-keygen from OpenSSH can do that:
-i This option will read an unencrypted private (or public)
SCP doesn't work (I suspect) because I'm using the SSH2 package once
found in non-free.
Oh, ssh2 is broken, yes. Try 'scp -1', perhaps?
I don't keep ssh1 installed for security reasons. sigh
I mentioned this (and the reasons why) some time back.
Care to reiterate? I can't remember,
On Mon, Sep 22, 2003 at 01:14:47PM -0400, Brian White wrote:
Martin Michlmayr wrote:
* Brian White [EMAIL PROTECTED] [2003-09-20 07:37]:
Neither SCP nor anonymous-FTP methods work and I want to get that
fixed.
SSH works. SCP doesn't.
Well, it works for everyone else. So it
On Tue, Sep 23, 2003 at 12:14:02AM +0100, James Troup wrote:
The queue daemon can no longer handle PGP 2.x keys; I don't know why
and since a) the number of developers still using these kind of keys
for uploads can be counted on the fingers of a mutilated hand, b)
there are alternative methods
* Brian White [EMAIL PROTECTED] [2003-09-20 07:37]:
Neither SCP nor anonymous-FTP methods work and I want to get that
fixed.
SSH works. SCP doesn't.
Well, it works for everyone else. So it would be good if you'd find
out why it doesn't work for you. In the meantime, you can put your
signed
Martin Michlmayr [EMAIL PROTECTED] a tapoté :
* Brian White [EMAIL PROTECTED] [2003-09-20 07:37]:
Neither SCP nor anonymous-FTP methods work and I want to get that
fixed.
SSH works. SCP doesn't.
Well, it works for everyone else. So it would be good if you'd find
out why it doesn't
On Sat, Sep 20, 2003 at 03:48:35PM +0200, Andreas Metzler wrote:
Brian White [EMAIL PROTECTED] wrote:
SSH works. SCP doesn't.
It is easy to circumvent non-working scp:
tar cf - foo bar | ssh ftp-master.debian.org tar xf -
or
rsync -vtaz foo bar ftp-master.debian.org:
Scp works for me,
On Mon, Sep 22, 2003 at 11:57:14PM +1000, Martin Michlmayr wrote:
* Brian White [EMAIL PROTECTED] [2003-09-20 07:37]:
Neither SCP nor anonymous-FTP methods work and I want to get that
fixed.
SSH works. SCP doesn't.
Well, it works for everyone else. So it would be good if you'd find
Matt Zimmerman [EMAIL PROTECTED] writes:
What didn't work about anonymous FTP?
The queue daemon can no longer handle PGP 2.x keys; I don't know why
and since a) the number of developers still using these kind of keys
for uploads can be counted on the fingers of a mutilated hand, b)
there are
* Brian White [EMAIL PROTECTED] [2003-09-20 07:37]:
Neither SCP nor anonymous-FTP methods work and I want to get that
fixed.
SSH works. SCP doesn't.
Well, it works for everyone else. So it would be good if you'd find
out why it doesn't work for you. In the meantime, you can put
On Mon, Sep 01, 2003 at 10:04:19PM -0400, Brian White wrote:
What do I have to do to fix this problem? My key is valid, has been
signed, and was uploaded to the keyserver via gpg --send-keys.
Why do I continue to get these messages? The only way I can upload
packages is to use SSH to
What do I have to do to fix this problem? My key is valid, has been
signed, and was uploaded to the keyserver via gpg --send-keys.
Why do I continue to get these messages? The only way I can upload
packages is to use SSH to connect to ftp-master and then use wget
to fetch the various files from
13 matches
Mail list logo
