From: John Kelly <bilbo@waitrose.com>
To: linux-newbie@vger.kernel.org
Subject: Re: security training suggestions
Date: Tue, 24 Feb 2004 22:23:13 +0000 [thread overview]
Message-ID: <20040224222313.253ca77e.bilbo@waitrose.com> (raw)
In-Reply-To: <fc.004c4e0000512903004c4e0000512903.512ab7@palmertrinity.org>
Hi,
On Tue, 24 Feb 2004 14:54:29 -0500
"William Stanard" <wstanard@palmertrinity.org> wrote:
> We are about to add our Linux box to our school's intranet (a 10.x.x.x
> network); our network manager is afraid that, by adding a Linux box, we
> will be opening ourselves up to mischief from our (my) students. Does
> anyone know of any security training offerings in the southeastern US that
> I and my network manager could attend to bring us up to speed on security
> issues surrounding Linux.
>
> I am running Red Hat 8.0 (2.4.18-14) and plan to use Apache's httpd to
> serve pages for the teachers and students within the school's intranet. I
> will be teaching Linux to about ten students next fall.
>
> Bill Stanard
I don't know it this helps but O'Reilly publish a book, "Building
Secure Servers with Linux". The isbn is 0-596-00217-3. My edition dates
from 2002 and I found it useful.
Of course I would also recommend that you learn as much as possible
about Linux and networking in general. Security is not a stand-alone
issue.
Just my $0.02 worth.
regards,
John Kelly
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
prev parent reply other threads:[~2004-02-24 22:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-24 19:54 security training suggestions William Stanard
2004-02-24 20:07 ` John T. Williams
2004-02-24 21:15 ` Ray Olszewski
2004-02-24 22:23 ` John Kelly [this message]
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=20040224222313.253ca77e.bilbo@waitrose.com \
--to=bilbo@waitrose.com \
--cc=linux-newbie@vger.kernel.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