> I admit it: I have never done a telnet to port 80 of a web server of
> which I was not currently an admin.
You may as well have never visited someone else's website, because it's the
same idea. It's a conscious choice you have made for personal reasons.
If i'm interested in whether or not the web service is running on someone's
corporate webserver, and it affects my ability to use it, i'm going to use
the lowest level of overhead in the protocol to figure out why (a direct
socket connection). Whether or not I admin the machine seems pretty
irrelavant. My intent isn't to break in to the box.
> Are these really things that you
> routinely do?
Indeed they are.
> Does your corporate legal department know you do?
My corporate legal department generally has more important things to take
care of than whether or not I'm trying to determine if my favorite websites
are
up, so no, I don't think they have any feelings on the matter.
> Could I go to jail if I had done this? Apparently, the answer is "yes" in
> Sweden, "the law appears to be susceptible to that interpretation" in
Oregon,
> and "maybe" in an unknown number of other jurisdictions.
Perhaps for sequential socket connections to ports, but for:
telnet your.host 80
GET /
or echo "GET /\n" | nc -p 80 your.host
I'm thinking noone really cares. It's the effective equivalent of saying
that
I can't use lynx or a browser written in perl, but netscape and IE are ok.
The whole idea is ludicrous.
>
> David G
> -
> [To unsubscribe, send mail to [EMAIL PROTECTED] with
> "unsubscribe firewalls" in the body of the message.]
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
