Allow exporting key material and init of cipherstate #50
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In order to allow implementations to store the nonce and key (e.g. for use with distributed systems), I've added an
UnsafeKey
method that exports the current key for storage. Combined with theCipherSuite
, already exportable nonce, and this key, these can be used to reconstruct aCipherState
from stored data using the newUnsafeNewCipherState
method.Noting that
UnsafeKey
isn't strictly necessary if it is already accessible from theCipher
, but I think this is preferable overall to needing to possibly create wrappedCipher
types which allow the key to be later exportable.The
Unsafe
keyword is mean to indicate that these functions should be avoided at a glance, unless the caller accepts responsibility for manually managing exported state outside of application memory.