[60173] in North American Network Operators' Group
Re: Blocking port 135?
daemon@ATHENA.MIT.EDU (Mans Nilsson)
Sat Aug 2 09:53:15 2003
Date: Sat, 2 Aug 2003 15:52:44 +0200
From: Mans Nilsson <mansaxel@sunet.se>
To: Jack Bates <jbates@brightok.net>
Cc: nanog@merit.edu, Adi Linden <adil@adis.on.ca>
In-Reply-To: <3F2BB81B.1060000@brightok.net>
X-synced-from: Pilsnet
Errors-To: owner-nanog-outgoing@merit.edu
--3XA6nns4nE4KvaS/
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Subject: Re: Blocking port 135? Date: Sat, Aug 02, 2003 at 08:09:47AM -0500=
Quoting Jack Bates (jbates@brightok.net):
> Depends on why you block and interfere. Intention plays a large part=20
> according to law.=20
If people can sue McDonalds for hot coffee, everything is possible. I'm Eur=
opean, so this does not apply, but I'd try to be very careful in .us.
>=20
> Many AUP/TOS aggreements have interesting no-server clauses.=20
Not mine. And, I generally think that with such AUPen, one gets something
one step better than Minitel or I-Mode, which is not Internet.=20
Yes, I'm one of those loud end-to-end guys. =20
> - Setup detection systems and perform immediate contact on accounts that=
=20
> trigger the system to determine if it's legitimate or not. If not, bye=
=20
> bye.
That is wiretapping in Sweden, and illegal without a court order.
I believe. Nobody has gone even close to taking it to court, and I
stay far away from it.
> Of course, this only stops outbound issues. It does nothing to prevent=20
> inbound, and in the event of a worm, you'd better make sure you have=20
> double and triple methodologies in place to stabalize your network.=20
Some of our thinner access lines were up to 50% full when the Slammer hit.=
=20
If there comes a much more evil worm than so, we do have OOB access
to the entire core.. =20
--=20
M=E5ns Nilsson Systems Specialist
+46 70 681 7204 KTHNOC
MN1334-RIPE
CHUBBY CHECKER just had a CHICKEN SANDWICH in downtown DULUTH!
--3XA6nns4nE4KvaS/
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (FreeBSD)
iD8DBQE/K8Is02/pMZDM1cURAphGAKClc45/BW7K3LW2cmBGIEBIojp4zACfQgm5
P0heUmQptkB8ezI64BuB49k=
=hfrN
-----END PGP SIGNATURE-----
--3XA6nns4nE4KvaS/--
