openssh bugs - Sep 2003 - [Bug 657] Priv seperation causes setreuid error

http://bugzilla.mindrot.org/show_bug.cgi?id=657

dtucker at zip.com.au changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Priv seperation causes      |Priv seperation causes
                   |segfault                    |setreuid error



------- Additional Comments From dtucker at zip.com.au  2003-09-18 09:20 -------
Try adding:
#define SETEUID_BREAKS_SETUID 1
#define BROKEN_SETREUID 1
#define BROKEN_SETREGID 1

to your config.h and recompiling (don't re-run configure)



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=657

mgamble at eol.ca changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED



------- Additional Comments From mgamble at eol.ca  2003-09-18 10:17 -------
That fixed it.  Perhaps that should be noted somewhere?  Perhaps a README.BSDi 
file?



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=657

dtucker at zip.com.au changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |



------- Additional Comments From dtucker at zip.com.au  2003-09-18 11:33 -------
The bug shouldn't be closed until we fix configure to automatically define
those.  What does configure report for the "system type" for your BSDi
box?



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=657

dtucker at zip.com.au changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jsr at dexter.mi.org



------- Additional Comments From dtucker at zip.com.au  2003-09-18 11:40 -------
*** Bug 674 has been marked as a duplicate of this bug. ***



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=657





------- Additional Comments From markus at openbsd.org  2003-09-18 23:49 -------
it should be this:


              Host: i386-pc-bsdi4.3.1

same for other bsd/os versions. e.g 4.3, 4.2, 4.0.2
and probably 5.0, but i did not test.




------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=657





------- Additional Comments From markus at openbsd.org  2003-09-18 23:57 -------
bsdos 5.0  (all patches) needs the same defines.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=657





------- Additional Comments From root at nk.ca  2003-09-19 02:05 -------
Here is what I am getting

1) doctor.nl2k.ab.ca//etc/mail$ sshd -d -d -d
debug2: read_server_config: filename /usr/contrib/etc/sshd_config
debug1: sshd version OpenSSH_3.7.1p1
debug1: private host key: #0 type 0 RSA1
debug3: Not a RSA1 key file /usr/contrib/etc/ssh_host_rsa_key.
debug1: read PEM private key done: type RSA
debug1: private host key: #1 type 1 RSA
debug3: Not a RSA1 key file /usr/contrib/etc/ssh_host_dsa_key.
debug1: read PEM private key done: type DSA
debug1: private host key: #2 type 2 DSA
debug1: setgroups() failed: Invalid argument
debug1: Bind to port 22 on ::.
debug1: Bind to port 22 on 0.0.0.0.
Bind to port 22 on 0.0.0.0 failed: Address already in use.
Cannot bind any address.
You have new mail in /var/mail/root
doctor.nl2k.ab.ca//etc/mail$

2)  doctor.nl2k.ab.ca/~$less typescriot
typescriot: No such file or directory
doctor.nl2k.ab.ca/~$less typescript
Script started on Wed Sep 17 06:20:55 2003
doctor.nl2k.ab.ca/~$ssh -v -2 -i ~doctor/.ssh/id_rsa -l doctor uucp
OpenSSH_3.7.1p1, SSH protocols 1.5/2.0, OpenSSL 0.9.6j [engine] 10 Apr 2003
debug1: Reading configuration data /usr/contrib/etc/ssh_config^M
debug1: Connecting to uucp [204.209.81.3] port 22.^M
debug1: Connection established.^M
debug1: identity file /usr/home/doctor/.ssh/id_rsa type 1^M
debug1: Remote protocol version 1.99, remote software version OpenSSH_3.7.1p1^M
debug1: match: OpenSSH_3.7.1p1 pat OpenSSH*^M
debug1: Enabling compatibility mode for protocol 2.0^M
debug1: Local version string SSH-2.0-OpenSSH_3.7.1p1^M
debug1: SSH2_MSG_KEXINIT sent^M
Connection closed by 204.209.81.3^M
debug1: Calling cleanup 0x80608b0(0x0)^M
doctor.nl2k.ab.ca/~$exit
exit

Script done on Wed Sep 17 06:21:34 2003




------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=657





------- Additional Comments From dtucker at zip.com.au  2003-09-19 21:16 -------
Created an attachment (id=435)
 --> (http://bugzilla.mindrot.org/attachment.cgi?id=435&action=view)
Add defines to configure.ac for BSDi

Please try the attached patch.	You will need to run autoconf to rebuild
configure.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=657

dtucker at zip.com.au changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|                            |FIXED



------- Additional Comments From dtucker at zip.com.au  2003-09-22 11:22 -------
Thanks for the report.  This has been fixed (both in HEAD and the 3.7 branch). 
Please try tomorrow's snapshot (which you can get from one of the mirrors)
and
see if it works correctly out-of-the-box.

http://www.openssh.com/portable.html#mirrors



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.