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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20080603182947.GB2727@ami.dom.local>
Date:	Tue, 3 Jun 2008 20:29:47 +0200
From:	Jarek Poplawski <jarkao2@...il.com>
To:	Patrick McHardy <kaber@...sh.net>
Cc:	Krzysztof Oledzki <olel@....pl>, netdev@...r.kernel.org
Subject: Re: [PATCH]  Fix routing tables with id > 255 for legacy software

On Tue, Jun 03, 2008 at 07:58:42PM +0200, Patrick McHardy wrote:
> Jarek Poplawski wrote:
...
>> IMHO, adding a safety with e.g. CONFIG_IP_FIB_COMPAT_DEPRECATED
>> (default N) for one stable, letting to change this back in some
>> (probably nonexistent) strange cases, should be enough to keep up
>> appearances...
>
>
> Mhh .. I don't think this is a good solution. Things can
> only break if you actually use the new feature, and if
> you do, you should simply make sure that all software
> running can deal with it. Fixing the routing daemons
> should be a triviality.

But, I think, you've written earlier there is no good solution. And,
probably, there is no way to make sure. This is mainly for appearances
(niceness), and maybe let us know if the problem really existed. But,
I don't insist on this...

Jarek P.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html