From: Lennert Buytenhek <buytenh@wantstofly.org>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: "Lorenzo Hernández García-Hierro" <lorenzo@gnu.org>,
linux@horizon.com, mingo@elte.hu,
"Arjan van de Ven" <arjan@infradead.org>,
bunk@stusta.de, "Chris Wright" <chrisw@osdl.org>,
davem@redhat.com, "Hank Leininger" <hlein@progressive-comp.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
netdev@oss.sgi.com, Valdis.Kletnieks@vt.edu,
spender@grsecurity.net
Subject: Re: [PATCH] OpenBSD Networking-related randomization port
Date: Thu, 3 Feb 2005 21:14:08 +0100 [thread overview]
Message-ID: <20050203201408.GB3199@xi.wantstofly.org> (raw)
In-Reply-To: <20050203115127.3245951f@dxpl.pdx.osdl.net>
On Thu, Feb 03, 2005 at 11:51:27AM -0800, Stephen Hemminger wrote:
> Recent 2.6 does a more advanced form of port randomization already
> using address hash at connect time. tcp_v4_get_port is only used for
> the case of applications that explicitly bind to port zero to find a
> free port.
Is any such randomisation done or planned for UDP?
--L
next prev parent reply other threads:[~2005-02-03 20:14 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-28 17:17 [PATCH] OpenBSD Networking-related randomization port Lorenzo Hernández García-Hierro
2005-01-28 17:40 ` Adrian Bunk
2005-01-28 17:47 ` Lorenzo Hernández García-Hierro
2005-01-28 18:18 ` Stephen Hemminger
2005-01-28 18:54 ` Lorenzo Hernández García-Hierro
2005-01-28 19:09 ` Adrian Bunk
2005-01-28 18:02 ` Stephen Hemminger
2005-01-28 18:31 ` Lorenzo Hernández García-Hierro
2005-01-28 18:52 ` Stephen Hemminger
2005-01-28 18:58 ` Lorenzo Hernández García-Hierro
2005-01-28 20:34 ` Lorenzo Hernández García-Hierro
2005-01-28 20:45 ` David S. Miller
2005-01-28 21:34 ` Stephen Hemminger
2005-01-28 21:45 ` David S. Miller
2005-01-29 6:59 ` Andi Kleen
2005-01-28 20:47 ` Arjan van de Ven
2005-01-28 22:12 ` Lorenzo Hernández García-Hierro
2005-01-29 8:04 ` Arjan van de Ven
2005-01-29 8:05 ` Arjan van de Ven
2005-01-29 9:15 ` Valdis.Kletnieks
2005-01-31 16:50 ` Adrian Bunk
2005-01-31 17:23 ` Lorenzo Hernández García-Hierro
2005-01-31 20:11 ` Ingo Molnar
2005-01-31 23:27 ` linux
2005-02-12 22:29 ` Andi Kleen
2005-02-12 23:25 ` linux
2005-02-13 0:18 ` Roland Dreier
2005-02-13 1:41 ` linux
2005-02-02 17:17 ` linux
2005-02-02 17:38 ` Lorenzo Hernández García-Hierro
2005-02-03 19:51 ` Stephen Hemminger
2005-02-03 20:14 ` Lennert Buytenhek [this message]
2005-01-31 19:42 ` Valdis.Kletnieks
2005-01-31 20:03 ` Lorenzo Hernández García-Hierro
2005-02-01 23:22 ` Matt Mackall
2005-01-28 18:04 ` Jörn Engel
2005-01-28 18:07 ` Arjan van de Ven
2005-01-28 18:36 ` Lorenzo Hernández García-Hierro
2005-02-01 14:54 ` Bill Davidsen
2005-01-28 19:24 ` Horst von Brand
2005-01-29 18:16 ` Florian Weimer
2005-01-28 19:24 Hank Leininger
2005-01-29 7:24 linux
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050203201408.GB3199@xi.wantstofly.org \
--to=buytenh@wantstofly.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=arjan@infradead.org \
--cc=bunk@stusta.de \
--cc=chrisw@osdl.org \
--cc=davem@redhat.com \
--cc=hlein@progressive-comp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@horizon.com \
--cc=lorenzo@gnu.org \
--cc=mingo@elte.hu \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.org \
--cc=spender@grsecurity.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).