netdev - Re: [RFC PATCH net-next] bridge: Implement MLD Querier wake-up calls / Android bug workaround

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]

Message-Id: <20200816.211002.1955628031429504263.davem@davemloft.net>
Date:   Sun, 16 Aug 2020 21:10:02 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     linus.luessing@...3.blue
Cc:     netdev@...r.kernel.org, roopa@...ulusnetworks.com,
        nikolay@...ulusnetworks.com, bridge@...ts.linux-foundation.org,
        gluon@...beck.freifunk.net, openwrt-devel@...ts.openwrt.org
Subject: Re: [RFC PATCH net-next] bridge: Implement MLD Querier wake-up
 calls / Android bug workaround

From: Linus Lüssing <linus.luessing@...3.blue>
Date: Sun, 16 Aug 2020 22:24:24 +0200

> I'm aware that this is quite a hack, so I'm unsure if this is suitable
> for upstream. On the other hand, the Android ticket isn't moving
> anywhere and even if it were fixed in Android, I'd expect it to take
> years until that fix would propagate or unpatched Android devices to
> vanish. So I'm wondering if it should be treated like a hardware bug
> workaround and by that should be suitable for applying it upstream in
> the Linux kernel?

Long after those Android devices are deprecated and no longer used, we
will still have this ugly hack in the tree.

Sorry, we're not doing this.