Re: Using Putty to access IBM i

[Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>]

On my V7R4 partition we simply started the *SSHD daemon and signed on after
accepting the certificate.
That's out of box.   Since you were messing with Ciphers earlier, are you
sure you did not enable/disable on of them needed for this?

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On Fri, Nov 15, 2019 at 7:39 AM Rob Berendt <rob@xxxxxxxxx> wrote:

> I downloaded Scott's presentation.  Basically it says at my release of the
> OS I should be able to run STRTCPSVR *SSHD and it will automatically
> generate the keys and I should be able to connect right away using putty.
> I'm using the same putty client that he is.  I get the log in but it fails
> after I enter in my password.
>
> Rob Berendt
> --
> IBM Certified System Administrator - IBM i 6.1
> Group Dekko
> Dept 1600
> Mail to:  2505 Dekko Drive
>           Garrett, IN 46738
> Ship to:  Dock 108
>           6928N 400E
>           Kendallville, IN 46755
> http://www.dekko.com
>
>
> -----Original Message-----
> From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
> Mark Waterbury
> Sent: Thursday, November 14, 2019 5:44 PM
> To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
> Subject: Re: Using Putty to access IBM i
>
> CAUTION: This email originated from outside of the organization. Do not
> click links or open attachments unless you recognize the sender and know
> the content is safe.
>
>
>  Hi, Rob,
>
> Scott put together a nice presentation about this topic, it is available
> here as a .pdf --
>
> http://www.scottklement.com/presentations/#OPENSSH
>
>
> Perhaps that might help?
>
> Mark S. Waterbury
>
>     On Thursday, November 14, 2019, 5:10:46 PM EST, Rob Berendt <
> rob@xxxxxxxxx> wrote:
>
>  Ok, I hear all this stuff about how using qsHell and/or pase to process
> some things isn't quite as kosher as using a ssh client, such as putty.  I
> think Scott Klement explained it with "Need for a "Real" Unix Terminal".
> I'm starting to accept that.
>
> How does one set up your partition to get to it using a putty client?
>
> I see that the webby "IBM Navigator for i" says that SSHD is started.
> NETSTAT *CNN shows
> F15 subset to port 22
> Remote          Remote    Local            Local
> Address          Port      Address          Port      Type
> *                *          2##.##.##.##    ssh        *TCP
> And the job is:
>                                                   Current
> Name          User          Number    Type      User
> QP0ZSPWT      QPGMR          622938    *BCH      QPGMR
>
>
> I use that address in my putty client on my PC.  I get:
> login as: rob
> Pre-authentication banner message from server:
> | Welcome! Please login.
> End of banner message from server
> Keyboard-interactive authentication prompts from server:
> | password
> | Password:
> Enter in my password.  That screen displays:  End of keyboard-interactive
> prompts from server
> And I get a popup:  Server refused to start a shell/command
>
>
>
>
>
> I am using:
> PuTTY
> Release 0.71
> Build platform: 64-bit x86 Windows
> Compiler: clang 7.0.0 (tags/RELEASE_700/final), emulating Visual Studio
> 2013 / MSVC++ 12.0 (_MSC_VER=1800)
> Embedded HTML Help file: yes
> Source commit: abfc751c3ee7d57bf3f127a458c40bb4ca2b6996
> (c) 1997-2019 Simon Tatham. All rights reserved.
>
>
> Rob Berendt
> --
> IBM Certified System Administrator - IBM i 6.1
> Group Dekko
> Dept 1600
> Mail to:  2505 Dekko Drive
>           Garrett, IN 46738
> Ship to:  Dock 108
>         6928N 400E
>           Kendallville, IN 46755
> http://www.dekko.com
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> 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: https://amazon.midrange.com
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> 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: https://amazon.midrange.com
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> 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: https://amazon.midrange.com