Hi,
* Lester Hightower [2022-03-18 16:12:45 CET]:
> I do not equate your one, esoteric data access problem with justification
> for removing the package from Debian.
Pasting data into the comment field of an entry is nothing I would
anywhere closely consider esoteric, rather the opposite. A
I do not equate your one, esoteric data access problem with justification
for removing the package from Debian. There is no security problem and no
data was lost. Even if you had not fixed the problem in File::KeePass
yourself, there are many other programs that operate on KeePass files that
could
reopen 1007914
thanks
* Lester Hightower [2022-03-18 12:53:30 CET]:
> Please note that marking this bug as "grave" queued kpcli for autoremoval
> from Debian testing:
I am very well aware how the bug states work. Thing is, why do you
think the data loss isn't severe enough to warrant a release
clone 1006917 -1
reassign -1 libfile-keepass-perl
retitle -1 libfile-keepass-perl: crashes "not well-formed (invalid token)" when
finding escape characters
severity -1 important
thanks
Hey,
Am 18.03.22 um 12:02 schrieb Rhonda D'Vine:
* Arno Töll [2022-03-17 14:07:02 CET]:
Hi Rhonda,
Am 08.0
Rhonda,
Please note that marking this bug as "grave" queued kpcli for autoremoval
from Debian testing:
kpcli 3.1-3.1 is marked for autoremoval from testing on 2022-04-06
> It is affected by these RC bugs:
> 1006917: kpcli: "not well-formed (invalid token)" when opening a file
> https://bugs.de
* Arno Töll [2022-03-17 14:07:02 CET]:
> Hi Rhonda,
>
> Am 08.03.22 um 16:31 schrieb Rhonda D'Vine:
> > Upstream is at 3.6 in the meantime, I'm willing to update it now that I
> > digged a bit further into it. If I don't hear back in the next few days
> > I propose an NMU for it, as thanks for
Hi Rhonda,
Am 08.03.22 um 16:31 schrieb Rhonda D'Vine:
Upstream is at 3.6 in the meantime, I'm willing to update it now that I
digged a bit further into it. If I don't hear back in the next few days
I propose an NMU for it, as thanks for having it around in the first
place. :)
please feel f
Yes indeed, i had to fix it through the module. Sorry that I wasn't clear on
that part. Likely this should be changed to be a bug in the module interface
since the frontend shouldn't have to know too much about what's allowed or not
in the fields, the module should give the frontend error messag
Hi Rhonda,
I am happy that you found and fixed your problem. I suspect, however, that
the code that you changed was not actually kpcli code but, instead,
File::KeePass code -- the module that kpcli uses to read and write keepass
files. https://metacpan.org/pod/File::KeePass
Can you confirm that I
Hi,
$buffer =~ s/\e//g;
.. this was all that was needed to fix my mess. Though, kpcli for
obvious reasons shouldn't be able to write broken data it can't read
again, so I keep seeing this as a severe bug in the code which can lead
to data loss for people who aren't familiar enough with perl o
Hi,
I managed to find the culprit With A Little Help From My Friends[tm]. I
used Data::Dumper before the content got passed to XML::Parser, and it
turned out that there is an Escape character (0x1b, ^[) in a comment
field.
kpcli seems to have accepted this when the comment was pasted and
sto
Package: kpcli
Version: 3.1-3.1
Severity: grave
Tags: upstream
Justification: causes serious data loss
Dear Maintainer,
I store my passwords in a keepass file that I exclusively use through kpcli.
After the last kernel upgrade reboot I was unable to open the file anymore, and
thus can't access my
12 matches
Mail list logo
