On Wednesday, July 19, 2017 at 5:43:39 PM UTC-4, 0brand wrote: > Which Keepass? On debian: > > I use the same as you Keepassx. > > > > I'm thinking it may have something to do with dom0 backup/restore. I have > multiple 512 Gib usb drives i do backups on. I don't want to try to restore > from one of my other ones because I'm afraid they may become corrupted as > well. > > > > My next step doing a fresh install on my other hard drive and see if I can > restore my kepassx databases onto that. If that does not work I guess I'm out > of luck. > > > > > > > Sent with ProtonMail Secure Email. > > > > -------- Original Message -------- > > Subject: Re: [qubes-users] Re: Keepass vault password no worky > > Local Time: July 19, 2017 3:53 PM > > UTC Time: July 19, 2017 3:53 PM > > From: [email protected] > > To: qubester <[email protected]>, qubes-users <[email protected]>, > [email protected] > > > > qubester: > > > On 07/18/2017 02:27 PM, "0brand" via qubes-users wrote: > > >> I"ve been trying to resolve a problem with both of my Debian-8 > > >> vault-appvms.. For some reason my Keepass passwords no longer work. > > >> When I type in the password I get this message: > > >> Unable to open database. Wrong key or database file is corrupt > > >> I have been using the same password for both my Keepass databases for > > >> quite some time now so the problem isn"t due to forgetting or > > >> miss-typing my passwords. Normally this would not be much of a problem > > >> except for the fact that restoring from backups is not remedying the > > >> issue. I"ve restored both my Keepass vault-appvms and my Debian-8 > > >> Template. > > >> Looking back at the day before this happened there is only one thing > > >> that I did that may have contributed to the problem. I removed my > > >> sys-usb (netvm) and created a sys-usb (appvm). After I created the new > > >> sys-usb I realized that It would not run unless I set pci_strictreset > > >> to false. This was not acceptable to me so I removed the new sys-usb > > >> and created a new one with: > > >> sudo qubesctl top.enable qvm.sys-usb > > >> sudo qubesctl top.enable qvm.sys-usb > > >> The reason I think this may have contributed to the problem is because > > >> the first two times I tried to restore my appVMs things did not go > > >> well. The first time the Gui completely froze and I was unable to > > >> unmount the drive. The second time the backup-restore did not complete > > >> but at least the screen did not freeze up. The third time I used a > > >> backup from a couple days prior and everything went smoothly. It did > > >> not solve the problem though. I still can not unlock my Keepass vaults. > > >> I"m not really sure what to do next. Is it possible that my backups > > >> are somehow being corrupted when I restore them? I"m a little > > >> flustered at this point and I could use some guidance. > > >> Thanks in advance > > >> > > >> Sent with [ProtonMail](https://protonmail.com) Secure Email. > > >> > > > > > > If it makes you feel better, I had the thing fail. with the same > > > messages, and I"d swear, I did nothing at all, after that I stopped > > > using it ..... as pretty pointless to use something that MUST be > > > reliable and have it fail so easily, whatever caused it IMHO of course > > > ; I think mine was in the Vault VM > > > > > > > Which Keepass? On debian: > > > > user@host:~$ apt-cache search keepass > > keepass2 - Password manager > > keepass2-doc - Password manager - Documentation > > keepassx - Cross Platform Password Manager > > kpcli - command line interface to KeePassX password manager databases > > libfile-keepass-perl - interface to KeePass V1 and V2 database files > > > > I ask because I have been using keepassx for three or four years with > > only two databases. I keep multiple copies on different storage devices > > and I have had only one copy ever become corrupt, but it was the fault > > of the usb device. I use keepassx and kpcli with pleasure. > > > > -- > > qubenix > > GPG: B536812904D455B491DCDCDD04BE1E61A3C2E500 > > > > -- > > You received this message because you are subscribed to the Google Groups > "qubes-users" group. > > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > > To post to this group, send email to [email protected]. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/qubes-users/92461c9e-a320-196b-8f8b-d57670264ca0%40riseup.net. > > For more options, visit https://groups.google.com/d/optout.
I've never had a database keepassx become corrupt. I use fedora for my vaultvm. And sorry if this sounds absurd, but very frequently the database file will become unselected, this happens to everyone in my family all the time and you sometimes will repeatedly try the password, to have it fail, not realizing you actually have to re-select the database file again. This happens if you don't shut down keepassx properly. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/a6daf5e6-c156-4303-b2b0-fcaa171d4344%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
