-
-
Notifications
You must be signed in to change notification settings - Fork 12
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
OTP Secret is not detected if there is an otp
string entry from a different plugin
#16
Comments
Hi @clst, I'm still working on it. Basically it is hard to resolve the error, which happens when closing. I assume to present you a pre-release tomorrow. Kind regards |
Hi @clst, I have tried to fix your issue. Its complicated, I cant figure out, why KeePassOtp is crashing when closing KeePass. Anyway, I have implemented the "otpauth://" uri feature, so this will work for now. I will come back and tell you, if I have fixed the issue with KeePassOtp. Here you have a pre-release with the implemented uri feature: Just give it a try and feel free to comment any problems, bugs or enhancements. Kind regards |
Accidentally closed. |
Hi @tiuub, Sorry for taking so long to try it. Somehow all versions of the plugin > 1.5.3.0 crash Keepass on my Arch Linux. It seems some incompatibility with mono. If you want to look into it here is the crash report: Wall of text with 1.5.3.1(pre)
With 1.5.4.1 mono/keepass detects a problem, tells me my Keepass is too old and doesn't load the plugin. |
Oh I see. Your on Linux. I will build up an VM with Linux to get an better understanding of this issue. Please give me some time. I will notify you, if I have a patch for you. Kind regards |
I was using KeeOtp2 on my Linux box and KeeOTP or KeePassOTP on the Windows PCs. |
OTP Secret is not detected if there is an
otp
string entry from a different plugin (KeePassOTP).Version: 1.5.3.0
TimeOtp-Secret-Base32
is correctly created and auto-type works but the setup dialog keeps appearing.Renaming
otp
fixes the issue. (But then KeePassOTP stops working on the other PC).My
otp
contains a standard otpauth:// string. Maybe it could be a candidate for an automatic fallback/import.The text was updated successfully, but these errors were encountered: