From: Jesse Pollard <pollard@tomcat.admin.navo.hpc.mil>
To: jamagallon@able.es, "Richard B . Johnson" <root@quark.analogic.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux connectivity trashed.
Date: Thu, 29 Mar 2001 10:30:26 -0600 (CST) [thread overview]
Message-ID: <200103291630.KAA67240@tomcat.admin.navo.hpc.mil> (raw)
"J . A . Magallon" <jamagallon@able.es>:
> On 03.29 Richard B. Johnson wrote:
> >
> > The penetration occurred because somebody changed our firewall
> > configuration
> > so that all of the non-DHCP addresses, i.e., all the real IP addresses had
> > complete
> > connectivity to the outside world. This meant that every Linux and Sun
> > Workstation
> > in this facility was exposed to tampering from anywhere in the world. This
> > appears
> > to be part of a plan to remove all non-DHCP machines by getting them
> > trashed.
> >
>
> See the cleverness of his network admins, that spent their time configuring
> a firewall to MAKE HOLES where there are not any...
And obviously not tell anyone they were doing so....
-------------------------------------------------------------------------
Jesse I Pollard, II
Email: pollard@navo.hpc.mil
Any opinions expressed are solely my own.
next reply other threads:[~2001-03-29 16:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-29 16:30 Jesse Pollard [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-03-29 13:34 Linux connectivity trashed Richard B. Johnson
2001-03-29 14:54 ` J . A . Magallon
2001-03-29 16:51 ` John Jasen
2001-03-29 19:01 ` Doug Ledford
2001-04-02 17:42 ` Richard B. Johnson
2001-03-29 20:21 ` Roger Larsson
2001-03-31 17:20 ` John Kodis
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=200103291630.KAA67240@tomcat.admin.navo.hpc.mil \
--to=pollard@tomcat.admin.navo.hpc.mil \
--cc=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
--cc=root@quark.analogic.com \
/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