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

How to extract OAUTH (TOTP keys) from a pico-tool dump? #139

New Issue
Open
opened 2025-04-03 14:01:48 +08:00 by fucksophie · 11 comments
fucksophie commented 2025-04-03 14:01:48 +08:00 (Migrated from github.com)
Copy Link

I dumped the memory of my pico a while back, and the pico has now died and I need to get my TOTP keys out. How do I do that?

I dumped the memory of my pico a while back, and the pico has now died and I need to get my TOTP keys out. How do I do that?
polhenarejos commented 2025-04-07 00:34:35 +08:00 (Migrated from github.com)
Copy Link

Is it recognized by picotool?

Is it recognized by `picotool`?
fucksophie commented 2025-04-07 21:43:47 +08:00 (Migrated from github.com)
Copy Link

Yes.

Yes.
polhenarejos commented 2025-04-08 05:10:59 +08:00 (Migrated from github.com)
Copy Link

Then you can backup and restore the entire flash memory to another device. It will generate new FIDO credentials and older will not be recognized but in the case of OTP should work since it uses another filesystem.

Then you can backup and restore the entire flash memory to another device. It will generate new FIDO credentials and older will not be recognized but in the case of OTP should work since it uses another filesystem.
fucksophie commented 2025-04-08 20:44:02 +08:00 (Migrated from github.com)
Copy Link

Then you can backup and restore the entire flash memory to another device. It will generate new FIDO credentials and older will not be recognized but in the case of OTP should work since it uses another filesystem.

The death of the pico was because I applied a update to it, and that update has made it so I cannot access yubikey.

> Then you can backup and restore the entire flash memory to another device. It will generate new FIDO credentials and older will not be recognized but in the case of OTP should work since it uses another filesystem. The death of the pico was because I applied a update to it, and that update has made it so I cannot access yubikey.
fucksophie commented 2025-04-08 21:10:18 +08:00 (Migrated from github.com)
Copy Link

Thanks, I tried a bunch of different UF2's, untill I saw that the pid:vid of the pico key was 0000:0000. I was running into #118 , I updated my pico key, and then comissioned it, and then all of my fido stuffs dissapeared. Is there a way to recover them? Passkeys are gone, but all of the normal OAUTH stuff is still there.

Thanks, I tried a bunch of different UF2's, untill I saw that the pid:vid of the pico key was 0000:0000. I was running into #118 , I updated my pico key, and then comissioned it, and then all of my fido stuffs dissapeared. Is there a way to recover them? Passkeys are gone, but all of the normal OAUTH stuff is still there.
polhenarejos commented 2025-04-08 21:16:23 +08:00 (Migrated from github.com)
Copy Link

Try the development version and commission it through the web. It should work unless you installed another firmware prepared for less memory that overwrote the previous map.

Try the development version and commission it through the web. It should work unless you installed another firmware prepared for less memory that overwrote the previous map.
fucksophie commented 2025-04-08 23:02:26 +08:00 (Migrated from github.com)
Copy Link

I am using the development version, commissioned through web. All passkey stuff is gone, I didnt use another firmware with less memory, only
pico_fido_seeed_xiao_rp2040-6.4.uf2
pico_fido_seeed_xiao_rp2040-6.4.uf2 (development ver)
pico_fido_seeed_xiao_rp2040-6.4.yubikey5.uf2 (pico patcher version)

and almost flashed pico_hsm_seeed_xiao_rp2040-6.4.uf2, however I noticed it's the "pico_hsm" version.

I am using the development version, commissioned through web. All passkey stuff is gone, I didnt use another firmware with less memory, only `pico_fido_seeed_xiao_rp2040-6.4.uf2` `pico_fido_seeed_xiao_rp2040-6.4.uf2 (development ver)` `pico_fido_seeed_xiao_rp2040-6.4.yubikey5.uf2 (pico patcher version)` and almost flashed `pico_hsm_seeed_xiao_rp2040-6.4.uf2`, however I noticed it's the "pico_**hsm**" version.
polhenarejos commented 2025-04-08 23:24:19 +08:00 (Migrated from github.com)
Copy Link

Probably the HSM wiped all the previous data.

Probably the HSM wiped all the previous data.
fucksophie commented 2025-04-08 23:31:03 +08:00 (Migrated from github.com)
Copy Link

Would not make sense, all OAUTH info would be gone, but it's still there.

Would not make sense, all OAUTH info would be gone, but it's still there.
fucksophie commented 2025-11-23 04:48:20 +08:00 (Migrated from github.com)
Copy Link

@polhenarejos Cannot seem to get the passkeys out of it in any way shape or form. Even the previous dumps I can't get the passkey.

Is there a way that I can emulate the passkey or spoof it to get access to a bunch of my accounts?

@polhenarejos Cannot seem to get the passkeys out of it in any way shape or form. Even the previous dumps I can't get the passkey. Is there a way that I can emulate the passkey or spoof it to get access to a bunch of my accounts?
polhenarejos commented 2025-11-23 05:45:10 +08:00 (Migrated from github.com)
Copy Link

You would need a special firmware to do so.

You would need a special firmware to do so.
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
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#139
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?