W3C home > Mailing lists > Public > public-credentials@w3.org > February 2021

Re: File formats for the secure export/import of Verified Credentials?

From: Christopher Allen <ChristopherA@lifewithalacrity.com>
Date: Sun, 31 Jan 2021 18:34:28 -0800
Message-ID: <CACrqygAU9=mpLOMXRZV=jekDNXgF9oDEPxqrgnguYUDVeqkFyA@mail.gmail.com>
To: "Michael Herman (Trusted Digital Web)" <mwherman@parallelspace.net>
Cc: Leonard Rosenthol <lrosenth@adobe.com>, Credentials Community Group <public-credentials@w3.org>
We have on the Blockchain Commons roadmap to add encrypted CBOR objects to
our UR/QR research and reference implementation work. As you can tag JSON
text as CBOR, you can technically put anything in it, though it is more
efficient if you use native CBOR.

Our requirements are that we can support not only important
symmetric encryption schemes, but that we can also support decryption
through a shamir sharded symmetric key, or include asymmetric key CBOR
objects, bundled with the encrypted data that allow it to be decrypted. We
also want it to be totally self-describing and support efficient nested
embedding of encrypted objects inside encrypted objects. Our inspiration is
the MiniLock file format
<https://45678.github.io/miniLock-file-format/2.html> but with CBOR.

However, with current patronage income flow, this probably will not be done
until later in the year — our UR focus right now is more focused on
airgapped key management and signing (mostly Bitcoin keys & partially
signed transactions right now but adding 25519 soon.) We already support
multi-QR and animated QRs for larger transfers. We already have
implementations supporting these in C, Java, Rust, and Python with more
coming. If patronage funding commitments accelerate, we may do our
encrypted CBOR sooner.

Overview UR article:
Initial UR Research Paper:

/bcc @wolfmcnally @shannona @VinayTaylor
Received on Monday, 1 February 2021 02:35:17 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:25:09 UTC