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:   Thu, 2 Aug 2018 21:58:02 +0000
From:   Vineet Gupta <Vineet.Gupta1@...opsys.com>
To:     Alexey Brodkin <Alexey.Brodkin@...opsys.com>,
        "linux-snps-arc@...ts.infradead.org" 
        <linux-snps-arc@...ts.infradead.org>
CC:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Rob Herring <robh+dt@...nel.org>,
        "stable@...r.kernel.org" <stable@...r.kernel.org>,
        "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>
Subject: Re: [PATCH] ARC: AXS10x/HSDK: Allow U-Boot to pass MAC-address to
 the kernel

On 08/02/2018 03:19 AM, Alexey Brodkin wrote:
> Otherwise kernel uses random MAC which is not very conveniet.

Curious what exactly is the issue - why does the user care what MAC is assigned ?

> With that change in place use might set desired MAC in U-Boot
> with "setenv ethaddr 11:22:33:44:55:66", save environment and
> then from boot to boot the same MAC will be used by the kernel.
>

And what if one is running without uboot - it will resort to all zeros vs. random
yet working MAC ?


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ