From: dscott@phivedesign.com
To: "'gentoo-hardened@gentoo.org'" <gentoo-hardened@gentoo.org>
Subject: [gentoo-hardened] More thoughts..
Date: Thu, 20 Mar 2003 06:07:38 -0500 [thread overview]
Message-ID: <1048158458.a743b0ff9f2d5@www.phivedesign.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 675 bytes --]
Before this continues much further:
(http://www-dt.e-technik.uni-dortmund.de/~ma/qmail-bugs.html
RFC-1652, RFC-2821, RFC-1894)
I simply wanted to make the point that user-based file exclusion
(systrace/selinux policies) should not be the only concern for a hardened
distro.
The application layer is equally important, both from a stability and security
perpective (in some cases DDOS vulnerabilities would be equally as devastating
as ending up an IRC Zombie).
Encouraging users to use applications that have a solid history of 0 or better
exploits/buffer attacks is a "good thing".
D.
[-- Attachment #1.2: PGP Digital Signature --]
[-- Type: application/pgp-signature, Size: 831 bytes --]
[-- Attachment #2: PGP Public Key --]
[-- Type: application/pgp-keys, Size: 1642 bytes --]
[-- Attachment #3: Type: text/plain, Size: 42 bytes --]
--
gentoo-hardened@gentoo.org mailing list
reply other threads:[~2003-03-20 11:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1048158458.a743b0ff9f2d5@www.phivedesign.com \
--to=dscott@phivedesign.com \
--cc=gentoo-hardened@gentoo.org \
/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