DiME
  • Introduction
  • Format overview
  • Claims
  • Item verification
  • Time syncronization
  • Implementations
  • Licence
  • Version history
  • Items
    • Envelopes
    • Key
    • Identity
    • Identity Issuing Request
    • Data
    • Message
    • Tag
  • Encoding
    • General encoding
    • Key encoding
    • Signature encoding
  • Cryptography
    • Thumbprints
    • Item links
    • Suites
Powered by GitBook
On this page

Was this helpful?

  1. Encoding

Key encoding

DiME, the open and trust-based data format building secure Application-based Public-Key Infrastructures (APKIs) in a breeze.

PreviousGeneral encodingNextSignature encoding

Last updated 2 years ago

Was this helpful?

This section relates on how raw key data is encoded. The encoding of DiME key items is outlined in the previous chapter . As with the overall DiME item, Base64 is also used to encode raw key material. 

"key": "DSC.7VN2b6f0nxqubSU955PuMenLtV6u9ltQr0ovUG0CL0Rfhb9S9IvUapNj58CHcsVwMYr3bOw/aghjECVcua2M+Q"
"pub": "DSC.X4W/UvSL1GqTY+fAh3LFcDGK92zsP2oIYxAlXLmtjPk"

The ‘key’ claim contains the secret key whereas the ‘pub’ claim contains the public key. The cryptographic suite used to generate the key is indicated by the initial header (‘DSC’). For more information about suites, see the chapter , which details out the use of cryptographic suites.

General encoding
Suites