netdev - Re: [PATCH] Fix routing tables with id

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0806032036070.3438@bizon.gios.gov.pl>
Date:	Tue, 3 Jun 2008 20:39:39 +0200 (CEST)
From:	Krzysztof Oledzki <olel@....pl>
To:	davem@...emloft.net, Patrick McHardy <kaber@...sh.net>
cc:	Jarek Poplawski <jarkao2@...il.com>, netdev@...r.kernel.org
Subject: Re: [PATCH]  Fix routing tables with id > 255 for legacy software



On Tue, 3 Jun 2008, Patrick McHardy wrote:

> Krzysztof Oledzki wrote:
>> On Tue, 3 Jun 2008, Patrick McHardy wrote:
>> 
>>> I think the proper solution is what I wrote in the changelog
>>> entry: fix userspace applications when using extended table
>>> IDs.
>> 
>> It is unquestionably true, however it may take some time and people may 
>> still use old version of such applications for whatsoever reasons.
>> 
>>> Your patch makes it more predictable, so I'm not completely
>>> opposed, but still its just a workaround.
>> 
>> Indeed - it is a workaround but I believe we need it.
>
> I'm neither opposed (as long as we don't add CONFIG options for
> this) nor in favour - people using fixed applications won't notice,
> and for other people it substitutes undesired behaviour by more
> predictable undesirable behaviour,

Exactly,

> which is at least no loss :)

OK, so I assume it is a very weak ack-by? ;)

David?

Best regards,

 				Krzysztof Olędzki