Closed clst closed 3 years ago
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: KeeOtp2 - 1.5.3.1(pre).zip
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.
Probably the same reason why stable Arch is still on Keepass 2.47
I will try again once this is resolved.
If you want to look into it here is the crash report:
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.
If all is well the DLLs/plgx files should just work under mono without any changes. Looks like a bug in mono to me.
Maybe some incompatibility with nhotkey or the new troubleshooting page. I don't think its directly connected to this issue.
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.