linux-kernel - Re: PROBLEM: No static MAC address for usb gadget ethernet via kernel parameter any more.

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]

Date:   Tue, 17 May 2022 18:55:50 +0000 (UTC)
From:   Marian Postevca <posteuca@...ex.one>
To:     Maximilian Senftleben <kernel@...l.msdigital.de>
Cc:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: PROBLEM: No static MAC address for usb gadget ethernet via
 kernel parameter any more.


12 May 2022 16:39:02 Maximilian Senftleben <kernel@...l.msdigital.de>:

> [1.] One line summary of the problem:
>
> No static MAC address for usb gadget ethernet via kernel boot parameter any more.
>
> [2.] Full description of the problem/report:
>
> In 5.15. and before we were able to set a static MAC address for the usb gadget ethernet connection using kernel parameters "g_ether.dev_addr" and "g_ether.host_addr".
> Since 5.16. and more concrete after commit 890d5b40908bfd1a79be018d2d297cf9df60f4ee, this is no longer possible, and a random MAC address is assigned.
> (Possible Regression)
>
> [3.] Keywords (i.e., modules, networking, kernel):
> usb, gadget, mac, g_ether
>
> [4.] Kernel information
> [4.1.] Kernel version (from /proc/version):
> Linux version 5.17.4-141174-ge11818a6ec02 (ms@...al) (arm-v7a-linux-gnueabihf-gcc (OSELAS.Toolchain-2020.08.0 10-20200822) 10.2.1 20200822, GNU ld (GNU Binutils) 2.35) #14 SMP Thu May 12 13:51:50 CEST 2022
> [4.2.] Kernel .config file:
> -
Could you please send the kernel .config file and kernel command line with which you reproduce this issue?