At 11:00 AM 04/22/96, you wrote:
>> However, we have a problem with people sending fakemail with the smtp
>> daemon, by telnetting to port 25 and manually sending mail. Obviously we
>> can not stop people from telnetting to sites off campus, but is is possible
>> to stop it on campus? So far, no solutions have been found. Any
>> help/suggestions would be greatly appreciated, if it is even possible.
>
>One solution would be to pull down sources for a telnet client, and add
>some code to prohibit connections to certain machines, or to specific
>ports on those certain machines. If you're comfortable using C, then you
>should be able to do this in under an hour, IMHO.
>
>Dave Brookshire | Systems Engineer |
Good idea, but with such a diverse range of machines and OS's that the
telnets are coming from, it is next to impossible. Telnetting from unix
based systems is a minor case (probably). We use some unix machines (public
access through telnet). Many PC (dos/windows) based systems in labs. And
people can use their own machines in their rooms with IPX connections as
well as trumpet winsock support. So both DOS and Windows clients work, and
new ones can be added.
I think we need to make a server-side fix. And that is where the problem
arises.
Thanks anyway...
john
_________________________________________________________
John P. Mulligan <mulligaj @
lafayette .
edu>
PGP PUBLIC KEY available at http://www.lafayette.edu/~mulligaj
_________________________________________________________
"Perhaps you think your Email is legitimate enough that encryption is
unwarranted. If you really are a law-abiding citizen with nothing to hide,
then why don't you always send your paper mail on postcards? ... Are
you trying to hide something?" --- Pretty Good Privacy (PGP) Manual
Follow-Ups:
|
|
