From: John Scroggins <dataefx@earthlink.net>
To: Conan Callen <ccallen@windowpane.com>
Cc: SELinux@tycho.nsa.gov
Subject: Re: [Fwd: Partial TOC for Comment]
Date: Fri, 17 Aug 2001 13:05:20 -0700 [thread overview]
Message-ID: <3B7D7900.EEFEA652@earthlink.net> (raw)
In-Reply-To: 002f01c12743$52700650$3a8314d1@nwlink.com
Conan Callen wrote:
>
> > I don't expect SELinux will protect against all possible threats ...
> A chapter on SELinux scope would be helpful here. Listing additional
> references, tools & techniques that
> can be used along with SELinux to help find and plug the holes.
>
> Also a scenarios section would be nice too. For instance "Building
> Firewalls" has a whole chapter on different configurations.
Good idea, but I think it out of scope for the preliminary document, but
I will install a placeholder for this element
I want to set up
> two configurations, a secured server running http & smtp, and a dual homed
> firewall. The kinds of questions in my mind are "is there a better way that
> I could be doing this?", "am I setting this up correctly?, did I miss
> something ...?".
I can place references (URLs)to relevant material in the body of the doc
to take care of this situation..
For instance if it was just as secure to stick a second nic
> into the server and make it the gateway as well, then I could spend more
> effort on the one machine.
Again, I want to move away from hardware, and distro issues of choice.
Your input is great .. thanks
--JS
>
> >
>
> --
> You have received this message because you are subscribed to the selinux list.
> If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
> the words "unsubscribe selinux" without quotes as the message.
--
You have received this message because you are subscribed to the selinux list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2001-08-17 20:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-17 2:07 [Fwd: Partial TOC for Comment] John Scroggins
2001-08-16 23:12 ` Dale Amon
[not found] ` <3B7D591A.EA28B00C@earthlink.net>
2001-08-17 11:23 ` Dale Amon
2001-08-18 11:43 ` LeRoy Cressy
[not found] ` <20010818084601.A7060@vnl.com>
[not found] ` <3B7FD0EE.398E6F02@telocity.com>
2001-08-19 4:58 ` Dale Amon
2001-08-17 17:20 ` Benjamin D. Thomas
2001-08-17 19:00 ` John Scroggins
2001-08-17 17:37 ` Conan Callen
2001-08-17 20:05 ` John Scroggins [this message]
2001-08-16 23:18 ` Dale Amon
2001-08-17 18:03 ` Conan Callen
2001-08-17 19:51 ` John Scroggins
2001-08-17 20:09 ` Conan Callen
2001-08-17 11:42 ` Dale Amon
2001-08-17 22:21 ` John Scroggins
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=3B7D7900.EEFEA652@earthlink.net \
--to=dataefx@earthlink.net \
--cc=SELinux@tycho.nsa.gov \
--cc=ccallen@windowpane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.