Re: [FreeBSD-Announce] FreeBSD-4.11 Release Candidate 1 Available

2004-12-20 Thread Matthias Andree
Ken Smith [EMAIL PROTECTED] writes:

 Announcement
 

 The FreeBSD Release Engineering Team is pleased to announce the availability
 of FreeBSD 4.11-RC1, which marks the beginning of the FreeBSD 4.11 Release
 Cycle.  This will be the last of the FreeBSD 4.X releases.  It is meant

These long-standing bugs are still open, in decreasing order of
importance. I checked 60313 and 44260 a few moments ago with a current
RELENG_4_11 CVS, and haven't seen any followups on 46866 and 71453.

kern/60313  data destruction
(kernel access wrong address on block device)

bin/46866   nondeterministic NIS returns
(this has been messing up NIS-based systems for ages
with users gone one moment and appearing the next)

bin/71453   tcpdump segfaults on PPP IPV6CP traffic
(includes a suggested solution, perhaps MFC suffices)   

kern/44260  LINT does not list pseudo-device tap
(trivial to fix)

-- 
Matthias Andree
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: [FreeBSD-Announce] FreeBSD-4.11 Release Candidate 1 Available

2004-12-20 Thread Trond Endrestøl
On Mon, 20 Dec 2004 11:49+0100, Matthias Andree wrote:

 bin/46866   nondeterministic NIS returns
 (this has been messing up NIS-based systems for ages
 with users gone one moment and appearing the next)

While you're at it, could someone take a look at the logit() function
in portmap (in the file portmap/pmap_check.c)?

Make the function more safe to use with NIS, i.e. the call to
getrpcbynumner(), and particularly when the NIS domain is set, but
ypbind hasn't yet registrered itself with portmap or are about to
register itself with portmap. This (serious) problem occurs only when
portmap is run with logging turned on, which probably accounts for why
no one has done anything about it before.

Take a look at PR bin/73422 for more details about this problem with
portmap, ypbind and rc.network. Please don't hesitate about contacting
me if you need more information.

Btw, the same problem is present in FreeBSD 5.x.

-- 
--
Trond Endrestøl  |[EMAIL PROTECTED]
Patron of The Art of Computer Programming|   FreeBSD 4.8-S  Pine 4.55
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]