--1SQmhf2mF2YjsYvc
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Naturally you shouldn't be portscanning other people's computers
anywhere, but don't even try portscanning your own off-campus server
=66rom 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
=66rom on campus period.

--=20
 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

--1SQmhf2mF2YjsYvc
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/S38h/JjozeCq1GARAsIUAJ99WJ3hRFSw+Ou+AaA/f37kT2LIqgCgx8DM
vW/gEuJTCstRJsvqPYXeGQM=
=iBAz
-----END PGP SIGNATURE-----

--1SQmhf2mF2YjsYvc--

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

Reply via email to