Open GoogleCodeExporter opened 9 years ago
This is a problem across both java and python that I ran across on the weekend
and applies to all functions (promote, demote, etc) once you add an encrypted
key. Indeed once an encrypted key is added any pre-existing unencrypted keys
are not usable. I have fixes for python but unfortunately the way the mocks are
embedded in the code make it difficult to write tests for so I was reworking
that before raising an issue. Unfortunately I've been too busy to finish it off
so far this week, hopefully will wrap it up on the weekend.
See
http://code.google.com/r/rleftwich-lightkeeper/source/detail?r=39fea025cd98e473a
e6d9fb04ecf60af92a1072c&name=fix_python_revoke_bug for a somewhat related bug
where after a revoke the internal state of the Keyczar object is out of sync
with the metadata and if you access the revoked key thru the same instance it
is still present and worse will be rewritten to disk as unrevoked. A similar
issue also appears to be present in java.
Original comment by rleftw...@lightkeeper.com
on 4 May 2012 at 9:11
Original comment by jtu...@gmail.com
on 2 Mar 2013 at 9:30
I've attached a patch for the Java side of this issue; I'm not good at Python,
so someone else will have to implement that fix.
Unfortunately, there aren't any test cases for this fix, as the KeyczarToolTest
class isn't really conducive testing with encrypted keys, and I don't feel
comfortable refactoring your test enough to make it happen.
Also, I could only update the English internationalizion, as I don't know the
other languages.
Original comment by yo.yo.yo...@gmail.com
on 7 Oct 2014 at 9:17
Attachments:
Original issue reported on code.google.com by
mbarry%b...@gtempaccount.com
on 4 May 2012 at 8:57