linux-kernel - Re: [v3] wlcore: add missing nvs file name info for wilink8

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: <20170725115805.GU10026@atomide.com>
Date:   Tue, 25 Jul 2017 04:58:06 -0700
From:   Tony Lindgren <tony@...mide.com>
To:     "Reizer, Eyal" <eyalr@...com>
Cc:     Kalle Valo <kvalo@...eaurora.org>,
        "linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "sebastian.reichel@...labora.co.uk" 
        <sebastian.reichel@...labora.co.uk>
Subject: Re: [v3] wlcore: add missing nvs file name info for wilink8

* Reizer, Eyal <eyalr@...com> [170725 04:33]:
> > From: Tony Lindgren [mailto:tony@...mide.com]
> > Hmm so why would we ever even use this bogus nvs file? In addition to
> > warning,
> > I think we should just ignore the bogus nvs file completely.
> > 
> While it looks bogus, it is still at least a valid mac address and the chip will function
> Using it.
> Wilink6/7 doesn't have a  default mac address in hardware (wilink8 does have one)
> so we need to assign one for it so It can work, even if not optimally until configured 
> using the calibrator tool and a unique mac address is assigned to it.

But it's not a unique mac address. What we should do in that case is
use a random mac address just like many USB devices do.

Regards,

Tony