Bug#241996:

2004-04-04 Thread Ronny Vaningh
Package: libc6.1
Version: 2.3.2.ds1-11

I cannot ssh to the box anymore after upgrading libc
Running sshd in debug results in
 
debug1: permanently_set_uid: 100/65534
setresgid 65534: Function not implemented
debug1: do_cleanup

I have the same package versions of libC and ssh on a alpha box running
a 2.4 kernel, without encountering any problems


-- System Information:
Debian Release: testing/unstable
Architecture: alpha
Kernel:  2.2.20 #2 Wed Mar 20 19:57:28 EST 2002 alpha GNU/Linux


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#241996:

2004-04-04 Thread Colin Watson
On Sun, Apr 04, 2004 at 10:18:12AM +0200, Ronny Vaningh wrote:
 Package: libc6.1
 Version: 2.3.2.ds1-11
 
 I cannot ssh to the box anymore after upgrading libc
 Running sshd in debug results in
  
 debug1: permanently_set_uid: 100/65534
 setresgid 65534: Function not implemented
 debug1: do_cleanup
 
 I have the same package versions of libC and ssh on a alpha box running
 a 2.4 kernel, without encountering any problems

I think this is bug #23, which I'll be fixing in openssh shortly.

However, I'm interested that it occurred following a libc6.1 upgrade.
What version of libc6.1 did you have beforehand?

-- 
Colin Watson  [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#241996:

2004-04-04 Thread Colin Watson
reassign 241996 ssh
severity 241996 important
merge 23 241996
thanks

On Sun, Apr 04, 2004 at 05:56:18PM +0200, Ronny Vaningh wrote:
 I was quite sure that I saw libc mentioned as an updated package some
 days ago ...
 
 I keep the box up to date with apt quite regulary
 
 The funky thing is that I upgraded the kernel to the 2.4.25 (-1-generic
 as packaged) and that this seemed to solve my ssh problem as well.

Yes, that's not surprising at all. The problem is ssh not coping
gracefully with the setresuid() and setresgid() system calls being
missing, and they aren't missing in 2.4.25.

I was wondering why this failure seemed to be new, but the use of
setres[ug]id() is new in OpenSSH 3.7, which would explain it. I bet the
upgrade you noticed also included an upgrade from ssh 3.6-* to 3.8-*.

Normally I'd request that glibc provide compatibility stubs, but I don't
think that's possible for setres[ug]id(), so ssh just has to deal with
it.

 We have another box with the same architecture (norritake) running 
 testing and had no problems with the ssh on the box, but this one was
 already running a 2.4 kernel for a long time
 
 I know this is not what I would call sufficient info ... sorry

Oh well; thanks anyway.

Cheers,

-- 
Colin Watson  [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Processed: Re: Bug#241996:

2004-04-04 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 reassign 241996 ssh
Bug#241996: 
Bug reassigned from package `libc6.1' to `ssh'.

 severity 241996 important
Bug#241996: 
Severity set to `important'.

 merge 23 241996
Bug#23: Read from socket failed on Alpha
Bug#241996: 
Merged 23 241996.

 thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]