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]
Message-Id: <20210309132725.638205-1-avri.altman@wdc.com>
Date:   Tue,  9 Mar 2021 15:27:25 +0200
From:   Avri Altman <avri.altman@....com>
To:     alex.bennee@...aro.org
Cc:     Matti.Moell@...nsynergy.com, arnd@...aro.org, bing.zhu@...el.com,
        hmo@...nsynergy.com, ilias.apalodimas@...aro.org,
        joakim.bech@...aro.org, linux-kernel@...r.kernel.org,
        linux-mmc@...r.kernel.org, linux-nvme@...r.kernel.org,
        linux-scsi@...r.kernel.org, maxim.uvarov@...aro.org,
        ruchika.gupta@...aro.org, tomas.winkler@...el.com,
        yang.huang@...el.com
Subject: [RFC PATCH  0/5] RPMB internal and user-space API + WIP virtio-rpmb frontend

The mmc driver has some hooks to support rpmb access, but access is
mainly facilitated from user space, e.g. mmc-utils.

The ufs driver has no concept of rpmb access - it is facilitated via
user space, e.g. ufs-utils and similar.

Both for ufs and mmc, rpmb access is defined in their applicable jedec
specs. This is the case for few years now - AFAIK No new rpmb-related
stuff is expected to be introduced in the near future.

What problems, as far as mmc and ufs, are you trying to solve by this new subsystem?

Thanks,
Avri

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ