dearsky/pico-fido
1
0
Fork 0
Code Issues 46 Pull Requests 1 Actions Packages Projects Releases 22 Wiki Activity

OTP update doesn't work #141

New Issue
Closed
opened 2025-04-08 23:50:13 +08:00 by polhenarejos · 4 comments
polhenarejos commented 2025-04-08 23:50:13 +08:00 (Migrated from github.com)
Copy Link

To put it simply, as long as the otp is set to challenge the password attribute of the modified slot, the challenge data will be damaged and the challenge verification will fail.
For example, after setting the challenge, setting the password through the ykman otp settings -A 576bc54882f3 2 command will cause the challenge verification to fail.

By @IsayIsee

To put it simply, as long as the otp is set to challenge the password attribute of the modified slot, the challenge data will be damaged and the challenge verification will fail. For example, after setting the challenge, setting the password through the ykman otp settings -A 576bc54882f3 2 command will cause the challenge verification to fail. By @IsayIsee
polhenarejos commented 2025-04-09 01:01:00 +08:00 (Migrated from github.com)
Copy Link

Fixed in 3212f95.

Tested with:

ykman otp chalresp 1 -T -f JBSWY3DPEHPK3PXP
ykman otp calculate 1 -T   
ykman otp settings -f -A 576bc54882f3 1   
ykman otp calculate 1 -T   
ykman otp --access-code 576bc54882f3 settings -f --delete-access-code 1
ykman otp calculate 1 -T

all three produce the same result.

Fixed in 3212f95. Tested with: ``` ykman otp chalresp 1 -T -f JBSWY3DPEHPK3PXP ykman otp calculate 1 -T ykman otp settings -f -A 576bc54882f3 1 ykman otp calculate 1 -T ykman otp --access-code 576bc54882f3 settings -f --delete-access-code 1 ykman otp calculate 1 -T ``` all three produce the same result.
IsayIsee commented 2025-04-09 08:55:59 +08:00 (Migrated from github.com)
Copy Link

@polhenarejos

The test challenge successfully adds/deletes passwords, but the button's trigger setting still defaults from press to passive

Image

@polhenarejos The test challenge successfully adds/deletes passwords, but the button's trigger setting still defaults from press to passive ![Image](https://github.com/user-attachments/assets/bab130bd-26ea-4a5f-bb1b-db35b80847b2)
polhenarejos commented 2025-04-10 01:50:21 +08:00 (Migrated from github.com)
Copy Link

Passive means the challenge does not requiere touch. If you configure the slot with "Require touch", a "Press" will appear instead of "Passive".

Passive means the challenge does not requiere touch. If you configure the slot with "Require touch", a "Press" will appear instead of "Passive".
IsayIsee commented 2025-04-10 08:38:47 +08:00 (Migrated from github.com)
Copy Link

@polhenarejos but i set need touch, after add password the touch is not need

Image

@polhenarejos but i set need touch, after add password the touch is not need ![Image](https://github.com/user-attachments/assets/e28327eb-a1c8-4186-8d20-9d9a69836244)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something isn't working
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 good first issue
Good for newcomers
 help wanted
Extra attention is needed
 invalid
This doesn't seem right
 question
Further information is requested
 wontfix
This will not be worked on
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
dearsky
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dearsky/pico-fido#141
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?