This Would be a GREAT start for us newbies!
I really appreciate that you took a look at the basic idea and found a way
how to make a version of it fit into a LUG meeting. It seems all to often
that (newbie) ideas are dismissed out of hand. I realize that I may not
understand the fullness of what I am asking. But having someone (like Larry)
repackage the basic idea into a workable version is very encouraging to those
of us getting started in LINUX.
Larry, Thanks for your input!
Regards!
Vince McHugh
Systems Support Manager
NECS\Canon
> There are some good references available that have been mentioned already
> which will allow someone to develop a full understanding of Linux security,
> but I think I might have a good suggestion for a single-meeting topic. Some
> distros ship with many dangerous features enabled already...but it's hard
> for someone just learning about security to find and plug these holes. It
> may take a busy person several weeks to read a book such as "Maximum..." and
> much longer to begin to really understand some of the topics and put things
> into place. Most of those same people won't wait until they really
> understand the security risks and procedures before they put their box on
> the net. Perhaps a presenter who is familiar with the security topic could
> shine a light on some of these risks. For example, explain or demonstrate a
> good tool for scanning your box for vulnerabilities (open ports, programs w/
> known weaknesses, etc.) and how to shut them down. The talk could wrap up
> with some good "for further information you should..." pointers.
>
> I would like to say "pass" in advance before anyone `volunteers ` me. :-)
> I'm trying to learn TCP/IP and Java right now, as well as brushing up on
> PERL, (the priority switching to whatever is the "hot topic" for the week)
> for work and I am already close frying my brain.
>
> #include <disclosure.h>
> Larry
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
