>On Monday, 30 November 2015, 8:17, Bill Damage wrote:
Sorry to be a pain here but this is still broken. Any more ideas for info I can
supply please?
I also read the link you sent which prompted me to run the query:
~]# ssh -G nx
user root
hostname nx
port 22
addressfamily any
batchmode no
canonicalizefallbacklocal yes
canonicalizehostname false
challengeresponseauthentication yes
checkhostip yes
compression no
controlmaster false
I meant the log for the SSH server, on the machine you are trying to
connect to, not the nx log. On the SSH server, run
grep sshd /var/log/messages
Here it is:
Nov 29 11:07:18 tiger kernel: audit: type=1109 audit(1448795238.479:95):
pid=12140 uid=0 auid=4294967295 ses=4294967295 msg='op=P
November 2015, 12:33, Neil Bothwick wrote:
On Sat, 28 Nov 2015 10:24:32 + (UTC), Bill Damage wrote:
> The log I see says its not using the password but the key. I have
> regenerated the key but it didn't help. This setup has been fine for
> years. Could there be key *types* which
gt; 204 Authentication failed.
On Friday, 27 November 2015, 9:10, Peter Humphrey wrote:
On Thursday 26 November 2015 21:39:57 Bill Damage wrote:
> Is this better? Damn Yahoo webmail...
Yes, it's fine.
--
Rgds
Peter
Thanks.
I want root to be able to SSH in, so I commented out the "without-password"
one, but it made no difference.
On Thursday, 26 November 2015, 23:59, Neil Bothwick wrote:
On Thu, 26 Nov 2015 21:39:57 +0000 (UTC), Bill Damage wrote:
> PermitRootLogin yes
[snip]
>
Is this better? Damn Yahoo webmail...
My /var/log/nx/nxserver.log remains at 0 bytes even though in node.conf I set
NX_LOG_LEVEL to 6 from 0.
Anyway, I will dump my sshd_config for completeness:
[root@example~]# cat /etc/ssh/sshd_config
# $OpenBSD: sshd_config,v 1.84 2011/05/23 03:30:07
On Thursday, 26 November 2015, 9:51, Peter Humphrey
wrote:
I would need a magnifying glass to read this. Please don't use HTML on this
list.
It's damn Yahoos webmail, I switched to plain text maybe it's better now?
Anyway the log at /var/log/nx/nxserver.log is always 0 bytes.
Somehow the details of my message wasn't posted:
NX> 203 NXSSH running with pid: 10200NX> 285 Enabling check on switch
commandNX> 285 Enabling skip of SSH config filesNX> 285 Setting the preferred
NX optionsNX> 200 Connected to address: 192.168.62.4 on port: 22NX> 202
Authenticating user: nxNX>
Thanks, but either way I'm still getting nowhere:
NX> 203 NXSSH running with pid: 9904NX> 285 Enabling check on switch commandNX>
285 Enabling skip of SSH config filesNX> 285 Setting the preferred NX
optionsNX> 200 Connected to address: 192.168.62.4 on port: 22NX> 202
Authenticating user: nxNX>
I have exactly the same problem mentioned in this thread. I think something
changed and broke the authentication during an update. i found this message by
Googling and just joined the mail list to ask for help. I have done everything
mentioned in the thread, and here's where I'm at: (it worked f
11 matches
Mail list logo
