|
On Apr 17, 2018, at 10:28 AM, Jay Vaughn <jeffersonvaughn@xxxxxxxxx> wrote:
ok, we do in fact have the prerequisites loaded and in place...
so which file is RSA2?
the id_rsa or the id_rsa.pub?
Jay
On Tue, Apr 17, 2018 at 9:40 AM, Jay Vaughn <jeffersonvaughn@xxxxxxxxx>
wrote:
Thanks - Scott your PDF on this is priceless...--
I went back over it and found the "prerequisites" section.
Seems as though we don't have everything necessary loaded - so that is the
first item of biz before I continue.
Jay
On Mon, Apr 16, 2018 at 5:44 PM, Scott Klement <
midrange-l@xxxxxxxxxxxxxxxx> wrote:
Jay,
The id_rsa/id_rsa.pub filenames are the default for RSA2. So... I
suspect that it's quite correct that they aren't RSA1... plus... it's
2018, and nobody should be using RSA1!
-SK
On 4/16/2018 12:44 PM, Jay Vaughn wrote:This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
so thought I had performed the setup steps correctly, but producing the
key
info to home/userprf/.ssh directory...
but when I run the simple sftp, there is an issue with connecting...
(what does this mean? " debug3: Not a RSA1 key file
/home/lsamsso/.ssh/id_rsa."???
sftp -vvv user@xxxxxxxxxxx
Connecting to xx.xxx.x.xx...
OpenSSH_4.7p1, OpenSSL 0.9.7d 17 Mar 2004
debug1: Reading configuration data
/QOpenSys/QIBM/ProdData/SC1/OpenSSH/openss
h-3.8.1p1//etc/ssh_config
debug3: RNG is ready, skipping seeding
debug2: ssh_connect: needpriv 0
debug1: Connecting to xx.xxx.x.xx [xx.xxx.x.xx] port 22.
debug1: Connection established.
debug3: Not a RSA1 key file /home/user/.ssh/id_rsa.
debug2: key_type_from_name: unknown key type '-----BEGIN'
debug3: key_read: missing keytype
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
...
Jay
--
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.