From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Frank Steiner <fsteiner-mail@bio.ifi.lmu.de>
Cc: markb@wetlettuce.com, linux-kernel@vger.kernel.org
Subject: Re: 2.6.8.1: ip auto-config accepts wrong packages
Date: Thu, 26 Aug 2004 09:17:22 -0700 [thread overview]
Message-ID: <20040826091722.54a0cc72.rddunlap@osdl.org> (raw)
In-Reply-To: <412DBBF0.3090107@bio.ifi.lmu.de>
On Thu, 26 Aug 2004 12:31:12 +0200 Frank Steiner wrote:
| Hi Mark,
|
| in addition to the DEBUG flags I added two little debugging lines to make
| sure the right code is executed.
|
| ipconfig.c:
| if (able & IC_BOOTP){
| DBG(("calling get_random_btyes"));
| get_random_bytes(&d->xid, sizeof(u32));
|
| random.c:
|
| void get_random_bytes(void *buf, int nbytes)
| {
| DEBUG_ENT("get_random_bytes entered\n");
| if (sec_random_state) {
| DEBUG_ENT("sec_random_state\n");
| extract_entropy(sec_random_state, (char *) buf, nbytes,
| EXTRACT_ENTROPY_SECONDARY);
| }
|
|
| And here is the output from boot.msg:
|
|
| <4>IP-Config: Entered.
| <4>calling get_random_btyes<7>random: get_random_bytes entered
| <7>random: sec_random_state
| <7>random: 0000 0000 : going to reseed secondary with 64 bits (32 of 0 requested)
| <7>random: 0000 0000 : trying to extract 64 bits from primary
| <7>random: 0000 0000 : debiting 0 bits from primary
| <7>random: 0000 0000 : trying to extract 32 bits from secondary
| <7>random: 0000 0000 : debiting 32 bits from secondary (unlimited)
| <4>IP-Config: eth0 UP (able=1, xid=07196018)
| <5>Sending BOOTP requests .<7>random: get_random_bytes entered
| <7>random: sec_random_state
| <7>random: 0000 0000 : going to reseed secondary with 64 bits (32 of 0 requested)
| <7>random: 0000 0000 : trying to extract 64 bits from primary
| <7>random: 0000 0000 : debiting 0 bits from primary
| <7>random: 0000 0000 : trying to extract 32 bits from secondary
| <7>random: 0000 0000 : debiting 32 bits from secondary (unlimited)
| <6>tg3: eth0: Link is up at 100 Mbps, full duplex.
| <6>tg3: eth0: Flow control is on for TX and on for RX.
| <4>.DHCP/BOOTP: Got extension 1: ff ff ff 80
| <4>DHCP/BOOTP: Got extension 3: 8d 54 01 82
| <4>DHCP/BOOTP: Got extension 6: 81 bb d6 87
| <4>DHCP/BOOTP: Got extension 17: 2f
| <4>DHCP/BOOTP: Got extension 28: 8d 54 01 ff
| <4>DHCP/BOOTP: Got extension 15: 62 69 6f 2e 69 66 69 2e 6c 6d 75 2e 64 65
| <4> OK
| <4>IP-Config: Got BOOTP answer from 141.84.1.132, my address is 141.84.1.167
| ...
|
| So it looks like the code is executed, but the xid is always the
| same. Just like the random module would not create a random number
| but a constant :-) I'm not good enough in C to really understand
| and further debug the code in random.c or ipconfig.c :-((
Maybe fixed by
http://linux.bkbits.net:8080/linux-2.5/cset@412a4a00MfXRfzWB5kTFo9NXM1Q3hw?nav=index.html|ChangeSet@-7d
i.e., fix is already merged, I think.
--
~Randy
next prev parent reply other threads:[~2004-08-26 16:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-25 9:40 2.6.8.1: ip auto-config accepts wrong packages Frank Steiner
2004-08-25 13:04 ` Mark Broadbent
2004-08-25 14:41 ` Frank Steiner
2004-08-25 15:47 ` Mark Broadbent
2004-08-26 6:39 ` Frank Steiner
2004-08-26 10:31 ` Frank Steiner
2004-08-26 16:17 ` Randy.Dunlap [this message]
2004-08-27 11:42 ` Frank Steiner
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=20040826091722.54a0cc72.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=fsteiner-mail@bio.ifi.lmu.de \
--cc=linux-kernel@vger.kernel.org \
--cc=markb@wetlettuce.com \
/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