although i think that it is dumb... it is their network, so if they want to restrict that... they can... but...

their response of...

        "as a BYU student this behavior is unacceptable and if it
        continues will be reported to the honor code office"


...is a stupid!


why is everything so extreme? what in the flying fig newton does port scanning your own server have to do with the honor code office?

why can't they simply inform you that BYU has a policy against port scanning from on campus?


On Tuesday, Aug 26, 2003, at 09:39 US/Mountain, Hans Fugal wrote:


Naturally you shouldn't be portscanning other people's computers
anywhere, but don't even try portscanning your own off-campus server
from on campus because BYU appears to be monitoring their logs for
things. That's reassuring. The fact that they were two weeks late in
contacting me about the portscan I did weakens that feeling of
reassurance, though...

When I notified them that I was just scanning my own server to verify
the firewall they politely said 'as a BYU student this behavior is
unacceptable and if it continues will be reported to the honor code
office'. I suggest you just stay off the radar and avoid portscanning
from on campus period.

--
 Hans Fugal                 | De gustibus non disputandum est.
 http://hans.fugal.net/     | Debian, vim, mutt, ruby, text, gpg
 http://gdmxml.fugal.net/   | WindowMaker, gaim, UTF-8, RISC, JS Bach
---------------------------------------------------------------------
GnuPG Fingerprint: 6940 87C5 6610 567F 1E95  CB5E FC98 E8CD E0AA D460
<mime-attachment>____________________
BYU Unix Users Group
http://uug.byu.edu/
___________________________________________________________________
List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list



____________________
BYU Unix Users Group http://uug.byu.edu/ ___________________________________________________________________
List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list

Reply via email to