linux-kernel - Re: [PATCH 1/1] MAINTAINERS: add Hridya and myself into Android driver maintainers list

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: <CAEXW_YQ5VoN6DZcfJH_4u5MnRc0vybY7zYH3Y_WD=j3u-RRVHQ@mail.gmail.com>
Date:   Thu, 9 Jul 2020 09:03:13 -0400
From:   Joel Fernandes <joel@...lfernandes.org>
To:     Greg KH <gregkh@...uxfoundation.org>
Cc:     Suren Baghdasaryan <surenb@...gle.com>,
        Hridya Valsaraju <hridya@...gle.com>,
        Todd Kjos <tkjos@...gle.com>,
        Christian Brauner <christian@...uner.io>,
        Arve Hjønnevåg <arve@...roid.com>,
        Martijn Coenen <maco@...roid.com>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/1] MAINTAINERS: add Hridya and myself into Android
 driver maintainers list

On Thu, Jul 9, 2020 at 4:18 AM Greg KH <gregkh@...uxfoundation.org> wrote:
> And I thought we were deleting ashmem soon?

This seems harder than initially thought. The Android userspace is
intertwined with ashmem in various ways (security policies, apps etc).
There were various concerns with old apps using /dev/ashmem directly
without going through library layers and that such apps could not be
upgraded. Various approaches were tried to work around this by
different folks to varying degrees of effect. Also, I am no longer
with the Android team at Google, but I continue to work with them
upstream.

Fwiw, I will continue reviewing this and other Android code from my
side. Thanks.