From bmurray at snf.stanford.edu  Tue Mar  4 15:37:56 2003
From: bmurray at snf.stanford.edu (Bill Murray)
Date: Tue, 4 Mar 2003 15:37:56 -0800 (PST)
Subject: [GECOS] sendmail update, and snort too (fwd)
Message-ID: <Pine.LNX.4.04.10303041536540.19301-100000@snf.stanford.edu>

Mike or John,

Has anyone looked at this report yet?

Bill

---------- Forwarded message ----------
Date: Tue, 4 Mar 2003 11:18:03 -0800
From: Joe Little <jlittle at cs.stanford.edu>
To: gecos at island.stanford.edu
Subject: [GECOS] sendmail update, and snort too

Today's island report covers the sendmail issue in depth, including  
important notes from the CERT advisory, further advisories for vendors,  
and a technical analysis of the bug

http://island.stanford.edu/ 
modules.php?op=modload&name=News&file=article&sid=491&mode=thread&order= 
0&thold=0

Also note that all snort versions (an intrusion detection system) have  
a RPC buffer overflow that can be exploited from viewed network  
traffic, and this feature is on by default. All snort systems need to  
update to avoid this issue.

_______________________________________________
GECOS mailing list
GECOS at island.stanford.edu
http://island.stanford.edu/mailman/listinfo/gecos



From bmurray at snf.stanford.edu  Tue Mar  4 18:09:07 2003
From: bmurray at snf.stanford.edu (Bill Murray)
Date: Tue, 4 Mar 2003 18:09:07 -0800 (PST)
Subject: Sendmail CERT Advisory
Message-ID: <Pine.LNX.4.04.10303041802420.25382-100000@snf.stanford.edu>

John and Mike,

Based on my review of Joe Little's web site, a careful reading of the 
CERT Advisory, and the qmail FAQs and mailing list, I believe that 
qmail is completely immune to this latest remote buffer overflow
problem.  Yeah!!!  So that takes care of snf.

John has downloaded a version of sendmail (8.12.8) on spf that has the
bug patched and is not running sendmail anyway.  Any snf replacement
will be running qmail instead of sendmail.  That takes care of spf.

On to the Solaris boxes.

Bill



From mikebell at stanford.edu  Thu Mar 13 11:55:44 2003
From: mikebell at stanford.edu (Mike Bell)
Date: Thu, 13 Mar 2003 11:55:44 -0800
Subject: Computer acting up!
References: <3E70DBA3.CE13D1B2@snf.stanford.edu>
Message-ID: <3E70E240.4078BC62@stanford.edu>

Hi Jeannie,

I'll forward this to computer at snf.stanford.edu, the home for these
problems. Also a good first step is to restart your machine.

Mike

Jeannie Perez wrote:

> Hi Mike,
> I am not sure if this is your problem or if I have to contact another
> person, but let me know.  At times my computer flickers and I lose
> resolution. Just started doing this today.
>
> --
> Jeannie Perez
> Stanford Nanofabrication Facility
> CIS Room 146, Mail Code 4070
> Stanford, CA  94305
> (650) 723-7997
> jperez at snf.stanford.edu



From shott at snf.stanford.edu  Thu Mar 13 14:30:49 2003
From: shott at snf.stanford.edu (John Shott)
Date: Thu, 13 Mar 2003 14:30:49 -0800
Subject: Unmoderated mailing lists ....
Message-ID: <3E710699.B5204D30@snf.stanford.edu>

Bill, Mike, and Dick:

As you know, I've been moderating most of the mailing lists since our last
spam/virus attach.  Fortunately that activity has subsided ...  Well,
actually, I unmoderated all of the *-pcs lists a week or so ago.

Secondly, since I will be out of town tomorrow through Monday, it would make
for grumpy customers, if that amount of e-mail was being held up waiting for
me to moderate it.

Accordinlgy I've unmoderated all of the normal equip_name at snf.stanford.edu
mailing lists as well as the diffusion, beamtools, and other "update" lists. 
Finally, I've also unmoderated lambmembers ... I guess what I'm trying to say
is that none of the mailing lists is being moderated at the moment.

Thats should work ... certainly for the next few days.

Bill or Mike, should there be the need to begin moderating one or more lists,
that can be done with:

ezmlm-make -+m ~alias/MLs/mailing_list_name

and unmoderating can be done with:

ezmlm-make -+M ~alias/MLs/mailing_list_name

Both of these commands can be run (on snf, of course) either as root or as
alias.

If you do need to start moderation, I think that I'm already listed as a
moderator.  To manually add someone else as a moderator is done with:

ezmlm-sub ~alias/MLs/mailing_list_name-mod moderator_name at snf.stanford.edu

Hopefully none of this will be needed but will avoid the problem of getting a
backlog of 4 days worth of e-mail backed up because I wasn't around.

Thanks,

John

p.s. I did leave webmaster at snf.stanford.edu ... that mailing list gets nothing
but spam/viruses.  I'll bet that a lot of spammers know that if they send mail
to webmaster at any_host_in_the_world that some poor soul is going to see it.
When I have a chance I'll try to remember to eliminate that mailing list ...
I'll bet that renaming it website at snf.stanford.edu would cut way down on that
problem.


From mahnaz at snf.stanford.edu  Mon Mar 24 16:29:02 2003
From: mahnaz at snf.stanford.edu (Mahnaz)
Date: Mon, 24 Mar 2003 16:29:02 -0800
Subject: Print
Message-ID: <3E7FA2CE.5A5B577B@snf.stanford.edu>


hello

How am I suppose to print? The printer has been down since last week.

mahnaz



From shott at snf.stanford.edu  Mon Mar 24 16:35:39 2003
From: shott at snf.stanford.edu (John Shott)
Date: Mon, 24 Mar 2003 16:35:39 -0800
Subject: Print
References: <3E7FA2CE.5A5B577B@snf.stanford.edu>
Message-ID: <3E7FA45B.B22C99EC@snf.stanford.edu>

Mahnaz:

It's dead ... and it's not clear that it can be fixed.  A new one has been
ordered, but I don't know when it will be avialable.

John


From bmurray at snf.stanford.edu  Wed Mar 26 13:10:47 2003
From: bmurray at snf.stanford.edu (Bill Murray)
Date: Wed, 26 Mar 2003 13:10:47 -0800 (PST)
Subject: Mahnaz's Computer
Message-ID: <Pine.LNX.4.04.10303261304340.9928-100000@snf.stanford.edu>

John,

Mahnaz told me her computer was dying so I took a look today.  I ran the
defragmenter, downloaded virus updates, scanned for viruses, ...  I couldn't
find any major problems.  Perhaps the next thing to do is re-install the
operating system.  (If we're going to do that, we should consider XP or
whatever we wish to make the desktop standard.)  Since this could be quite
time-consuming, and I have a number of higher priority tasks on my list,
I'm sending this request to computer at snf.

Thanks,
Bill




From mahnaz at snf.stanford.edu  Fri Mar 28 11:15:57 2003
From: mahnaz at snf.stanford.edu (Mahnaz)
Date: Fri, 28 Mar 2003 11:15:57 -0800
Subject: Printer
Message-ID: <3E849F6D.9F4CC614@snf.stanford.edu>



Helloooo,

Is the driver and all that set up. We still can not print.

mahnaz