Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #212683 > unrolled thread

Secure Shell refuses to accept connections from anyone

Back to article view | Back to linux.debian.user

Contents

  Secure Shell refuses to accept connections from anyone Keith Steensma <keith@airways-consulting.com> - 2019-08-12 15:40 +0200
    Re: Secure Shell refuses to accept connections from anyone john doe <johndoe65534@mail.com> - 2019-08-12 16:20 +0200
      Re: Secure Shell refuses to accept connections from anyone Keith Steensma <keith@airways-consulting.com> - 2019-08-12 16:50 +0200
        Re: Secure Shell refuses to accept connections from anyone john doe <johndoe65534@mail.com> - 2019-08-12 17:00 +0200
    Re: Secure Shell refuses to accept connections from anyone Roberto C. Sánchez <roberto@debian.org> - 2019-08-12 16:30 +0200
      Re: Secure Shell refuses to accept connections from anyone Roberto C. Sánchez <roberto@debian.org> - 2019-08-12 16:40 +0200
      Re: Secure Shell refuses to accept connections from anyone Dan Ritter <dsr@randomstring.org> - 2019-08-12 16:40 +0200
        Re: Secure Shell refuses to accept connections from anyone john doe <johndoe65534@mail.com> - 2019-08-12 16:50 +0200
        Re: Secure Shell refuses to accept connections from anyone Keith Steensma <keith@airways-consulting.com> - 2019-08-12 16:50 +0200
          Re: Secure Shell refuses to accept connections from anyone mick crane <mick.crane@gmail.com> - 2019-08-12 22:00 +0200
      Re: Secure Shell refuses to accept connections from anyone Keith Steensma <keith@airways-consulting.com> - 2019-08-12 16:40 +0200
    Re: Secure Shell refuses to accept connections from anyone mick crane <mick.crane@gmail.com> - 2019-08-12 16:40 +0200
    Re: Secure Shell refuses to accept connections from anyone Bruce Halco <bruce@halcomp.com> - 2019-08-12 16:50 +0200
    Re: Secure Shell refuses to accept connections from anyone Andrei POPESCU <andreimpopescu@gmail.com> - 2019-08-12 21:10 +0200
    Re: Secure Shell refuses to accept connections from anyone elvis <elvis@dogonfire.com> - 2019-08-12 23:10 +0200
      Re: Secure Shell refuses to accept connections from anyone <tomas@tuxteam.de> - 2019-08-13 15:30 +0200
        Re: Secure Shell refuses to accept connections from anyone Joe <joe@jretrading.com> - 2019-08-13 17:40 +0200
          Re: Secure Shell refuses to accept connections from anyone Michael Howard <mike@dewberryfields.co.uk> - 2019-08-13 18:50 +0200
            Re: Secure Shell refuses to accept connections from anyone Keith Steensma <keith@airways-consulting.com> - 2019-08-13 19:50 +0200
              Re: Secure Shell refuses to accept connections from anyone john doe <johndoe65534@mail.com> - 2019-08-13 20:10 +0200
              Re: Secure Shell refuses to accept connections from anyone Michael Howard <mike@dewberryfields.co.uk> - 2019-08-13 20:20 +0200
                Re: Secure Shell refuses to accept connections from anyone Keith Steensma <keith@airways-consulting.com> - 2019-08-14 00:30 +0200
                  Re: Secure Shell refuses to accept connections from anyone Keith Steensma <keith@airways-consulting.com> - 2019-08-14 04:20 +0200
                    Re: Secure Shell refuses to accept connections from anyone Bruce Halco <bruce@halcomp.com> - 2019-08-14 12:30 +0200
                    Re: Secure Shell refuses to accept connections from anyone Michael Howard <mike@dewberryfields.co.uk> - 2019-08-14 13:40 +0200
                Re: Secure Shell refuses to accept connections from anyone Keith Steensma <keith@airways-consulting.com> - 2019-08-14 00:30 +0200
      Re: Secure Shell refuses to accept connections from anyone Keith Steensma <keith@airways-consulting.com> - 2019-08-13 15:30 +0200

Page 1 of 2  [1] 2  Next page →

#212683 — Secure Shell refuses to accept connections from anyone

I've installed both Version 9.9 (OldStable) and 'Buster' (Stable) and 
found that both version seem to have the same problem.  It's like I'm 
doing something wrong.  But these are fresh installs - no modification.

With Secure Shell server installed and running on port 22 (or any other 
port of your choice) and iptable Chain Input and Output Policy Accept 
All.  When I try to connect from a Windows machine using 'putty' 
(without letting 'putty' fill in any user name) and fill in a regular 
user's login name, Secure Shell refuses to allow that connection and 
replies back "Access denied' and asks for the password again and again, 
and again. Never allowing the connection.

The same thing happens if I fill in 'root' as the login even though a 
'root' login is not permitted in the default 'sshd_config' 
configuration.  Even when I change the configuration to allow for 'root' 
login, 'root' can never login.

Has anyone run into this behavior before or know about a fix for this 
problem.  I have formatted, installed, reinstalled and Googled so many 
times that I many be going crazy.

Keith

[toc] | [next] | [standalone]

#212686

On 8/12/2019 3:23 PM, Keith Steensma wrote:
> I've installed both Version 9.9 (OldStable) and 'Buster' (Stable) and
> found that both version seem to have the same problem.  It's like I'm
> doing something wrong.  But these are fresh installs - no modification.
>
> With Secure Shell server installed and running on port 22 (or any other
> port of your choice) and iptable Chain Input and Output Policy Accept
> All.  When I try to connect from a Windows machine using 'putty'
> (without letting 'putty' fill in any user name) and fill in a regular
> user's login name, Secure Shell refuses to allow that connection and
> replies back "Access denied' and asks for the password again and again,
> and again. Never allowing the connection.
>
> The same thing happens if I fill in 'root' as the login even though a
> 'root' login is not permitted in the default 'sshd_config'
> configuration.  Even when I change the configuration to allow for 'root'
> login, 'root' can never login.
>
> Has anyone run into this behavior before or know about a fix for this
> problem.  I have formatted, installed, reinstalled and Googled so many
> times that I many be going crazy.
>

A username needs to be specified for putty to be able to connect to the
SSH server.
So after a fresh install of Debian in putty try to enter the username
and the password of the non-root user you have created at install time.


For the time being  clear any rules in iptables and try to install
Debian with SSH pkg and see how it goes from there.


I have no problem accessing my servers on Stretch or Buster after an
upgrade from Stretch to Buster or after an fresh install of both releases.

--
John Doe

[toc] | [prev] | [next] | [standalone]

#212695

On 8/12/2019 9:18 AM, john doe wrote:
> On 8/12/2019 3:23 PM, Keith Steensma wrote:
>> I've installed both Version 9.9 (OldStable) and 'Buster' (Stable) and
>> found that both version seem to have the same problem.  It's like I'm
>> doing something wrong.  But these are fresh installs - no modification.
>>
>> With Secure Shell server installed and running on port 22 (or any other
>> port of your choice) and iptable Chain Input and Output Policy Accept
>> All.  When I try to connect from a Windows machine using 'putty'
>> (without letting 'putty' fill in any user name) and fill in a regular
>> user's login name, Secure Shell refuses to allow that connection and
>> replies back "Access denied' and asks for the password again and again,
>> and again. Never allowing the connection.
>>
>> The same thing happens if I fill in 'root' as the login even though a
>> 'root' login is not permitted in the default 'sshd_config'
>> configuration.  Even when I change the configuration to allow for 'root'
>> login, 'root' can never login.
>>
>> Has anyone run into this behavior before or know about a fix for this
>> problem.  I have formatted, installed, reinstalled and Googled so many
>> times that I many be going crazy.
>>
> A username needs to be specified for putty to be able to connect to the
> SSH server.
> So after a fresh install of Debian in putty try to enter the username
> and the password of the non-root user you have created at install time.
>
>
> For the time being  clear any rules in iptables and try to install
> Debian with SSH pkg and see how it goes from there.
>
>
> I have no problem accessing my servers on Stretch or Buster after an
> upgrade from Stretch to Buster or after an fresh install of both releases.
>
> --
> John Doe
>
I've done that more than a few times. Even to the point of thinking it 
was the hardware
(which it is not).  I had been using the net install version and 
considered that it was tainted,
so I download a full dvd version but it is the same way.  I've used 
Debian for over 10 years
and never been faced with something like this.

BTW. Where in putty do you put the user's password?  I've never seen 
that slot.  I know where
the user's key goes, but not the user's password.

[toc] | [prev] | [next] | [standalone]

#212699

On 8/12/2019 4:42 PM, Keith Steensma wrote:
>
>
> On 8/12/2019 9:18 AM, john doe wrote:
>> On 8/12/2019 3:23 PM, Keith Steensma wrote:
>>> I've installed both Version 9.9 (OldStable) and 'Buster' (Stable) and
>>> found that both version seem to have the same problem.  It's like I'm
>>> doing something wrong.  But these are fresh installs - no modification.
>>>
>>> With Secure Shell server installed and running on port 22 (or any other
>>> port of your choice) and iptable Chain Input and Output Policy Accept
>>> All.  When I try to connect from a Windows machine using 'putty'
>>> (without letting 'putty' fill in any user name) and fill in a regular
>>> user's login name, Secure Shell refuses to allow that connection and
>>> replies back "Access denied' and asks for the password again and again,
>>> and again. Never allowing the connection.
>>>
>>> The same thing happens if I fill in 'root' as the login even though a
>>> 'root' login is not permitted in the default 'sshd_config'
>>> configuration.  Even when I change the configuration to allow for 'root'
>>> login, 'root' can never login.
>>>
>>> Has anyone run into this behavior before or know about a fix for this
>>> problem.  I have formatted, installed, reinstalled and Googled so many
>>> times that I many be going crazy.
>>>
>> A username needs to be specified for putty to be able to connect to the
>> SSH server.
>> So after a fresh install of Debian in putty try to enter the username
>> and the password of the non-root user you have created at install time.
>>
>>
>> For the time being  clear any rules in iptables and try to install
>> Debian with SSH pkg and see how it goes from there.
>>
>>
>> I have no problem accessing my servers on Stretch or Buster after an
>> upgrade from Stretch to Buster or after an fresh install of both
>> releases.
>>
>> --
>> John Doe
>>
> I've done that more than a few times. Even to the point of thinking it
> was the hardware
> (which it is not).  I had been using the net install version and
> considered that it was tainted,

No problem here with 'netinst.iso' file, did you checksummed and
verified the iso file before using it?

> so I download a full dvd version but it is the same way.  I've used
> Debian for over 10 years
> and never been faced with something like this.
>
> BTW. Where in putty do you put the user's password?  I've never seen
> that slot.  I know where
> the user's key goes, but not the user's password.
>

For me, after entering the server hostname/ip and port I click on open
then I get prompted to enter the username and then the password.

--
John Doe

[toc] | [prev] | [next] | [standalone]

#212688

On Mon, Aug 12, 2019 at 08:23:17AM -0500, Keith Steensma wrote:
> I've installed both Version 9.9 (OldStable) and 'Buster' (Stable) and found
> that both version seem to have the same problem.  It's like I'm doing
> something wrong.  But these are fresh installs - no modification.
> 
> With Secure Shell server installed and running on port 22 (or any other port
> of your choice) and iptable Chain Input and Output Policy Accept All.  When
> I try to connect from a Windows machine using 'putty' (without letting
> 'putty' fill in any user name) and fill in a regular user's login name,
> Secure Shell refuses to allow that connection and replies back "Access
> denied' and asks for the password again and again, and again. Never allowing
> the connection.
> 
What messages are logged on the machine(s) running sshd?

Regards,

-Roberto

-- 
Roberto C. Sánchez

[toc] | [prev] | [next] | [standalone]

#212689

On Mon, Aug 12, 2019 at 09:32:42AM -0500, Keith Steensma wrote:
> 
> 
> On 8/12/2019 9:23 AM, Roberto C. Sánchez wrote:
> > On Mon, Aug 12, 2019 at 08:23:17AM -0500, Keith Steensma wrote:
> > > I've installed both Version 9.9 (OldStable) and 'Buster' (Stable) and found
> > > that both version seem to have the same problem.  It's like I'm doing
> > > something wrong.  But these are fresh installs - no modification.
> > > 
> > > With Secure Shell server installed and running on port 22 (or any other port
> > > of your choice) and iptable Chain Input and Output Policy Accept All.  When
> > > I try to connect from a Windows machine using 'putty' (without letting
> > > 'putty' fill in any user name) and fill in a regular user's login name,
> > > Secure Shell refuses to allow that connection and replies back "Access
> > > denied' and asks for the password again and again, and again. Never allowing
> > > the connection.
> > > 
> > What messages are logged on the machine(s) running sshd?
> > 
> > Regards,
> > 
> > -Roberto
> > 
> In /var/log/messages NOTHING and that is so maddening.  I have tried to get
> it to log something, anything and
> it won't.
> 

Then try executing ssh with the '-vvv' option from the client side and
examining the diagnostic messages related to the key exchange and other
steps of the connection negotiation.

Regards,

-Roberto
-- 
Roberto C. Sánchez

[toc] | [prev] | [next] | [standalone]

#212690

Keith Steensma wrote: 
> 
> 
> On 8/12/2019 9:23 AM, Roberto C. Sánchez wrote:
> > On Mon, Aug 12, 2019 at 08:23:17AM -0500, Keith Steensma wrote:
> > > I've installed both Version 9.9 (OldStable) and 'Buster' (Stable) and found
> > > that both version seem to have the same problem.  It's like I'm doing
> > > something wrong.  But these are fresh installs - no modification.
> > > 
> > > With Secure Shell server installed and running on port 22 (or any other port
> > > of your choice) and iptable Chain Input and Output Policy Accept All.  When
> > > I try to connect from a Windows machine using 'putty' (without letting
> > > 'putty' fill in any user name) and fill in a regular user's login name,
> > > Secure Shell refuses to allow that connection and replies back "Access
> > > denied' and asks for the password again and again, and again. Never allowing
> > > the connection.
> > > 
> > What messages are logged on the machine(s) running sshd?
> > 
> > Regards,
> > 
> > -Roberto
> > 
> In /var/log/messages NOTHING and that is so maddening.  I have tried to get
> it to log something, anything and
> it won't.

Check /var/log/auth.log

-dsr-

[toc] | [prev] | [next] | [standalone]

#212694

On 8/12/2019 4:34 PM, Dan Ritter wrote:
> Keith Steensma wrote:
>>
>>
>> On 8/12/2019 9:23 AM, Roberto C. Sánchez wrote:
>>> On Mon, Aug 12, 2019 at 08:23:17AM -0500, Keith Steensma wrote:
>>>> I've installed both Version 9.9 (OldStable) and 'Buster' (Stable) and found
>>>> that both version seem to have the same problem.  It's like I'm doing
>>>> something wrong.  But these are fresh installs - no modification.
>>>>
>>>> With Secure Shell server installed and running on port 22 (or any other port
>>>> of your choice) and iptable Chain Input and Output Policy Accept All.  When
>>>> I try to connect from a Windows machine using 'putty' (without letting
>>>> 'putty' fill in any user name) and fill in a regular user's login name,
>>>> Secure Shell refuses to allow that connection and replies back "Access
>>>> denied' and asks for the password again and again, and again. Never allowing
>>>> the connection.
>>>>
>>> What messages are logged on the machine(s) running sshd?
>>>
>>> Regards,
>>>
>>> -Roberto
>>>
>> In /var/log/messages NOTHING and that is so maddening.  I have tried to get
>> it to log something, anything and
>> it won't.
>
> Check /var/log/auth.log
>

From (1) on the server side:

"LogLevel
Gives the verbosity level that is used when logging messages from
sshd(8). The possible values are: QUIET, FATAL, ERROR, INFO, VERBOSE,
DEBUG, DEBUG1, DEBUG2, and DEBUG3. The default is INFO. DEBUG and DEBUG1
are equivalent. DEBUG2 and DEBUG3 each specify higher levels of
debugging output. Logging with a DEBUG level violates the privacy of
users and is not recommended."


On Windows, you need to increase the verbosity of the client
(putty/Teraterm ...) or try Cygwin to use 'ssh -vvv' on windows.


1)  https://linux.die.net/man/5/sshd_config

--
John Doe

[toc] | [prev] | [next] | [standalone]

#212697

On 8/12/2019 9:34 AM, Dan Ritter wrote:
> Keith Steensma wrote:
>>
>> On 8/12/2019 9:23 AM, Roberto C. Sánchez wrote:
>>> On Mon, Aug 12, 2019 at 08:23:17AM -0500, Keith Steensma wrote:
>>>> I've installed both Version 9.9 (OldStable) and 'Buster' (Stable) and found
>>>> that both version seem to have the same problem.  It's like I'm doing
>>>> something wrong.  But these are fresh installs - no modification.
>>>>
>>>> With Secure Shell server installed and running on port 22 (or any other port
>>>> of your choice) and iptable Chain Input and Output Policy Accept All.  When
>>>> I try to connect from a Windows machine using 'putty' (without letting
>>>> 'putty' fill in any user name) and fill in a regular user's login name,
>>>> Secure Shell refuses to allow that connection and replies back "Access
>>>> denied' and asks for the password again and again, and again. Never allowing
>>>> the connection.
>>>>
>>> What messages are logged on the machine(s) running sshd?
>>>
>>> Regards,
>>>
>>> -Roberto
>>>
>> In /var/log/messages NOTHING and that is so maddening.  I have tried to get
>> it to log something, anything and
>> it won't.
> Check /var/log/auth.log
>
> -dsr-
>
Just shows SSH started and stopped.  I may have to modify the start up 
routine to include something.

[toc] | [prev] | [next] | [standalone]

#212712

On 2019-08-12 15:45, Keith Steensma wrote:
<snipped>
> Just shows SSH started and stopped.?? I may have to modify the start up
> routine to include something.

I think I might have had an issue going from windows putty to Linux with 
the windows line endings in the public key.
I think I've changed the encoding to linux in notepad++ on windows 
before pasting into authorized_keys.
If open the public key in vi you might see if there are any wonky 
characters.
Also I think it is possible to generate the key pair on linux and then 
import them with putty key_agent but I am hazy about that bit, think 
that is what I've done before.

mick

-- 
Key ID    4BFEBB31

[toc] | [prev] | [next] | [standalone]

#212692

On 8/12/2019 9:23 AM, Roberto C. Sánchez wrote:
> On Mon, Aug 12, 2019 at 08:23:17AM -0500, Keith Steensma wrote:
>> I've installed both Version 9.9 (OldStable) and 'Buster' (Stable) and found
>> that both version seem to have the same problem.  It's like I'm doing
>> something wrong.  But these are fresh installs - no modification.
>>
>> With Secure Shell server installed and running on port 22 (or any other port
>> of your choice) and iptable Chain Input and Output Policy Accept All.  When
>> I try to connect from a Windows machine using 'putty' (without letting
>> 'putty' fill in any user name) and fill in a regular user's login name,
>> Secure Shell refuses to allow that connection and replies back "Access
>> denied' and asks for the password again and again, and again. Never allowing
>> the connection.
>>
> What messages are logged on the machine(s) running sshd?
>
> Regards,
>
> -Roberto
>
In /var/log/messages NOTHING and that is so maddening.  I have tried to 
get it to log something, anything and
it won't.

[toc] | [prev] | [next] | [standalone]

#212691

On 2019-08-12 15:22, Keith Steensma wrote:
> Using
> "PermitRootLogin Yes"
> "PubkeyAuthentication yes"
> and a SSH key created under putty and placed in the proper location in
> the 'root' directory, still gives a "Server refused our Key"
> 
I can't remember.
perhaps you have to restart sshd after changing the config file.
The public key wants to be in ~/.ssh/authorized_keys.

mick
-- 
Key ID    4BFEBB31

[toc] | [prev] | [next] | [standalone]

#212696

Is there anything useful in /var/log/sshd.log?

Bruce

On 8/12/19 9:23 AM, Keith Steensma wrote:
> I've installed both Version 9.9 (OldStable) and 'Buster' (Stable) and 
> found that both version seem to have the same problem.  It's like I'm 
> doing something wrong.  But these are fresh installs - no modification.
>
> With Secure Shell server installed and running on port 22 (or any 
> other port of your choice) and iptable Chain Input and Output Policy 
> Accept All.  When I try to connect from a Windows machine using 
> 'putty' (without letting 'putty' fill in any user name) and fill in a 
> regular user's login name, Secure Shell refuses to allow that 
> connection and replies back "Access denied' and asks for the password 
> again and again, and again. Never allowing the connection.
>
> The same thing happens if I fill in 'root' as the login even though a 
> 'root' login is not permitted in the default 'sshd_config' 
> configuration.  Even when I change the configuration to allow for 
> 'root' login, 'root' can never login.
>
> Has anyone run into this behavior before or know about a fix for this 
> problem.  I have formatted, installed, reinstalled and Googled so many 
> times that I many be going crazy.
>
> Keith
>

[toc] | [prev] | [next] | [standalone]

#212710

[Multipart message — attachments visible in raw view] — view raw

On Lu, 12 aug 19, 08:23:17, Keith Steensma wrote:
> I've installed both Version 9.9 (OldStable) and 'Buster' (Stable) and found
> that both version seem to have the same problem.  It's like I'm doing
> something wrong.  But these are fresh installs - no modification.
> 
> With Secure Shell server installed and running on port 22 (or any other port
> of your choice) and iptable Chain Input and Output Policy Accept All.  When
> I try to connect from a Windows machine using 'putty' (without letting
> 'putty' fill in any user name) and fill in a regular user's login name,
> Secure Shell refuses to allow that connection and replies back "Access
> denied' and asks for the password again and again, and again. Never allowing
> the connection.

Can you login with the same user locally 'ssh localhost'?

If you try entering the password in the username field (don't press 
enter so it's not logged) does it show as you expect it?


Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

[toc] | [prev] | [next] | [standalone]

#212713

On 12/8/19 11:23 pm, Keith Steensma wrote:
>
> The same thing happens if I fill in 'root' as the login even though a 
> 'root' login is not permitted in the default 'sshd_config' 
> configuration.  Even when I change the configuration to allow for 
> 'root' login, 'root' can never login.
>
>


Try a local ssh login to see if it rules out network problems. As in ssh localhost.  or ssh -l <user> localhost. If it is your network getting in the way it may
rule that out.

-- 
The gene pool could use a little chlorine...

[toc] | [prev] | [next] | [standalone]

#212744

[Multipart message — attachments visible in raw view] — view raw

On Tue, Aug 13, 2019 at 08:23:35AM -0500, Keith Steensma wrote:
> 
> 
> On 8/12/2019 4:00 PM, elvis wrote:
> >On 12/8/19 11:23 pm, Keith Steensma wrote:
> >>
> >>The same thing happens if I fill in 'root' as the login even
> >>though a 'root' login is not permitted in the default
> >>'sshd_config' configuration.  Even when I change the
> >>configuration to allow for 'root' login, 'root' can never login.
> >>
> >>
> >
> >
> >Try a local ssh login to see if it rules out network problems. As
> >in ssh localhost.  or ssh -l <user> localhost. If it is your
> >network getting in the way it may
> >rule that out.
> >
> Yes that works ( ssh -l <user> localhost ).  So that means it has to
> do with the network connections.

Not necessarily. It can be the client, too (your PuTTY). You didn't
describe the error message in detail (perhaps it is too unspecific,
GUI clients tend to be like that), but perhaps PuTTY has some
"verbose" option you can activate. Then you may infer whether there's
a hole in the net or whether just client and server don't get along
with each other.

Cheers
-- tomás

[toc] | [prev] | [next] | [standalone]

#212751

On Tue, 13 Aug 2019 15:28:04 +0200
<tomas@tuxteam.de> wrote:

> On Tue, Aug 13, 2019 at 08:23:35AM -0500, Keith Steensma wrote:
> > 
> > 
> > On 8/12/2019 4:00 PM, elvis wrote:  
> > >On 12/8/19 11:23 pm, Keith Steensma wrote:  
> > >>
> > >>The same thing happens if I fill in 'root' as the login even
> > >>though a 'root' login is not permitted in the default
> > >>'sshd_config' configuration.  Even when I change the
> > >>configuration to allow for 'root' login, 'root' can never login.
> > >>
> > >>  
> > >
> > >
> > >Try a local ssh login to see if it rules out network problems. As
> > >in ssh localhost.  or ssh -l <user> localhost. If it is your
> > >network getting in the way it may
> > >rule that out.
> > >  
> > Yes that works ( ssh -l <user> localhost ).  So that means it has to
> > do with the network connections.  
> 
> Not necessarily. It can be the client, too (your PuTTY). You didn't
> describe the error message in detail (perhaps it is too unspecific,
> GUI clients tend to be like that), but perhaps PuTTY has some
> "verbose" option you can activate. Then you may infer whether there's
> a hole in the net or whether just client and server don't get along
> with each other.
> 

It is some years since I used PuTTY regularly, but I seem to recall
that it didn't use OpenSSH-type keys and insisted on generating its own
and providing a conversion to an OpenSSH key, which then had to be
placed on the server. Is it possible this procedure may have gone amiss,
or perhaps it is willing to use OpenSSH keys now?

-- 
Joe

[toc] | [prev] | [next] | [standalone]

#212752

On 13/08/2019 16:31, Joe wrote:
> On Tue, 13 Aug 2019 15:28:04 +0200
> <tomas@tuxteam.de> wrote:
>
>> On Tue, Aug 13, 2019 at 08:23:35AM -0500, Keith Steensma wrote:
>>>
>>> On 8/12/2019 4:00 PM, elvis wrote:
>>>> On 12/8/19 11:23 pm, Keith Steensma wrote:
>>>>> The same thing happens if I fill in 'root' as the login even
>>>>> though a 'root' login is not permitted in the default
>>>>> 'sshd_config' configuration.  Even when I change the
>>>>> configuration to allow for 'root' login, 'root' can never login.
>>>>>
>>>>>   
>>>>
>>>> Try a local ssh login to see if it rules out network problems. As
>>>> in ssh localhost.  or ssh -l <user> localhost. If it is your
>>>> network getting in the way it may
>>>> rule that out.
>>>>   
>>> Yes that works ( ssh -l <user> localhost ).  So that means it has to
>>> do with the network connections.
>> Not necessarily. It can be the client, too (your PuTTY). You didn't
>> describe the error message in detail (perhaps it is too unspecific,
>> GUI clients tend to be like that), but perhaps PuTTY has some
>> "verbose" option you can activate. Then you may infer whether there's
>> a hole in the net or whether just client and server don't get along
>> with each other.
>>
> It is some years since I used PuTTY regularly, but I seem to recall
> that it didn't use OpenSSH-type keys and insisted on generating its own
> and providing a conversion to an OpenSSH key, which then had to be
> placed on the server. Is it possible this procedure may have gone amiss

This has happened to me a couple of times. Regenerating and converting 
solved the problem.

-- 
Mike Howard

[toc] | [prev] | [next] | [standalone]

#212755

On 8/13/2019 11:35 AM, Michael Howard wrote:
> On 13/08/2019 16:31, Joe wrote:
>> On Tue, 13 Aug 2019 15:28:04 +0200
>> <tomas@tuxteam.de> wrote:
>>
>>> On Tue, Aug 13, 2019 at 08:23:35AM -0500, Keith Steensma wrote:
>>>>
>>>> On 8/12/2019 4:00 PM, elvis wrote:
>>>>> On 12/8/19 11:23 pm, Keith Steensma wrote:
>>>>>> The same thing happens if I fill in 'root' as the login even
>>>>>> though a 'root' login is not permitted in the default
>>>>>> 'sshd_config' configuration.  Even when I change the
>>>>>> configuration to allow for 'root' login, 'root' can never login.
>>>>>>
>>>>>
>>>>> Try a local ssh login to see if it rules out network problems. As
>>>>> in ssh localhost.  or ssh -l <user> localhost. If it is your
>>>>> network getting in the way it may
>>>>> rule that out.
>>>> Yes that works ( ssh -l <user> localhost ).  So that means it has to
>>>> do with the network connections.
>>> Not necessarily. It can be the client, too (your PuTTY). You didn't
>>> describe the error message in detail (perhaps it is too unspecific,
>>> GUI clients tend to be like that), but perhaps PuTTY has some
>>> "verbose" option you can activate. Then you may infer whether there's
>>> a hole in the net or whether just client and server don't get along
>>> with each other.
>>>
>> It is some years since I used PuTTY regularly, but I seem to recall
>> that it didn't use OpenSSH-type keys and insisted on generating its own
>> and providing a conversion to an OpenSSH key, which then had to be
>> placed on the server. Is it possible this procedure may have gone amiss
>
> This has happened to me a couple of times. Regenerating and converting 
> solved the problem.
It may be wrong, but I'm using putty where putty does not supply a 
username or a 'key'.  I'm using it just as
a terminal (does someone have an alternate suggestion).  I agree, putty 
gets along with OpenSSH is a
  'almost' fashion.  If you convert your 'key' in the right way.  I have 
been using mine a long time just because
it takes a while to get it to work correctly.

[toc] | [prev] | [next] | [standalone]

#212756

On 8/13/2019 7:40 PM, Keith Steensma wrote:
>
>
> On 8/13/2019 11:35 AM, Michael Howard wrote:
>> On 13/08/2019 16:31, Joe wrote:
>>> On Tue, 13 Aug 2019 15:28:04 +0200
>>> <tomas@tuxteam.de> wrote:
>>>
>>>> On Tue, Aug 13, 2019 at 08:23:35AM -0500, Keith Steensma wrote:
>>>>>
>>>>> On 8/12/2019 4:00 PM, elvis wrote:
>>>>>> On 12/8/19 11:23 pm, Keith Steensma wrote:
>>>>>>> The same thing happens if I fill in 'root' as the login even
>>>>>>> though a 'root' login is not permitted in the default
>>>>>>> 'sshd_config' configuration.  Even when I change the
>>>>>>> configuration to allow for 'root' login, 'root' can never login.
>>>>>>>
>>>>>>
>>>>>> Try a local ssh login to see if it rules out network problems. As
>>>>>> in ssh localhost.  or ssh -l <user> localhost. If it is your
>>>>>> network getting in the way it may
>>>>>> rule that out.
>>>>> Yes that works ( ssh -l <user> localhost ).  So that means it has to
>>>>> do with the network connections.
>>>> Not necessarily. It can be the client, too (your PuTTY). You didn't
>>>> describe the error message in detail (perhaps it is too unspecific,
>>>> GUI clients tend to be like that), but perhaps PuTTY has some
>>>> "verbose" option you can activate. Then you may infer whether there's
>>>> a hole in the net or whether just client and server don't get along
>>>> with each other.
>>>>
>>> It is some years since I used PuTTY regularly, but I seem to recall
>>> that it didn't use OpenSSH-type keys and insisted on generating its own
>>> and providing a conversion to an OpenSSH key, which then had to be
>>> placed on the server. Is it possible this procedure may have gone amiss
>>
>> This has happened to me a couple of times. Regenerating and converting
>> solved the problem.
> It may be wrong, but I'm using putty where putty does not supply a
> username or a 'key'.  I'm using it just as
> a terminal (does someone have an alternate suggestion).  I agree, putty
> gets along with OpenSSH is a
>  'almost' fashion.  If you convert your 'key' in the right way.  I have
> been using mine a long time just because
> it takes a while to get it to work correctly.
>

I don't understand how you are connecting to your server if you don't
use username/pwd or identityfile and what do you mean by "terminal"?

In this thread, some putty alternative were suggested if that is what
you are asking.

--
John Doe

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | linux.debian.user

csiph-web