[2594] in Release_7.7_team
Minutes of the 2001-02-14 release-team meeting
daemon@ATHENA.MIT.EDU (Greg Hudson)
Wed Feb 14 15:06:05 2001
Date: Wed, 14 Feb 2001 15:05:56 -0500
Message-Id: <200102142005.PAA23687@equal-rites.mit.edu>
From: Greg Hudson <ghudson@MIT.EDU>
To: release-team@mit.edu
Attending: ghudson zacheiss othomas ajfox rbasch miki tbelton amb jweiss
1. Status reports
AUI: nautilus builds for Linux, more or less, and almost for IRIX.
After that, Greg will go back to configuration fiddling.
Solaris 8: installation just about done for sun4u... currently all
64-bit. Previously we had planned to have a 32-bit userland. More
exploration of issues required. miki will put up lists of packages
(local, non-local, not installed at all) for review.
Linux: Nothing to report yet, hopefully soon.
2. Printing
The 8.4 lprng server has one serious bug left (authentication status
is dropped when a request passes through a bounce queue, so duplex
queues don't work when the target queue requires authentication).
Until this bug is fixed, print server maintainers are mostly stuck
running the 8.3 release.
We have three options:
* Fix the bug
* Go back to 8.3 source base (and reapply some patches)
* Import a new version of lprng and pray
Past experience pretty much rules out the third option as being a good
idea. Garry will try to fix the bug, and if that proves too
difficult, we will go back to the 8.3 source base.
3. Handling of remotely exploitable security holes
There was some political fallout from our handling of the sshd
security hole. In the future, we'll provide fixed binaries for older
releases or at least be clearer about our willingness to do so.
4. Solaris patches
Sun wants some Solaris patches applied before they'll consider
problems in the 1.3 JVM. These patches include a jumbo kernel patch
and a C++ library upgrade.
We'll go ahead and apply the patches. We should make sure to check
that KNFS still works and that non-updated machines don't lose due to
AFS/local disk mismatch.
5. Netscape
Netscape is unstable. We talked about this at length but didn't come
up with any realistic options. Basically, there are four outs:
* Netscape releases a reasonable browser (whether 4.x or 6.x)
* MS releases a reasonable IE for our platforms
* An acceptable substitute manifests
* We close the gap between Mozilla and what we would find
reasonable
The fourth option is the one we have the most control over (and may
get more feasible over time), but IS doesn't really want to be moving
in the direction of having more control over software.
6. xss problems
There are more reports of xss locking up such that the workstation
can't be unlocked. Our plan is to upgrade xss in the next full
release and hope that helps, given that we don't have a lot of
resources for debugging bugs we can't easily reproduce.
