From: "L. C. Robinson" <lcr@onewest.net>
To: blinux-list@redhat.com
Subject: Re: security programs
Date: Fri, 11 Oct 2002 14:04:35 -0600 (MDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0210111352460.945-100000@rupin.localnet> (raw)
In-Reply-To: <Pine.BSF.4.44.0210111243060.21085-100000@server1.shellworld.net>
Tcp_wrappers is a standard binary part of Red Hat, and
any other decent distribution. It is essential to
configure it after a new installation, for any decent
security, of course, along with the other security
configuration basics, such as installing all security
updates. If one neglects those things, good security
tools in linux are worthless, and you WILL get hacked
(but maybe not quite so quickly as with a certain
dominant vendor's junk software).
LCR
On Fri, 11 Oct 2002, Jude DaShiell wrote:
> Has anyone managed to get tcp_wrappers_7.6 built and
> operating under any version oor any brand of linux
> yet? If you don't know what that i
> ftp://ftp.porcupine.org/pub/security/index.html
> should give you background info.
--
L. C. Robinson
reply to no_spam+munged_lcr@onewest.net.invalid
People buy MicroShaft for compatibility, but get incompatibility and
instability instead. This is award winning "innovation". Find
out how MS holds your data hostage with "The *Lens*"; see
"CyberSnare" at http://www.netaction.org/msoft/cybersnare.html
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
Jude DaShiell
` L. C. Robinson [this message]
` Jude DaShiell
` David Csercsics
` Jude DaShiell
` David Csercsics
` Jude DaShiell
` John
` Jude DaShiell
` John
` L. C. Robinson
` John
` Jude DaShiell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.44.0210111352460.945-100000@rupin.localnet \
--to=lcr@onewest.net \
--cc=blinux-list@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).