<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2653.12">
<TITLE>RE: Testing Call</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>I hope to have time to test, but I have a quick question:</FONT>
</P>
<P><FONT SIZE=2>I caught the message that PAM is working for some transactions, but the last patch I saw said that it still doesn't work for password changes. Did I miss a patch, or is that still broken? We've got to choose a new version to deploy enterprise-wide within the next week or two and I've got to decide if we want to wait for 3.5 or go with 3.2 which IIRC was the last version with a functional PAM.</FONT></P>
<P><FONT SIZE=2>Will it work if privsep is disabled and relavent sections of code uncommented?</FONT>
</P>
<P><FONT SIZE=2>Thanks in advance,</FONT>
<BR><FONT SIZE=2>--Jason</FONT>
</P>
<P><FONT SIZE=2>-----Original Message-----</FONT>
<BR><FONT SIZE=2>From: Ben Lindstrom [<A HREF="mailto:mouring@etoh.eviladmin.org">mailto:mouring@etoh.eviladmin.org</A>]</FONT>
<BR><FONT SIZE=2>Sent: Wednesday, July 17, 2002 3:04 PM</FONT>
<BR><FONT SIZE=2>To: OpenSSH Development</FONT>
<BR><FONT SIZE=2>Subject: Testing Call</FONT>
</P>
<BR>
<BR>
<P><FONT SIZE=2>Ok.. I'm starting official testing calls early this release. I'd like to</FONT>
<BR><FONT SIZE=2>have more feedback and more time for handling fixes.</FONT>
</P>
<P><FONT SIZE=2>If people could test snapshots (<A HREF="http://www.openssh.org/portable.html" TARGET="_blank">http://www.openssh.org/portable.html</A>, pick</FONT>
<BR><FONT SIZE=2>your favorate mirror and select snapshots directory) and report failures</FONT>
<BR><FONT SIZE=2>it would be useful.</FONT>
</P>
<P><FONT SIZE=2>For those with pmake install there is regress/ which you can try out. It</FONT>
<BR><FONT SIZE=2>may help any platform issues. I know some platforms will outright fail</FONT>
<BR><FONT SIZE=2>(AIX). Hopefully post 3.5 we can look at supplying gnu make files.</FONT>
</P>
<P><FONT SIZE=2>For those that build packages for yourself/others from the contrib/</FONT>
<BR><FONT SIZE=2>section also let us know what needs to be updated. With the changes to</FONT>
<BR><FONT SIZE=2>the Solaris/Sysv package that I think it needs to be retested on</FONT>
<BR><FONT SIZE=2>non-solaris platforms (Tim, do you still have Daz's last patch to</FONT>
<BR><FONT SIZE=2>buildpkg.sh so you could test under SCO or should I just commit it and we</FONT>
<BR><FONT SIZE=2>can play cvs tag?).</FONT>
</P>
<P><FONT SIZE=2>Known issues:</FONT>
</P>
<P><FONT SIZE=2>1. Tru64 (OSF/1) w/ SIA still is broken under Privsep. (For partial</FONT>
<BR><FONT SIZE=2>privsep support change config.h /* #undef DISABLE_FD_PASSING */ to #define</FONT>
<BR><FONT SIZE=2>DISABLE_FD_PASSING 1) If we can't come up with a solution by 3.5 release</FONT>
<BR><FONT SIZE=2>then I'll just set DISABLE_FD_PASSING for the 3.5 release.</FONT>
</P>
<P><FONT SIZE=2>The issue is how the SIA sessioning is getting horked. And without</FONT>
<BR><FONT SIZE=2>someone giving me a tru64 box or access (w/ root) for a few days it is</FONT>
<BR><FONT SIZE=2>pretty much never going to be fixed. Ya, I know.=) I hate touching other</FONT>
<BR><FONT SIZE=2>people's servers and even worse having root on them.</FONT>
</P>
<P><FONT SIZE=2>2. AIX (some version) stall on large data output. Current CVS patch is</FONT>
<BR><FONT SIZE=2>wrong and will be pulled unless an agreement can be made.</FONT>
</P>
<P><FONT SIZE=2>3. Any platform lacking mmap() will not have compression (Sorry fokes,</FONT>
<BR><FONT SIZE=2>this is not an issue really..This is a fact of life.) Those platforms</FONT>
<BR><FONT SIZE=2>lacking a usable MAP_ANON should test the release. It should fall back to</FONT>
<BR><FONT SIZE=2>/dev/zero mmap() then back to sparse files. NOTE: The fall back is</FONT>
<BR><FONT SIZE=2>runtime so if one could (gawd) compile and run OpenSSH on multiple kernel</FONT>
<BR><FONT SIZE=2>release it should do the right thing.</FONT>
</P>
<P><FONT SIZE=2>4. NeXTStep is more than likely borken. I'm pretty sure.=) It lies about</FONT>
<BR><FONT SIZE=2>having a mmap(). I'll look into it once I get my NeXT box back on the</FONT>
<BR><FONT SIZE=2>network unless someone can fire off a simple patch to solve it.</FONT>
</P>
<P><FONT SIZE=2>5. Pam changes have not been merged. So password changing is still</FONT>
<BR><FONT SIZE=2>disabled.</FONT>
</P>
<P><FONT SIZE=2>I'm looking mostly for privsep issues. If you have a platform that has an</FONT>
<BR><FONT SIZE=2>issue with privsep and you are part of the main portable tree (uwin and</FONT>
<BR><FONT SIZE=2>cray are excluded at this moment) it needs to be discussed or you'll be</FONT>
<BR><FONT SIZE=2>suffering for another 4+ months.</FONT>
</P>
<P><FONT SIZE=2>Side notes:</FONT>
</P>
<P><FONT SIZE=2>uwin - You going to resend a patch againt -current for review?</FONT>
<BR><FONT SIZE=2>cray - This weekend or next week. =) I've promised this forever. Let me</FONT>
<BR><FONT SIZE=2>know what non-intrustive syncs we can do to lessen your tracking.</FONT>
</P>
<BR>
<P><FONT SIZE=2>Lastly, I'd like to thank all of you for bearing with us during the last</FONT>
<BR><FONT SIZE=2>few months. I'm sure it is was frustrating to you as it is for us.=)</FONT>
</P>
<P><FONT SIZE=2>Let me state something right now.. *NO NEW FEATURES* 3.5 is a patch</FONT>
<BR><FONT SIZE=2>release to stablize out every platform. Don't suggest, don't push, don't</FONT>
<BR><FONT SIZE=2>even THINK about thinking about suggestion new features. I'm serious.</FONT>
<BR><FONT SIZE=2>You will be ignored.</FONT>
</P>
<BR>
<P><FONT SIZE=2>- Ben</FONT>
</P>
<P><FONT SIZE=2>_______________________________________________</FONT>
<BR><FONT SIZE=2>openssh-unix-dev@mindrot.org mailing list</FONT>
<BR><FONT SIZE=2><A HREF="http://www.mindrot.org/mailman/listinfo/openssh-unix-dev" TARGET="_blank">http://www.mindrot.org/mailman/listinfo/openssh-unix-dev</A></FONT>
</P>
<CODE><FONT SIZE=3><BR>
<BR>
***********************************************************************************<BR>
WARNING: All e-mail sent to and from this address will be received or<BR>
otherwise recorded by the A.G. Edwards corporate e-mail system and is<BR>
subject to archival, monitoring or review by, and/or disclosure to,<BR>
someone other than the recipient.<BR>
************************************************************************************<BR>
</FONT></CODE></BODY>
</HTML>