From: Eric Dong <eric.dong@intel.com>
To: edk2-devel@lists.01.org
Subject: [Patch 0/2] Fixed correct password not works issue
Date: Tue, 10 Jul 2018 12:01:50 +0800 [thread overview]
Message-ID: <20180710040152.5812-1-eric.dong@intel.com> (raw)
Opal device may have an count in firmware to decide whether to resistent
user input password. If yes, even correct password will be reject by device
firmware. This count will be reset only after an cold reboot or user input
correct password.
Opal driver also has an internal count to decide whether allowed user to input
password. A reboot (code or hot) action will reset this count.
Current implementation just base on the count in opal driver to decide whether
allow user to input password again. In this case, if the count in opal device
already exceeded, even an correct password will be rejected.
New solution will check both count, either cout exceed will cause opal driver
report count exceed and a shutdown required.
Eric Dong (2):
SecurityPkg/TcgStorageOpalLib: Return AUTHORITY_LOCKED_OUT error.
SecurityPkg/OpalPassword: Fixed input correct password not works issue
SecurityPkg/Library/TcgStorageOpalLib/TcgStorageOpalUtil.c | 10 +++++++++-
SecurityPkg/Tcg/Opal/OpalPassword/OpalDriver.c | 9 +++++++++
2 files changed, 18 insertions(+), 1 deletion(-)
--
2.15.0.windows.1
next reply other threads:[~2018-07-10 4:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-10 4:01 Eric Dong [this message]
2018-07-10 4:01 ` [Patch 1/2] SecurityPkg/TcgStorageOpalLib: Return AUTHORITY_LOCKED_OUT error Eric Dong
2018-07-10 4:01 ` [Patch 2/2] SecurityPkg/OpalPassword: Fixed input correct password not works issue Eric Dong
2018-07-10 7:21 ` [Patch 0/2] Fixed " Wu, Hao A
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180710040152.5812-1-eric.dong@intel.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox