Date: Sat, 16 Dec 2000 08:58:30 +0800 From: "James Lim" <jameslpin@pacific.net.sg> To: "Mikhail Kruk" <meshko@cs.brandeis.edu>, "Anil Jangity" <aj@entic.net> Cc: "jrz" <jrz@cnmnetwork.com>, <security@FreeBSD.ORG> Subject: Re: Security Update Tool.. Message-ID: <007901c066fb$4f187040$fa5e78cb@gchang> References: <Pine.LNX.4.30.0012151959380.1733-100000@daedalus.cs.brandeis.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi,
Some of the ports are actually marked forbidden due to the security
hazards. That is served as a warning to users. But of course if they want to
risk it they just have to comment it
James Lim
Technical Support Executive
Pacific Internet Limited
89 Science Park Drive
#02-05/06 The Rutherford
Singapore 118261
Finger evilfry@sg.freebsd.org for PGP key.
----- Original Message -----
From: "Mikhail Kruk" <meshko@cs.brandeis.edu>
To: "Anil Jangity" <aj@entic.net>
Cc: "jrz" <jrz@cnmnetwork.com>; <security@FreeBSD.ORG>
Sent: Saturday, December 16, 2000 9:00 AM
Subject: Re: Security Update Tool..
> I'm not sure that many people would like that kind of automation, but what
> is really missing IMHO is ability to mark ports whichs are insecure and
> add some option to pkg_info which will check all installed packages. I
> think OpenBSD has exacty this, no?
>
> > I think he was looking for something a little more "automated".
Something
> > like IE's "Window's update" for freebsd ;-)
> >
> > I don't think its too difficult to do this, all you do is do ident on
any
> > binaries that are on the local system and compare the version with the
> > version string in the advisories... the advisory might need some
> > formatting changes?
> >
> > just thinking out loud.
> >
> >
> > Fri, 15 Dec 2000 (4:41pm -0800) Message:
> >
> > @ >> My question is, is there a util yet that in theory (maybe if so, or
if
> > @ >> someone writes one would work differently than what I'm imagining)
queries a
> > @ >> central database with all the security advisories, checks the local
system
> > @ >> for comparisons and vulnerabilities against that database and
reports to the
> > @ >> user who ran the util.
> > @ >>
> > @ >> ie, sacheck -H sa-host.freebsd.org
> > @
> > @ would be fairly easy to write a shell or perl script that checks for
current
> > @ advisories and prints it out in pretty format.
> > @
> > @ -jrz
> > @
> > @
> > @
> > @ ---
> > @ Jacob Zehnder | Systems Engineer
> > @ CNM Network | http://www.cnmnetwork.com
> > @ business: jrz@cnmnetwork.com
> > @ other: jrz@rackmount.org
> > @ ---
> > @ "Where am I, and what am I doing in this handbasket?"
> > @
> > @
> > @
> > @ To Unsubscribe: send mail to majordomo@FreeBSD.org
> > @ with "unsubscribe freebsd-security" in the body of the message
> > @
> > @
> >
> >
> >
> > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > with "unsubscribe freebsd-security" in the body of the message
> >
>
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-security" in the body of the message
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?007901c066fb$4f187040$fa5e78cb>