a.borque

Hello! Thanks for your reply! I take it then that there is no common way of storing OTP information amongst all implementations and to achieve best compatibility the data needs to be stored twice. Don't get me wrong, as a mere user I am not in a position to critizize different ways of implementation. But from that users point of view it was -amongst other things- always a great advantage that all applications supporting a certain database level were compatible in most relevant aspects. As OTP is...

Hello! Thanks for your reply! I take it then that there is no common way of storing OTP information amongst all implementations and to achieve best compatibility the data needs to be stored twice. Don't get me wrong, as a mere user I am not in a position to critizize different ways of implementation. But from that users point of view it was -amongst other things- always a great advantage that all applications supporting a certain database level were compatible in most relevant aspects. As OTP is...

Hello! I have started to store TOTP-information in a seperate KeePass-database which I created on my mobile because scanning QR codes is easier there. When I copied that database to my other devices I noticed that KeePass 2.52 is not able to interpret the additional fields and thus can not generate TOTP-codes. I tried KeePassXC and it works there. On the other hand TOTP-entries created by KeePass 2.52 are not working in KeePassXC and on my mobile. Digging a bit deeper into that topic I learned that...

I have not tried to use the version provided in the ppa you provided above. But this ppa has no connection with Debians official repositories and sources which receive their security support. And for these I have little hope for Bookworm. I wouldn't mind if future proffed me wrong, though! ;-)

I have not tried to use the version provided in the ppa you provided above. But for Bookworms official repositories and sources which receive security support directly from Debian I have little hope... I wouldn't mind if future proffed me wrong, though! ;-)

The unresolved bug seems to be in Debians package not in KeePass, it can be seen here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000338 Regarding the "testing"-status: Given that there has not been any recent activity of the package maintainer ( https://tracker.debian.org/pkg/keepass2 ) and the fact that the staged freeze prepariing the release in summer 2023 will beginn on 2023-01-12 I fear that KeepAss won't be part of the next debian release (at least not in the official repositories...

Hello! Last week I had to update my Debian from the current version 11 (Bullseye) to the upcoming release 12 (Bookworm) due to new hardware. Though this is currently in testing the freeze-period is beginning in a few days and no new packages will be added than. So I was surprised to see that KeePass 2 was removed during the upgrade. The update-history shows very little activity for the package, in fact the last version there was 2.47 and it was removed due to an unresolved bug on 2022-01-06. The...

Hello! Thanks for the reply, I will try this. And a big Thank you for 7-Zip in general!!! The file I want to backup is a firebird-db, which I set to backup mode using nbackup (ie all new data is written to a seperate "delta-file", but old data is read from the database). So it should be read only. I asked this question specifically for firebird before but got no reply, so I chose this more general way and asked again. Thanks again A.Borque