On Wed, 4 Oct 2000, Tony Lambiris wrote:

> On Wed, Oct 04, 2000 at 03:06:34PM -0400, Jeffry Smith wrote:
> > You write as if you are a security expert (especially given your
> > domain name), and have no knowledge of
> > the Bastille project (a group of people developing scripts to harden
> > Linux installs, and ensure they are set up correctly)?  I agree that
> > the user needs to verify for themselves, but they can also verify the
> > Bastille scripts.  Using Bastille is no different than using SAINT or
> > another tool to verify that a system is set up correctly.
> 
> Hahaha, I'm sorry I don't rely on scripts to harden my system, or keep up to
> date with the projects that create these scripts. I'm just a little too busy
> with the 15 other security-related mailinglists to worry about scripts to
> 'harden my system'. This is just another crutch to keep you from learning how
> to do it youself IMHO. Much like Red Hat does with Linux (am I sensing a
> pattern?).
> 

So you wrote your own kernel?  Write your own apps?  At some point,
you trust other people (and verify their code).  I choose to use tools
that help me, and get the job done, but, hey, you want to kill
yourself, that's your problem (btw:  did you wonder why you're "too
busy"?)

> > And if the person isn't an expert, they shouldn't be held responsible
> > as such.  Also, blaming the tool (Linux) for the human error (which is
> > what this thread was about) is still wrong.
> 
> Sure they should. If they can't do the job right, then they shouldn't be
> doing it. That's like putting a graphics designer in charge of your mail
> servers. It's just asking for trouble. And no one is blaming Linux, I'm
> blaming Red Hat for their ass-backwards way of doing things.
> 
> > You mean you never took a job for which you had to do on-the-job
> > training?  Must be nice to be competent in everything.  And it appears
> > from the original post that they aren't clued NOW (i.e. they removed
> > Linux from the campus network because 1 box was used to crack an
> > outside site).
> 
> Nope.
> I'm not trying to fool anyone.
> Yeah, it's a pretty safe bet KSC doesn't have any linux-saavy people. Hopefully
> they can learn a thing or two from this thread.
> 

Of course, some of us enjoy learning,  Others fool themselves
that they're perfect.  BTW:  I assume you walk into every job knowing
everything about the company, their systems, etc.  Never need to ask a
single question, never, ever make a mistake.  And, you have a bridge
in brooklyn to sell.


> > You can blame Red Hat, but it doesn't make it a bug.
> 
> ?

Read your own posts, if you have to ask.

> 
> > To quote from the first post of this thread:
> > KSC has traditionally had a Linux server that held student accounts
> > for mail
> [---snip---]
> > Show me the name in there.  Took me 1 second to spot that, 2 seconds
> > tops to post it here.  In fact, you quoted the above post in your
> > first reply:
> > Date: Wed, 4 Oct 2000 10:58:38 -0400
> > From: Tony Lambiris <[EMAIL PROTECTED]>
> > To: GNHLUG <[EMAIL PROTECTED]>
> > Subject: Re: KSCLUG
> > 
> > Wherein you, guess what, were the first one to name names.  Want to
> > try again on the excuses?
> 
> Would someone care to fwd me the first post of this thread? Thanks.
> 

Why, you didn't save it?  After quoting it?  My, my.  

> > Right, you forgot the smiley.
> 
> What smiley?
> 
> 

I suspect you've just made the mistake you regret.

jeff


------------------------------------------------------------------------
Jeffry Smith      Technical Sales Consultant     Mission Critical Linux
[EMAIL PROTECTED]   phone:603.930.9739   fax:978.446.9470
------------------------------------------------------------------------
Thought for today:  dup killer /d[y]oop kill'r/ n. 

 [FidoNet] Software that is
   supposed to detect and delete duplicates of a message that may have
   reached the FidoNet system via different routes.




**********************************************************
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
**********************************************************

Reply via email to