> OK, 2 to 5 minutes downtime to disable. Big Whoop. Maybe should be
> done. But, have you ever tried to administer 200 computers? How many
> people know the BIOS password? Do the primary users know it? Can they
> reboot their own machine? Does an administrator have to visit every
> machine
n using sulogin and not securing Lilo is like putting a nice
expensive dead bolt lock on a screen door.
Kurt Seifried
SecurityPortal, your focal point for security on the net
http://www.securityportal.com/
> Personally, when I see "1.2.0pre10-4", I think, "This is not the same as
the
> original/base 1.2.0pre10." Depending on how the numbering is implemented,
it
> has been updated 3 or 4 times since the original 1.2.0pre10. So I would
not
> expect it to have the same bugs.
So did you fix the root h
> Yes I read the update. I'd be happy to review your articles for you, but I
> don't think you should stop at one reviewer. Debian is a very big project
and I'm
> still finding my way around parts of it. You may have been in contact with
Ben
> Collins. If so I suggest you ask him too.
Yeah, he did
ds to bind port 53
>which is below 1024 there are problem to execute it. One solution is to
>rewrite named code (like httpd) another is to make the hole into the
>kernel. Both are nonstandard solutions. There are also possible to use
>some portwrapper/redir. Does anyone use some of these?
>
>[mod: Patches are floating around. -- REW]
>---
>Cougar
-seifried
--
Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
5 matches
Mail list logo
