I don't normally read this list, but someone forwarded the following
quote to me about me.
Jeff Sadayao: "He is a guy with poor judgment who puts holes in your
firewalls when you aren't looking (or are too trusting)."
Jeff, how could I have "put holes in your firewall" when you yourself
set it up to permit arbitrary inbound connections above TCP port 1024
on internet gateway machines?
I made no changes to your firewall configuration. I operated entirely
within the way you had set it up. What "hole" is that? I merely
opened a socket while I was at my desk at Intel and then used the
socket later from outside to stay on top of my mail and handle burning
issues for the short periods while I was gone *strictly for the
benefit of the company*.
If you did not wish to permit that kind of connection, you certainly
had it within your disposal to disallow it.
Let's be careful about who is claiming what here. You ran the
firewall, I didn't, nor did I alter the configuration in any way.
[If you have anything to follow up, please cc: me, because I am still
not reading this list.]
For details about my case, visit http://www.usa1.com/fors or send email
to fund @
stonehenge .
com (content is mostly ignored).
Name: Randal L. Schwartz / Stonehenge Consulting Services (503)777-0095
Keywords: Perl training, UNIX[tm] consulting, video production, skiing, flying
Email: <merlyn @
stonehenge .
com> Snail: (Call) PGP-Key: (finger merlyn @
ora .
com)
Web: <A HREF="http://www.teleport.com/~merlyn/";>My Home Page!</A>
Quote: "I'm telling you, if I could have five lines in my .sig, I would!" -- me
Follow-Ups:
|
|
