You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add the possibility to upgrade from a format v1 to a format v2 in mlar.
This could be part of the convert command line or a dedicated upgrade_v1_to_v2 sub-action.
In the current draft of the format v2, the upgrade consists of:
A possibility is to only update the first bytes of the layer, without re-encrypting the whole archive. But this solution:
does not renew the key, which might not be expected
could be problematic if some PQC key for recipients are missing
The preferred method for now would be like convert, ie. re-encrypting the whole archive with new keys materials.
Implementation
MLA 2 will mainly consist of:
mla 2.0.0: hybrid cryptography detailed in CRYPTO.md for the moment
mlar 2.0.0: supports MLA 2 only
no MLA 1 support except backporting fixes regarding MLA extraction or repair
Upgrade mechanism will consist in specific versions of mlar:
mlar-legacy: mlar version that will support extraction (and repair) for MLA 1 and MLA 2 in addition with everything mlar 2 has : best option for current pipelines using MLA
mlar-upgrade: mlar archive upgrader from MLA 1 to MLA 2 : option if you decide to only support MLA 2 in your pipelines
The text was updated successfully, but these errors were encountered:
Thoughts
Add the possibility to upgrade from a format v1 to a format v2 in
mlar
.This could be part of the
convert
command line or a dedicatedupgrade_v1_to_v2
sub-action.In the current draft of the format v2, the upgrade consists of:
encrypt
are left unchangedencrypt
layer, the AES-GCM key commitment ([AES-GCM] Add Key Commitment #206) is added and a public PQC key ([Format v2] Consider adding Post-Quantum cryptography with hybrid KEM for the encryption layer #195) is also provided.A possibility is to only update the first bytes of the layer, without re-encrypting the whole archive. But this solution:
The preferred method for now would be like
convert
, ie. re-encrypting the whole archive with new keys materials.Implementation
MLA 2 will mainly consist of:
mla
2.0.0: hybrid cryptography detailed inCRYPTO.md
for the momentmlar
2.0.0: supports MLA 2 onlyUpgrade mechanism will consist in specific versions of
mlar
:mlar-legacy
: mlar version that will support extraction (and repair) for MLA 1 and MLA 2 in addition with everythingmlar
2 has : best option for current pipelines using MLAmlar-upgrade
: mlar archive upgrader from MLA 1 to MLA 2 : option if you decide to only support MLA 2 in your pipelinesThe text was updated successfully, but these errors were encountered: