Bug 31457
| Summary: | OpenSSH 2.9 login(1) support broken | ||
|---|---|---|---|
| Product: | Base System | Reporter: | Ryan Beasley <ryanb> |
| Component: | bin | Assignee: | freebsd-bugs (Nobody) <bugs> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | 4.4-STABLE | ||
| Hardware: | Any | ||
| OS: | Any | ||
dwmalone committed a patch in version 1.4.2.10. Feel free to close
this report out. <g>
--
ryan beasley <ryanb@goddamnbastard.org>
professional fat bastard http://www.goddamnbastard.org
GPG Key ID 0x36321D13 with fingerprint
2074 CEB8 68AD 351A 85E6 98EB 09BA 36D9 3632 1D13
State Changed From-To: open->closed Patch committed in both -current and -stable. (Sorry I didn't notice this PR when I was committing the patch.) |
When UseLogin is set to 1 in sshd(8)'s config, all login attempts without a command to execute remotely cause the sshd child process to catch SIGSEGV and most likely dump core. Peeking at such a dump, we find a problem in the code that handles setting up the user's environment. Please the check the following URL for what I think is useful debugging info. http://www.freebsd.org/cgi/getmsg.cgi?fetch=547458+0+/usr/local/www/db/text/2001/freebsd-stable/20011021.freebsd-stable Fix: I'm going to look into this again in the near future, but I have no idea whatsoever. How-To-Repeat: Easy. Set UseLogin to yes in your sshd configuration and start the daemon. Follow that up with a standard SSH login: server: backup client: akerfeldt > [ryanb@akerfeldt ~] $ date > Tue Oct 23 12:38:34 CDT 2001 > [ryanb@akerfeldt ~] $ ssh backup > ryanb@backup's password: > Connection to backup closed. > > Oct 23 12:38:37 backup /kernel: pid 20327 (sshd), uid 0: exited on signal 11 (core dumped)