Firmware debugging patches?
johannes at sipsolutions.net
Sun Jun 8 02:13:12 PDT 2014
On Sun, 2014-06-08 at 11:35 +0300, Kalle Valo wrote:
> > I was thinking we should not add a MAC to the dump, for privacy concerns,
> > but whatever user-space tools gather the dump could add MAC if user perfers.
> The MAC addresses can be extracted from the target memory anyway so I
> don't see harm from including that in the dump. Is it even possible to
> address all privacy issues when dealing with firmware dumps?
We had something of a discussion about this - it's usually not just
BSSIDs/MAC addresses, but also encryption keys (say WEP keys, or at
least temporal keys, sometimes more), SSIDs, etc. In short, there's a
whole bunch of private data that can be included in such dumps.
However, we haven't really found a good solution. Popping up big scary
warnings to the user is unlikely to be productive, trying to keep the
data private and only accessible to (the right) developers is not going
to work ... encryption might work, but who manages that?
Certainly the data shouldn't be attached to a public bug tracker
More information about the ath10k