Asterios Raptis

Importing a KDBX database and exporting it again does not return what went in: entry identity is regenerated, timestamps are replaced, history is dropped. KDBX is the interchange format for local password storage, so a tool that cannot round-trip it is a one-way door. Deliverables: identity and timestamps preserved in both directions, history preserved or refused with what would be lost named, and a round-trip test against a real KDBX file. Lands in mystic-crypt-ui, where KDBX handling lives.

Key material is handled as opaque bytes: format, algorithm, fingerprint and certificate expiry are known to whoever wrote the file, not to the software holding it. Deliverables in the library itself: a key description model that reads those properties off the key instead of taking them on trust, the existing conversion, fingerprint and checksum operations bound to it, and an expiry query. The desktop application is the first consumer, so every project depending on mystic-crypt gains the result.