-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Wrong otp secrets when importing from 1pux file #10368
Comments
can you explain what is wrong about it? |
So keepassxc uses whole otp string(including issuer name and all the atributes) from 1password as secret value |
your 1Password exports an otp string?? Unfortunately they don't document the totp field: https://support.1password.com/1pux-format/. I had to guess based on using 1Password trial and exporting a bunch of created entries. Unfortunately for now you will just have to manually change the otp string |
My test export looks like this for an entry with two TOTP fields defined, DFDFDF... is the totp secret:
|
Yeah. Like half of my credentials contain otpauth://totp/ string instead of secret |
So I fixed this bug, can I open a pull request? |
Sure can! |
Overview
When importing data from 1pux file, keepassxc import otp string like this
otpauth://totp/credential:email?secret=otpauthtotpcredentialemailsecretACTUAL_SECRET&period=30&digits=6&issuer=issuer_name
and this leads to wrong otp codes
Steps to Reproduce
Expected Behavior
The line in the otp field should be identical to that in 1password
Actual Behavior
The otp line from 1password appears in the secret option in the keepassxc otp line
Debug Information
KeePassXC - Version 2.7.7
Revision: 68e2dd8
Qt 5.15.11
Debugging mode is disabled.
Operating system: macOS 14.3
CPU architecture: arm64
Kernel: darwin 23.3.0
Enabled extensions:
Cryptographic libraries:
Operating System: macOS
The text was updated successfully, but these errors were encountered: