|
Kevin. Haha. That's a good question. Ummm because I'm following an example from a Scott klement tutorial. (Must be obsolete)
So I remove the -1 and no longer get the version msg. But I am still having an issue with the server accepting the public key at sign on.
Will create a new thread on this tomorrow.
Jay
Sent from my iPhone
On Apr 17, 2018, at 10:44 AM, Kevin Bucknum <Kevin@xxxxxxxxxxxxxxxxxxx> wrote:
Why are you trying to force protocol 1 with the -1 flag? SSH version 1
hasn't been safe for quite a while yet. It looks like the server piece
has already disabled it, but you are trying to force the client to use
it.
Kevin Bucknum
Senior Programmer Analyst
MEDDATA/MEDTRON
Tel: 985-893-2550
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalfgetting...
Of Jay Vaughn
Sent: Tuesday, April 17, 2018 9:36 AM
To: Midrange Systems Technical Discussion
Subject: Re: iSeries SSH config for SFTP
ok the issue was i wasn't specifying the host correctly... so now I am
(so is the message "Protocol major versions differ: 1 vs. 2" highseverity?
What is the solution?<michaelrtr@xxxxxxxxx>
ssh -1 -vvv lsamsso@xxxxxxxxxx
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 10.110.4.99 [10.110.4.99] port 22.
debug1: Connection established.
debug1: identity file /home/lsamsso/.ssh/identity type -1
debug1: Remote protocol version 2.0, remote software version
OpenSSH_6.9
debug1: match: OpenSSH_6.9 pat OpenSSH*
Protocol major versions differ: 1 vs. 2
$
On Tue, Apr 17, 2018 at 10:34 AM, Jay Vaughn
<jeffersonvaughn@xxxxxxxxx>
wrote:
gotcha - thanks...
so what in the world am I missing?
on one lpar I have setup to be an SFTP server by... QSYS/STRTCPSVR
SERVER(*SSHD)
on another lpar i am doing the following and cannot log on for some
reason...??
what is this telling me?
ssh -1 -vvv user 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
ssh: lsamsso: Hostname and service name not provided or found
$
On Tue, Apr 17, 2018 at 10:30 AM, Michael Ryan
public key.wrote:
They both are. id_rsa is your private key, id_rsa.pub is your
So...
Sent from my iPhone
On Apr 17, 2018, at 10:28 AM, Jay Vaughnwrote:
<jeffersonvaughn@xxxxxxxxx>
the
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
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.
connecting...theI 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:
so thought I had performed the setup steps correctly, but
producing
key
info to home/userprf/.ssh directory...
but when I run the simple sftp, there is an issue with
To(what does this mean? " debug3: Not a RSA1 key fileThis is the Midrange Systems Technical Discussion (MIDRANGE-L)
/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
--
mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx
relatedpleasesubscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting,
take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription
listtakeaffiliatequestions.
Help support midrange.com by shopping at amazon.com with our
list--link: http://amzn.to/2dEadiD
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,questions.
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
link: http://amzn.to/2dEadiD
Help support midrange.com by shopping at amazon.com with our
affiliate
--
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
--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
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.