OpenSSH 3.7 testing (Re: 3.6p1 bug on SCO OpenServer)
mouring at etoh.eviladmin.org
Sat Sep 6 15:47:14 EST 2003
On this note I think it would be best to opening the floor for testing of
the current CVS tree. OpenSSH is in a feature lock and we should be in
in sync with the OpenBSD tree (there may be stray patches, but hopefully
So please if we can get people to start doing tests on their platform is
The major things that have changed is PAM and Kerb/GSS support. However,
we did do a clean up of openbsd-compat/ code so I may have broken
platforms I don't own by playing in there. I also redid how we handle
signal (signal() vs a stricter mysignal() version). So that is something
to watch out for (basicly made it consistant).
There are a bunch more changes, but I don't have a copy of the proposed
release notes sitting in front of me.
BTW, regression testing should hopefully work for most platforms. Please
get in the habbit of using this. It should give us a better handle on
platform breakage. Darren was nice enough to get that rolling recently.
It should be as simple as ./configure [needed options] && make && make
tests, but I've not had a chance to confirm it with an actually test on my
Solaris test box.
Sooooo... If you wish your platform to work then drop by
http://www.openssh.com/portable.html, pick your favorate ftp server
or grab the the source from the CVS tree.
- Ben && The OpenSSH Portable Team
On Fri, 5 Sep 2003, Tim Rice wrote:
> On Sat, 6 Sep 2003, Darren Tucker wrote:
> > Roger Cornelius wrote:
> > > loginrec.c writes incorrect data into the ut_id field of the utmp file.
> > > This has been an issue since at least openssh 3.0.2 but I never bothered
> > > to report it. For Openssh 3.6p1, defining WITH_ABBREV_NO_TTY corrects
> > > the problem.
> > [snip]
> > Are you talking about "*-*-sco3.2v4*" or "*-*-sco3.2v5*" or both?
> My 3.2v4.2 box is dead. Can someone check the last(C) output here?
> > Tim, any issue with doing this?
> I've verified the complaint. As soon as I can get "current" to build 
> on OpenServer I'll test the fix.
> 1. ssh-keygen.c uses PATH_MAX now.
> No source file used PATH_MAX in openssh-3.6.1
> More to do this weekend. ;-)
> Tim Rice Multitalents (707) 887-1469
> tim at multitalents.net
> openssh-unix-dev mailing list
> openssh-unix-dev at mindrot.org
More information about the openssh-unix-dev