At 10:12 AM -0800 2/7/00, Brandon Dudley wrote:
>
>BTW: I work for excite@Home, and just wanted to let you know that the pricing
>and service levels and such are set by the cable partners, not by us.
>
>B
Who sets the policies, like "no servers" (whatever that means)? In
this day of HTML only documentation, it's difficult to get by without
running an HTTP server on one's house network. And I'm not allowed
to run X clients on remote machines, because I need an X "server"
running on my local machine? Personally I think that policy needs a
great deal of clarification.
I have an ATT@Home account, and I interpret that "no servers" to mean
that I shouldn't let others use my machines or bandwidth. I run
"servers" on my machines (qmail, for example), that are strictly
controlled either by passwords or by the remote IP addresses allowed
to access them or both. I run portsentry on my machine, which
listens on lots of ports (so I suppose could be considered a
"server"), so I can detect the script kiddies that hunt on @Home (and
recently, the scans for NNTP proxies from @Home itself) and take
appropriate action. That *I* should be able to use my own machines
from wherever I am on the Internet I take as a given. That's what
Internet connectivity is all about. I did it with dialups (machines
dialed in using cron so I could get to them while I was at work), so
I'll do it with cable.
--
Paul J. Schinder
NASA Goddard Space Flight Center
Code 693
[EMAIL PROTECTED]
