On 02/03/2019 11:23, Christoph Biedl wrote: > Thanks for looking into this and the insights given. For luksmeta > however ... it's "to access metadata in a LUKSv1 header", and before the > buster release I better shall refrain from checking how the related > tools like clevis deal with LUKSv2 headers B-)
Clevis/Tang already supports direct metadata store to LUKS2 token objects (so the luksmeta package is obsolete for LUKS2 format). IIRC they use cryptsetup token command in the wrapper. Milan
