Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Device locking #3

Open
mchack-work opened this issue Apr 13, 2023 · 0 comments
Open

Device locking #3

mchack-work opened this issue Apr 13, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@mchack-work
Copy link
Member

Investigate device locking in different operating system.

Trying to run two tkey-runapp at once messes up the firmware but doesn't enter failed state. This works for me as an ordinary non-root user. If the serial package doesn't support device locking we should implement it ourselves somehow on the client side.

Might also need to look into why the firmware isn't in state failed.

% ./tkey-runapp apps/signer/app.bin &; ./tkey-runapp apps/signer/app.bin
[1] 91914
Auto-detected serial port /dev/ttyACM0
Connecting to device on serial port /dev/ttyACM0 ...
Auto-detected serial port /dev/ttyACM0
Connecting to device on serial port /dev/ttyACM0 ...
GetNameVersion failed: ReadFrame: Expected cmdlen 2 (32 bytes), got 1 (4 bytes)
If the serial port is correct, then the TKey might not be in firmware-
mode, and have an app running already. Please unplug and plug it in again.
[1]  + exit 1     ./tkey-runapp apps/signer/app.bin
Firmware name0:'tk m' name1:'kdf' version:0
GetUDI failed: ReadFrame: Message not meant for us: dest 0
@dehanj dehanj transferred this issue from tillitis/tkey-ssh-agent Sep 11, 2023
@dehanj dehanj added the enhancement New feature or request label Sep 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants