diff options
author | Craig Hesling <hesling@chromium.org> | 2019-10-18 08:52:12 -0700 |
---|---|---|
committer | Commit Bot <commit-bot@chromium.org> | 2019-11-18 20:03:11 +0000 |
commit | 7353ca106319d64962b7a6ccf2c9e88e701e2368 (patch) | |
tree | 6eff8f4452ba2f510404cc1cb32c8bdbcd2ddfe6 /chip/nrf51 | |
parent | ade2bda733d09458f923e37c67a8b0bc304d906b (diff) | |
download | chrome-ec-7353ca106319d64962b7a6ccf2c9e88e701e2368.tar.gz |
fpsensor: Make fpcapture and fpenroll restricted
There should be no functional difference to fpcapture or fpenroll,
since the restricted console command feature is implemented in a
similar manor.
The only noticeable difference is that the list of commands provided
by the "help" command should denote when these commands are restricted.
Note, each board requires a configuration, similar
to crrev.com/c/1867388, in order to activate restricted
console commands. Otherwise, this restricted flag has no
restricting effect.
BRANCH=nocturne
BRANCH=hatch
BUG=b:142559996, b:142505927
TEST=# Test on nocturne_fp
make BOARD=nocturne_fp
scp build/nocturne_fp/ec.bin dut1:~/
ssh dut1 flash_fp_mcu ./ec.bin
# From FPMCU UART console
version
# Ensure that version is custom based on workstation
help
# Ensure that fpcapture and fpenroll are not prefixed
# with "-"
help list
# Ensure that a "Flags" column exists and that
# fpcapture and fpenroll both have a 1 in the column.
fpcapture
fpenroll
# Ensure that both commands above succeed in their
# own operations
syslock
fpcapture
fpenroll
# Ensure that both commands above fail with "Access Denied"
help
# Ensure that fpcapture and fpenroll are now prefixed
# with "-" in the help message
Change-Id: Icbb74a1afece66db9ebd071de0770650d42bd553
Signed-off-by: Craig Hesling <hesling@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/1869400
Reviewed-by: Daisuke Nojiri <dnojiri@chromium.org>
Reviewed-by: Tom Hughes <tomhughes@chromium.org>
Diffstat (limited to 'chip/nrf51')
0 files changed, 0 insertions, 0 deletions