From: folkert@vanheusden.com (Folkert van Heusden)
To: Lorenzo Hern?ndez Garc?a-Hierro <lorenzo@gnu.org>
Cc: linux-kernel@vger.kernel.org
Subject: Suggestions for patch
Date: Fri, 4 Mar 2005 22:33:47 +0100 [thread overview]
Message-ID: <20050304213337.GJ6156@vanheusden.com> (raw)
In-Reply-To: <1108317508.9095.183.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1518 bytes --]
Hi,
I have a suggestion for the openbsd net security patch.
In the function static int tcp_v4_get_port(struct sock *sk, unsigned short snum)
there's the code that says:
rover = tcp_port_rover;
(like 224 on the version of tcp_ipv4.c patched with your patch for rc2 of 2.6.11)
I would like to suggest to change it to:
get_random_bytes(&rover, sizeof(rover));
no checks around it: that's already been taken care of in the original
code.
And for the ipv6 code:
diff -uNr tcp_ipv6.c.org tcp_ipv6.c
--- tcp_ipv6.c.org 2005-03-04 22:28:53.181183066 +0100
+++ tcp_ipv6.c 2005-03-04 22:32:56.425994913 +0100
@@ -138,8 +138,8 @@
int remaining = (high - low) + 1;
int rover;
+ get_random_bytes(&rover, sizeof(rover));
spin_lock(&tcp_portalloc_lock);
- rover = tcp_port_rover;
do { rover++;
if ((rover < low) || (rover > high))
rover = low;
Folkert van Heusden
Op zoek naar een IT of Finance baan? Mail me voor de mogelijkheden!
+------------------------------------------------------------------+
|UNIX admin? Then give MultiTail (http://vanheusden.com/multitail/)|
|a try, it brings monitoring logfiles to a different level! See |
|http://vanheusden.com/multitail/features.html for a feature list. |
+------------------------------------------= www.unixsoftware.nl =-+
Phone: +31-6-41278122, PGP-key: 1F28D8AE
Get your PGP/GPG key signed at www.biglumber.com!
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
parent reply other threads:[~2005-03-04 23:43 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1108317508.9095.183.camel@localhost.localdomain>]
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=20050304213337.GJ6156@vanheusden.com \
--to=folkert@vanheusden.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo@gnu.org \
/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
all inboxes | Powered by JetHome®