#250311 ssh: pubkey auth fails between 3.8.1p1-3 and 3.4(woody)

Package:
openssh-client
Source:
openssh
Description:
secure shell (SSH) client, for secure access to remote machines
Submitter:
Chad Walstrom
Date:
2015-03-16 15:12:05 UTC
Severity:
important
#250311#5
Date:
2004-05-22 01:47:52 UTC
From:
To:
I cannot connect to an ssh daemon running woody's current version
(1:3.4p1-1.woody.3) from the sarge/sid current version.  I have no
problems connecting to a client/server pair both running 3.8.1p1-3.
Default configuration files on all tests.

An example of where this hurts is when trying to get CVS repositories
from savannah.gnu.org.  Since they do not accept password authentication
and require publickey authentication, I cannot get read/write access to
the repositories.
#250311#10
Date:
2004-05-22 11:04:59 UTC
From:
To:
Hm, I do this all the time. I can connect to savannah.gnu.org from
1:3.8.1p1-3 using both i386 and powerpc and public key authentication.
What SSH protocol version are you using?

Can you get me ssh -vvv output, please?
#250311#15
Date:
2004-05-22 19:24:21 UTC
From:
To:
Colin Watson wrote:

I default to Protocol 2 in my .ssh/config file.

    # Chad's ssh configuration file
    #
    Protocol 2

Attached.
#250311#20
Date:
2004-07-21 04:52:10 UTC
From:
To:
I had precisely the same symptoms, with the same -vvv output.  Once
difference is that it only affected my connections to my own server,
not to savannah or sourceforge.

Looking at auth.log on my server revealed the problem: sshd was
refusing to use my public key because my home directory was
group-writable.  In order to do pubkey auth, both the home directory
and the .ssh directory must writable only by the owner.

I don't know if this is related to Chad's problem, but I thought I'd
mention it since the symptoms were so similar.

	Shawn.
#250311#23
Date:
2007-04-18 23:20:07 UTC
From:
To:
http://bugs.debian.org/250311
ssh: pubkey auth fails between 3.8.1p1-3 and 3.4(woody)

Please see the above URL; Shawn commented on the bug, but the bug number
(still) doesn't reach the submitter by default.  Is this problem solved?
#250311#28
Date:
2007-04-19 02:04:02 UTC
From:
To:
Justin Pryzby <justinpryzby@users.sourceforge.net>  wrote:

I honestly don't know.  It was reported so long ago.  The servers that
it could have affected have long since been upgraded.  I would
consider it close-able, even though the bug for those particular
versions may still be in effect.
#250311#35
Date:
2015-03-16 13:35:56 UTC
From:
To:
Notice to Appear,

You have to appear in the Court on the March 21.
You are kindly asked to prepare and bring the documents relating to the case to Court on the specified date.
Note: If you do not come, the case will be heard in your absence.

The Court Notice is attached to this email.

Regards,
Melvin Russo,
Court Secretary.