sshd segfaults after applying OpenBSD 5.7 errata 9

2015-06-13 Thread Jacob Vosmaer
Hi, I pulled in the latest changes into /usr/src with 'cvs -q up -rOPENBSD_5_7 -Pd' and recompiled libcrypto and smtpd. After a reboot I got in trouble because a number of daemons were segfaulting: sshd, smtpd, unbound. Luckily I have a serial console to get into my server (a Soekris net6501-50).

Re: sshd segfaults after applying OpenBSD 5.7 errata 9

2015-06-13 Thread Jacob Vosmaer
I discovered sendbug and submitted this issue to b...@openbsd.org. 2015-06-13 19:51 GMT+02:00 Jacob Vosmaer cont...@jacobvosmaer.nl: Hi, I pulled in the latest changes into /usr/src with 'cvs -q up -rOPENBSD_5_7 -Pd' and recompiled libcrypto and smtpd. After a reboot I got in trouble

Re: sshd segfaults after applying OpenBSD 5.7 errata 9

2015-06-13 Thread Miod Vallat
I am now trying to revert errata 9 and recompile libcrypto to see if I get a usable system back. (This is a fun breakage, curl is no longer working for instance.) If think I will move o to bsd.rd. You can use ftp(1) instead of curl. In the hubbub around OpenSSL 1.0.1n I read there was a

Re: sshd segfaults after applying OpenBSD 5.7 errata 9

2015-06-13 Thread Jacob Vosmaer
2015-06-13 21:42 GMT+02:00 Jacob Vosmaer cont...@jacobvosmaer.nl: I suppose I could empty /usr/src, unpack the 5.7 tarballs, apply errata 9 and see what happens. That way CVS is not in the picture. OK, looks like this was CVS user error. Removing /usr/src, untarring the 5.7 source tarballs,