On Thu, Oct 9, 2014 at 5:25 PM, Curt Lundgren verif...@gmail.com wrote:
All was well in Linux-land until yesterday when I added another host key to
.ssh/authorized_keys. It's running CentOS 6.5, a VM under VMware.
.ssh/ is owned by root:root. Its files are similarly owned and both
File and directory ownership and permissions are correct.
Normally I create (and expand, if necessary) the authorized_keys file by
doing a cat on the existing file, if any, and the new key file. This
doesn't add newlines, and none of these files have ever seen a Windows
system. I did a hex dump
We have another server that's identical except it's a physical machine,
it's working perfectly.
So what is working on that machine? is that the machine you can connect to
without issue, or is that the machine where the authorized_keys live and
you can ssh out of that box to others without a
If I remember right, the keys work independently, but not when concatenated
together? That smells like a missing EOL (in the first one). I don't think
ssh needs an EOL on the last line, but it definitely needs it in between
the public keys.
On Fri, Oct 10, 2014 at 10:35 AM, Wesley Duffee-Braun
I meant that the same version of CentOS is loaded on each machine and they
have nearly identical configurations and roles. On the 'working' machine I
simply did a cat with .ssh/authorized_keys and the new key file, changed
its permissions and moved it into the .ssh/ directory. Simple, sweet, and
Did you look at /var/log/secure on the sshd server to find out why it
was rejected?
On 10/9/14 6:25 PM, Curt Lundgren wrote:
All was well in Linux-land until yesterday when I added another host key
to .ssh/authorized_keys. It's running CentOS 6.5, a VM under VMware.
.ssh/ is owned by
Really, I should have thought of that. Sorry, no useful information there.
On Fri, Oct 10, 2014 at 10:36 AM, Drew from Zhrodague
drewzhroda...@zhrodague.net wrote:
Did you look at /var/log/secure on the sshd server to find out why
it was rejected?
On 10/9/14 6:25 PM, Curt
Sometimes you have to up your logging level in your config file for it to spit
out what you need. But 99% of the time looking at the secure/auth log file will
tell me what I've screwed up with the setup.
Kevin
Sent from my iPhone
On Oct 10, 2014, at 10:47 AM, Curt Lundgren
On 10/10/2014 10:47 AM, Curt Lundgren wrote:
Really, I should have thought of that. Sorry, no useful information there.
On Fri, Oct 10, 2014 at 10:36 AM, Drew from Zhrodague
drewzhroda...@zhrodague.net mailto:drewzhroda...@zhrodague.net wrote:
Did you look at /var/log/secure on
It's a high five and props to Howard! Talk about asleep at the prompt, I
never heard of ssh-copy-id before. It worked perfectly and now any of the
requisite (Python fans?) hosts can log in without the dreaded password
prompt.
The only problem with ssh-copy-id is that it's too easy and
On 10/10/2014 02:03 PM, Curt Lundgren wrote:
It's a high five and props to Howard! Talk about asleep at the prompt,
I never heard of ssh-copy-id before. It worked perfectly and now any of
the requisite (Python fans?) hosts can log in without the dreaded
password prompt.
The only problem with
Thanks to everyone who had suggestions. I have a new favorite command!
On Fri, Oct 10, 2014 at 1:24 PM, Howard White hwh...@vcch.com wrote:
On 10/10/2014 10:47 AM, Curt Lundgren wrote:
Really, I should have thought of that. Sorry, no useful information
there.
On Fri, Oct 10, 2014 at
All was well in Linux-land until yesterday when I added another host key to
.ssh/authorized_keys. It's running CentOS 6.5, a VM under VMware.
.ssh/ is owned by root:root. Its files are similarly owned and both
authorized_keys and known_hosts have 600 permissions.
OpenSSH is version 5.3p1.
expired certificates?
de-authorized key by some hacker?
firewall issue?
Yea, I am just fishing here.
On Thu, Oct 9, 2014 at 5:25 PM, Curt Lundgren verif...@gmail.com wrote:
All was well in Linux-land until yesterday when I added another host key to
.ssh/authorized_keys. It's running CentOS
Any individual key file works, so I don't think expiration is the issue.
Same answer for #2.
The servers are on the same subnet, so the firewall doesn't enter into the
picture.
Thanks, Jack.
On Thu, Oct 9, 2014 at 5:28 PM, Jack Coats j...@coats.org wrote:
expired certificates?
de-authorized
Ah ha! Remember those emails we've been getting about some certificate on
ns2 that was expiring? We didn't know what that certificate was used for.
Maybe it has something to do with this?
Chris
On Thu, Oct 9, 2014 at 5:33 PM, Curt Lundgren verif...@gmail.com wrote:
Any individual key file
On Thu, Oct 9, 2014 at 5:25 PM, Curt Lundgren verif...@gmail.com wrote:
All was well in Linux-land until yesterday when I added another host key
to .ssh/authorized_keys. It's running CentOS 6.5, a VM under VMware.
.ssh/ is owned by root:root. Its files are similarly owned and both
Yeah, I thought about that. I was using cat to produce the authorized_keys
file, like I generally do. I also tried doing a cat on each file
individually and pasting into Emacs. No difference.
On Thu, Oct 9, 2014 at 5:49 PM, Robert Wohlfarth rbwohlfa...@gmail.com
wrote:
On Thu, Oct 9, 2014 at
It's not the server keys. The recommendation I saw says remove all the key
files from /etc/ssh/ and restart SSHD. When I did this it regenerated the
keys, which were just over a year old. It's still asking for a password.
On Thu, Oct 9, 2014 at 5:50 PM, Curt Lundgren verif...@gmail.com wrote:
If this was 'winders' I would suspect bit rot. Can you retrieve the
appropriate key files from backup tapes from 'backwhen' things were
working?
--
--
You received this message because you are subscribed to the Google Groups
NLUG group.
To post to this group, send email to
Yeah, I can - but the additional host has to be there. It will make for an
interesting experiment in any case.
On Thu, Oct 9, 2014 at 6:00 PM, Jack Coats j...@coats.org wrote:
If this was 'winders' I would suspect bit rot. Can you retrieve the
appropriate key files from backup tapes from
21 matches
Mail list logo
