MidnightBSD 0.4-RELEASE-p13 Fix a vulnerability in the control message API. A buffer is not properly cleared.
MidnightBSD 0.4-RELEASE-p12
MidnightBSD 0.4-RELEASE-p11 Security updates for sendmail and ktrace. See UPDATING.
MidnightBSD 0.4-RELEASE-p10
Fix a TCP reassembly bug that could result in a DOS attack
of the system. It may be possible to obtain portions
of kernel memory as well.
0.4-RELEASE-p9 Fix a security issue affecting NFS server where a trusted client can deadlock the server.
0.4-p8 openssl fix.
document dot.profile fix.
security update
Move RELENG_0_4 to stable/0.4
Implement a compatibility fix for libc's iconv support to work with gettext and other GNU packages. MidnightBSD 0.4-RELEASE-p5
0.4-RELEASE-p3
nullfs(5)
The nullfs(5) implementation of the VOP_LINK(9) VFS operation does not
check whether the source and target of the link are both in the same
nullfs instance. It is therefore possible to create a hardlink from a
location in one nullfs instance to a file in another, as long as the
underlying (source) filesystem is the same.
ifioctl
As is commonly the case, the IPv6 and ATM network layer ioctl request
handlers are written in such a way that an unrecognized request is
passed on unmodified to the link layer, which will either handle it or
return an error code.
Network interface drivers, however, assume that the SIOCSIFADDR,
SIOCSIFBRDADDR, SIOCSIFDSTADDR and SIOCSIFNETMASK requests have been
handled at the network layer, and therefore do not perform input
validation or verify the caller's credentials. Typical link-layer
actions for these requests may include marking the interface as "up"
and resetting the underlying hardware.
0.4-RELEASE-p3 Fix the broken altq that was part of the release.
0.4-RELEASE-p2 Fix two security vulnerabilities. Fix an integer overflow in IP_MSFILTER (IP MULTICAST). This could be exploited to read memory by a user process. When initializing the SCTP state cookie being sent in INIT-ACK chunks, a buffer allocated from the kernel stack is not completely initialized. Patches obtained from: FreeBSD
bump to p1 to cover the recent security issues. Long term plan is to stop using p1, p2, p3, ... and increment release version like NetBSD does, but we'll "announce" that before making the change.
prepare for 0.4-RELEASE
0.4 is now prerelease
This commit was manufactured by cvs2svn to create branch 'RELENG_0_4'.
use SYSDIR rather than dirname + relative path
Sync some things with freebsd 9 stable
Move things along.. current is now 0.4-CURRENT. Change the man pages, osreldate and other tunables in the system accordingly. While we're here, update other bsd systems in our mdoc.local.
revert to 0.3 as discussed with ctriv@
Switch version information. We're starting at 1.0-CURRENT now.
Change over to using __MidnightBSDversion as discussed with ctriv. Switch to 0.3-CURRENT
Update to 0.2-CURRENT
Added cvs header.
This commit was generated by cvs2svn to compensate for changes in r5, which included commits to RCS files with non-trunk default branches.
Imported from FreeBSD 6.1 beta sources
Imported from FreeBSD 6.0 sources
This form allows you to request diffs between any two revisions of this file. For each of the two "sides" of the diff, enter a numeric revision.