[179031] in North American Network Operators' Group
Re: Frontier: Blocking port 22 because of illegal files?
daemon@ATHENA.MIT.EDU (Eygene Ryabinkin)
Thu Mar 26 00:21:52 2015
X-Original-To: nanog@nanog.org
Date: Thu, 26 Mar 2015 07:21:45 +0300
From: Eygene Ryabinkin <rea+nanog@grid.kiae.ru>
To: "Aaron C. de Bruyn" <aaron@heyaaron.com>
In-Reply-To: <CAEE+rGqimJYAfgmzm9AJ72+gcmJxfZLM7n4Rf03vynxKN=Qfeg@mail.gmail.com>
Cc: NANOG mailing list <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
Wed, Mar 25, 2015 at 07:31:35PM -0700, Aaron C. de Bruyn wrote:
> Just a friendly heads-up to anyone from Frontier who might be
> listening, I have a few additional ports you may wish to block:
>
> 80 - Allows users to use Google to search for illegal files
> 443 - Allows users to use Google to search for illegal files in a secure manner
> 69 - Allows users to trivially transfer illegal files
> 3389 - Allows users to connect to unlicensed Windows machines
> 179 - Allows users to exchange routes to illegal file shares
> 53 - Allows people to look up illegal names
Can't help to add that there are
- port 21 that allow users to give commands to examine
the existence and initiate transfers of illegal files;
- ports 1025 - 65535 that allow users to create data streams
to actually transfer illegal files in an (oh my) passive mode.
;)
--
Eygene Ryabinkin, National Research Centre "Kurchatov Institute"
Always code as if the guy who ends up maintaining your code will be
a violent psychopath who knows where you live.
