rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: Chris Siebenmann <cks>
To: rc
Subject: anonymous ftp from archone.tamu.edu
Date: Tue, 1 Dec 1992 02:26:23 -0500	[thread overview]
Message-ID: <92Dec1.022629est.2853@hawkwind.utcs.toronto.edu> (raw)

 I asked the system administrator of archone.tamu.edu about this, and
here's his reply.

	- cks

------- Forwarded Message

From:	Steve Rikli <steve@archone.tamu.edu>
To:	cks@hawkwind.utcs.toronto.edu
Subject: Re:  what happened to anonymous ftp to archone.tamu.edu?

archone.tamu.edu is still in the anonymous ftp business, but tamu.edu
is being unfriendly.

The Computing Services Center (i.e. main campus computing beaurocracy)
at Texas A&M was attacked by crackers near the end of August.  According
to their reports, the crackers were able to get into computers all
over campus (interestingly enough, they did not get into archone or
any of my other systems).

The response to this attack was to set up a packet filter at the main
campus routers--all incoming ftp, rsh, rlogin, telnet is being filtered
and turned away from non-tamu.edu sites, except for a select few campus
computers.

At the beginning of November, the CSC made available a series of scripts
and routines (basically Cops, but more paranoid and tailored to look for
signs of this recent attack) which any site admin on campus can run on
his/her computers, and if they pass, these computers will be allowed
free access to/from the outside world again.

archone.tamu.edu has passed most of these tests (all save one, actually)
but the last is somthing of a matter of opinion.  I don't particularly
care for it, but I suppose I will end up doing it, just because my net
access depends on it.

This has been more than a little bit of an inconvenience for me--I
provide several things anonymously via ftp, not the least of which is
Byron's rc, and my "customers" are unhappy.  I don't blame them.  Once
I "fix" the last of the CSC's criteria, I assume it will take a couple
weeks for archone to be unhindered again, so I am hoping for sometime
before the end of December.

Sorry for the inconvenience, but please bear with me--things won't always
be like this.

cheers,
sr.
- -------
|| Steve Rikli 	           |||  Visualization Lab               ||
|| steve@archone.tamu.edu  |||  Texas A&M University            ||
|| 409-845-3465            |||  College Station, TX  77843-3137 ||

------- End of Forwarded Message


                 reply	other threads:[~1992-12-01  7:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=92Dec1.022629est.2853@hawkwind.utcs.toronto.edu \
    --to=rc@hawkwind.utcs.toronto.edu \
    /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;
as well as URLs for NNTP newsgroup(s).