similar to: OpenSSH Portable Tinderbox available to test.

Hi All. I (actually the tinderbox[1]) found a problem with the fix for bug #422: when PAM is enabled on a platform that uses /etc/shadow, the variable "passwd" in auth.c is used uninitialized. There's a simple patch attached to fix this. The question is: should the locked account test be done when PAM is enabled or should we rely on PAM to do the right thing? In theory they

The Cray and tru64 patches I have, have been applied. Unless there is any major "oh my god it does not work". I believe 3.6 should now be ready for release soon. I'd like to thank everyone for providing feedback on the status of their their platform. Hopefully, we have not missed any platform that is commonly used. - Ben

Hi All, After finding out my AIX boxes haven't been updating their tinderbox[0] test trees (grr) and fixing that, I found that recent changes caused build errors on AIX 4.3.3 & 5.1. 4.2.1 appears OK. The error is: gcc -g -O2 -Wall -Wpointer-arith -Wno-uninitialized -I. -I.. -I../../openbsd-compat -I../../openbsd-compat/.. -I/usr/local/ssl/include -I/usr/local/include -DHAVE_CONFIG_H

Hi All. Damien merged a bunch of changes today which caused compile errors on a few platforms (which you can see live and in colour at [0]). a) Solaris, early AIX: ../crc32.c:100: `u_int32_t? undeclared (first use in this function) On these platforms u_int32_t is defined in defines.h which is not included by crc32.c. Fixed by attached patch. b) PAM platforms (Redhat, Solaris once a) is

http://www.mindrot.org/~djm/openssh/openssh-newpam-20030123.tar.gz Is a snapshot of the new PAM-via-KbdInt authentication support from FreeBSD's OpenSSH tree. Please test this now. I can only surmise by the silence that has greeted my previous requests for testing that the code works perfectly. -d

There are a couple of noteworthy changes in tonight's snapshot: 1. New UsePAM directive There is a new sshd_config directive, UsePAM for systems built using "configure --with-pam". This allows one to switch off all PAM calls from sshd. This is handy if one builds with PAM but wants to use the sshd's ability to run as a non-root user. Previously this was impossible if one

Hi All. The recent changes to scp caused build failures on Solaris and AIX 4.2 which showed up on the tinderbox[1]. I mentioned the first to djm in email yesterday but I'm posting after finding the second, in case anyone else has seen similar problems. Solaris' nanosleep is in librt (or libposix4 in older versions) which is not linked. Adding them to configure works fine, however ldd

Hi All. There are still build errors for scp on AIX 4.2.1 due to lack of nanosleep (which you can see them live and in colour at [1]). The attached patch fixes this by using the equivalent nsleep function on AIX if it exists and nanosleep doesn't. The patch is mostly the same as the AIX portion of the previous patch for the nanosleep issue, the major difference being that the #define is in

TB --- 2008-07-29 09:37:14 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2008-07-29 09:37:14 - starting RELENG_7 tinderbox run for sparc64/sparc64 TB --- 2008-07-29 09:37:14 - cleaning the object tree TB --- 2008-07-29 09:37:32 - cvsupping the source tree TB --- 2008-07-29 09:37:32 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/sparc64/sparc64/supfile TB ---

TB --- 2003-08-09 16:00:12 - starting RELENG_4 tinderbox run for i386/pc98 TB --- 2003-08-09 16:00:12 - checking out the source tree TB --- cd /home/des/tinderbox/RELENG_4/i386/pc98 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_4 src TB --- 2003-08-09 16:00:12 - /usr/bin/cvs returned exit code 1 TB --- 2003-08-09 16:00:12 - ERROR: unable to check out the source tree TB ---

http://tinderbox.x.org/builds/2008-07-08-0003/ http://tinderbox.x.org/builds/2008-07-08-0003/logs/xf86-video-nouveau/#build nouveau_bo.c: In function 'nouveau_bo_new': nouveau_bo.c:51: error: 'NOUVEAU_MEM_TILE' undeclared (first use in this function) nouveau_bo.c:51: error: (Each undeclared identifier is reported only once nouveau_bo.c:51: error: for each function it appears in.)

TB --- 2008-08-27 11:26:00 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2008-08-27 11:26:00 - starting RELENG_7 tinderbox run for amd64/amd64 TB --- 2008-08-27 11:26:00 - cleaning the object tree TB --- 2008-08-27 11:26:30 - cvsupping the source tree TB --- 2008-08-27 11:26:30 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/amd64/amd64/supfile TB --- 2008-08-27

TB --- 2008-06-03 08:42:30 - tinderbox 2.3 running on freebsd-legacy.sentex.ca TB --- 2008-06-03 08:42:30 - starting RELENG_6 tinderbox run for i386/i386 TB --- 2008-06-03 08:42:30 - cleaning the object tree TB --- 2008-06-03 08:43:09 - cvsupping the source tree TB --- 2008-06-03 08:43:09 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_6/i386/i386/supfile TB --- 2008-06-03 08:43:22

TB --- 2013-11-19 23:00:41 - tinderbox 2.20 running on worker01.tb.des.no TB --- 2013-11-19 23:00:41 - FreeBSD worker01.tb.des.no 9.1-RELEASE-p4 FreeBSD 9.1-RELEASE-p4 #0: Mon Jun 17 11:42:37 UTC 2013 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-11-19 23:00:41 - starting RELENG_10 tinderbox run for sparc64/sparc64 TB --- 2013-11-19 23:00:41 - cleaning the

TB --- 2013-11-13 13:00:41 - tinderbox 2.20 running on worker01.tb.des.no TB --- 2013-11-13 13:00:41 - FreeBSD worker01.tb.des.no 9.1-RELEASE-p4 FreeBSD 9.1-RELEASE-p4 #0: Mon Jun 17 11:42:37 UTC 2013 root at amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-11-13 13:00:41 - starting RELENG_10 tinderbox run for i386/i386 TB --- 2013-11-13 13:00:41 - cleaning the

TB --- 2012-12-04 23:10:18 - tinderbox 2.9 running on freebsd-legacy2.sentex.ca TB --- 2012-12-04 23:10:18 - FreeBSD freebsd-legacy2.sentex.ca 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 root at farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-12-04 23:10:18 - starting RELENG_8 tinderbox run for sparc64/sparc64 TB --- 2012-12-04 23:10:18 - cleaning

On the one hand, yes, they're about things most readers can't do anything about. On the other hand, they do let you know (once the tinderbox has stabilized, this being a new setup with the bugs being worked out of it) whether recent -STABLE will build or not, which can be quite useful even for ordinary users of -STABLE. (You know to hold off on updating if it's failing for your

TB --- 2013-02-26 21:23:55 - tinderbox 2.10 running on freebsd-stable.sentex.ca TB --- 2013-02-26 21:23:55 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012 mdtancsa at freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2013-02-26 21:23:55 - starting RELENG_9 tinderbox run for arm/arm TB --- 2013-02-26 21:23:55 - cleaning the

TB --- 2003-08-09 16:00:11 - starting RELENG_4 tinderbox run for i386/i386 TB --- 2003-08-09 16:00:11 - checking out the source tree TB --- cd /home/des/tinderbox/RELENG_4/i386/i386 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_4 src TB --- 2003-08-09 16:00:11 - /usr/bin/cvs returned exit code 1 TB --- 2003-08-09 16:00:11 - ERROR: unable to check out the source tree TB ---

We've lost tinderbox (last build 25th), which is presumably why the following wasn't caught: ---------------------------------------------------------------------- /s1/james/projects/xapian/xapian/xapian-core/extra/queryparser.yy: In function `int yylex()': /s1/james/projects/xapian/xapian/xapian-core/extra/queryparser.yy:443: `class std::basic_string<char,