On Tue, May 14, 2002 at 07:28:55AM -0700, Cy Schubert - CITS Open Systems Group wrote:
> In message <[EMAIL PROTECTED]>, Steve Shorter writes:
> > Howdy!
> > 
> >     I intend to upgrade ipfilter on FreeBSD 4.5 to ipf-fil3.4.27.
> > 
> >     A couple of questions ....
> > 
> >     1) The sources are readily available, but how can I verify
> >            their integrity? By this I mean is there a MD5 checksum
> >            or other metric that I can use to verify that the file
> >            ip-fil3.4.27.tar.gz is the file as Darren intends and
> >            has not been compromised? Other open source projects provide
> >            a MD5 checksum for source tar balls, is this possible for
> >            ipfilter?
> 
> CVSup 4.6-PRERELEASE.  IPF 3.4.27 comes with it.

        This does not answer the above. I have some *good* reasons for
not upgrading to 4.6. I simply think that there should be some way
to verify the integrity of downloaded source code. For example
the ports system uses MD5 checksums. Shouldn't IPFilter have a similar
verification mechanism for those who wish to upgrade directly from source
that is separate from the FreeBSD source tree?


> There are a number of bugs fixed in 4.6.  Besides, building world is 
> not that difficult.  The effort is minimal (about 1/2 hour of my time 
> and the rest of the time spent working in the yard while the computers 
> did the the upgrade), that being,

        I am only affected by 2 bugs and have patched them into
4.5-p4. For a home system "building world" is trivial. For a large 
production pool it requires planning, service interuption etc ...
and is quite unjustifiable.

> I'm running 4.6-PRERELEASE (CVSupped on Saturday) on all four of my 
> FreeBSD systems at home and on one FreeBSD system at work.

        My situation is quite different. I have *lots* of production
machines running very happilly on 4.5-p4 + fixes, and upgrading to
4.6 is completely unjustifiable for both technical and economic reasons.

        -steve

Reply via email to