I can't figure out what causes this error.
I can "fix" it by regenerating the server key on the system I'm trying
to connect to and restarting sshd but that seems to be temporary as the
same problem comes back in a week or so. Rebooting the server does not
fix it.
Does anyone know what that
What does the output of
ssh -vv
give you?
and what does /var/log/secure say on the server side?
Permission denied could be a number of things (time not in sync,
PAM configuration right, or other stuff. without knowing the
server and client sshd_config and ssh_config respectively it is hard to
Hi Joe,
Did you look at the sshd_config file?
I ran into a similar error output but it may not necessarily be the same
issue you're having. In my case, the sshd_conf file on one of my users
machine was edited and renamed. I backup that file and copy a default
sshd_config file, then test it.
Good
Thank you Tam, and Steven,
I just confirmed that regenerating the keys (ssh-keygen -t dsa -f
ssh_host_dsa_key && ssh -t rsa -f ssh_host_rsa_key) in /etc/ssh "fixes
the problem"
So ssh -vv shows me how it's supposed to look. I'll save that and do a
diff when it happens again.
As I continue
ux-us...@listserv.fnal.gov
[mailto:owner-scientific-linux-us...@listserv.fnal.gov] On Behalf Of Joseph
Areeda
Sent: Wednesday, November 21, 2012 5:46 PM
To: owner-scientific-linux-us...@listserv.fnal.gov
Cc: scientific-linux-users
Subject: Re: ssh returns "Permission denied (gssapi-keyex,gssapi-with-mic
f Of *Joseph
>> Areeda
>> *Sent:* Wednesday, November 21, 2012 5:46 PM
>> *To:* owner-scientific-linux-us...@listserv.fnal.gov
>> *Cc:* scientific-linux-users
>> *Subject:* Re: ssh returns "Permission denied
>> (gssapi-keyex,gssapi-with-mic)."
&g
er-scientific-linux-us...@listserv.fnal.gov>
*Cc:* scientific-linux-users
*Subject:* Re: ssh returns "Permission denied
(gssapi-keyex,gssapi-with-mic)."
Thank you Tam, and Steven,
I just confirmed that regenerating the keys (ssh-keygen -t dsa
On 22 November 2012 01:18, Joseph Areeda wrote:
>
> The user's directory is 755 which is the convention for grid computers in
> our collaboration and the plan is for this machine to be on our soon to be
> delivered cluster. The .ssh directory is 700. This doesn't change between
> the working and
On 11/21/2012 07:08 PM, Alan Bartlett wrote:
On 22 November 2012 01:18, Joseph Areeda wrote:
The user's directory is 755 which is the convention for grid computers in
our collaboration and the plan is for this machine to be on our soon to be
delivered cluster. The .ssh directory is 700. This
Well there is your problem
The users home directory needs to be 700 unless you turn off strict key
checking in the sshd configuration file. Also the public key should be 600
as well.
Making home directories world or group readable isn't a good plan for
collaberation because many applications store
Thanks for the comments Paul.
I was surprised when I joined the collaboration and saw home directories
world readable but that decision was made long before I arrived and
changing it remains above my pay grade.
The reason I doubt that's my current problem is because regenerating the
server k
Well this has been a thorn in my side for months but I think I've
figured it out. At least I found a plausible reason for it and it's
been working longer than it has before.
The problem turned out to be I had both gsisshd and sshd running and the
fix was to use chkconfig to disable it.
The
12 matches
Mail list logo
