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
{{ message }}
This repository has been archived by the owner on Aug 2, 2021. It is now read-only.
A sender should be able to specify the amount and even the content of padding to append in each message through the API.
Right now the padding in current fallback crypto implementation is fixed, although we kept methods prepared to specify amount of padding to append.
This could be specified inside WrapParams, that currently only allows the API caller to select the encryption keys.
typeWrapParamsstruct {
Sender*ecdsa.PrivateKey// Private key of sender used for signatureReceiver*ecdsa.PublicKey// Public key of receiver for encryptionSymmetricKey []byte// Symmetric key for encryption
}
If a custom content for a padding is specify, there will be appended as is, if not, the message should be filled up with random content up to a specified multiple of a paddedSize param.
A sender should be able to specify the amount and even the content of padding to append in each message through the API.
Right now the padding in current fallback crypto implementation is fixed, although we kept methods prepared to specify amount of padding to append.
This could be specified inside WrapParams, that currently only allows the API caller to select the encryption keys.
If a custom content for a padding is specify, there will be appended as is, if not, the message should be filled up with random content up to a specified multiple of a
paddedSize
param.Related with PR #1703
The text was updated successfully, but these errors were encountered: