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]
Date:	Thu, 01 Dec 2011 08:13:57 +0100
From:	Rémi Denis-Courmont <remi@...lab.net>
To:	<netdev@...r.kernel.org>
Subject: Re: [RFC 2/3] if_ether.h: Add IEEE 802.1 Local Experimental Ethertype 1.

On Wed, 30 Nov 2011 21:44:05 +0100, Sjur Br��ndeland
<sjur.brandeland@...ricsson.com> wrote:
> From: Sjur Brændeland <sjur.brandeland@...ricsson.com>
> 
> Add EthType 0x88b5.
> This Ethertype value is available for public use for prototype and
> vendor-specific protocol development,as defined in Amendment 802a
> to IEEE Std 802.

I don't think you can just go and steal a reserved EtherType. What if some
user-space (using packet sockets) or out-of-tree kernel driver does actual
"experiment" with this type?

Why don't you define your own link-layer, e.g. with a vendor-specific CDC
profile?

-- 
Rémi Denis-Courmont
http://www.remlab.net/
--
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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ