Date: Mon, 27 Aug 2001 20:07:31 -0400 (EDT) From: Mikhail Kruk <meshko@polkan2.dyndns.org> To: Christopher Schulte <christopher@schulte.org> Cc: Mikhail Kruk <meshko@mindspring.com>, <freebsd-security@FreeBSD.ORG> Subject: Re: procmail, squid: any takers? Message-ID: <Pine.BSF.4.33.0108272003260.45703-100000@localhost> In-Reply-To: <5.1.0.14.0.20010827185459.022a3de0@pop.schulte.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> At 07:55 PM 8/27/2001 -0400, Mikhail Kruk wrote:
> >Hm... I don't see anything about sendmail in UPDATING. Also things like
>
> 20010822: p14
> Fix command line argument overflow probelm in sendmail.
please tell me what am I doing wrong. I'm cvsup'ing to RELENG_4. Using
cvsup3.freebsd.org and grab src-all
This is the beginning of my UPDATING file:
20010814:
The pci attachment for pcic device was merged from current. You
should update your pccardd at the same time as you update your
kernel.
Note: Interrupts will now be shared between the CardBus bridge
and the cards. This is a change over the hand configuration
before.
20010811:
...
> >procmail which are ports don't go into updating anyway, right?
>
> So far as I can tell, no. Just the base userland and kernel. The kind of
> stuff that a make world or kernel will build and install.
So following UPDATING or even cvs logs isn't really enough. I still think
that it would be a good idea to release informal notifications. I agree
that security officer would be burried under cries for help, but I think
that there is enough crap (like this discussion :) on the list already. Is
it going to be that much worse?
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.33.0108272003260.45703-100000>