LKML Archive on
help / color / mirror / Atom feed
From: "Trent Waddington" <>
To: "Jan Engelhardt" <>
Cc: "Linux Kernel Mailing List" <>
Subject: Re: [discuss] portmapping sucks
Date: Thu, 25 Jan 2007 10:19:52 +1000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <Pine.LNX.4.61.0701250030530.32656@yvahk01.tjqt.qr>

On 1/25/07, Jan Engelhardt <> wrote:
> There are a number of common ports in the 512-1023 range. All
> obsolescence and meaninglessness aside, there _are_ rather "important"
> services in that range, ldaps, rtsp, kerberos, rsync, ftps, imaps, just
> to name a few from /etc/services. This map-to-random-port behavior is a
> total DoS thing.

Any reason why you can't make a one line code change to use a better
range?  Or add a blacklist?


  reply	other threads:[~2007-01-25  0:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-24 23:50 Jan Engelhardt
2007-01-25  0:19 ` Trent Waddington [this message]
2007-01-25  3:10 ` Trond Myklebust
2007-01-26  0:14 ` Henrique de Moraes Holschuh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \
    --subject='Re: [discuss] portmapping sucks' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).