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] [day] [month] [year] [list]
Message-ID: <DB7PR07MB3883AE7ADD2F8A9DC800F2E5ED720@DB7PR07MB3883.eurprd07.prod.outlook.com>
Date:   Mon, 27 Jul 2020 06:57:29 +0000
From:   "Varghese, Martin (Nokia - IN/Bangalore)" <martin.varghese@...ia.com>
To:     David Miller <davem@...emloft.net>,
        "martinvarghesenokia@...il.com" <martinvarghesenokia@...il.com>
CC:     "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        "kuba@...nel.org" <kuba@...nel.org>
Subject: RE: [PATCH net-next] net: Enabled MPLS support for devices of type
 ARPHRD_NONE.

>> From: Martin Varghese <martin.varghese@...ia.com>
>> 
>> This change enables forwarding of MPLS packets from bareudp tunnel 
>> device which is of type ARPHRD_NONE.
>> 
>> Signed-off-by: Martin Varghese <martin.varghese@...ia.com>

> This restriction looks just like a massive guessing game.

> What is needed by MPLS by a device specifically, and can therefore this restrictive test be removed entirely?

I think so . I  will send out a different patch which removes the complete check.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ