On 05/07/2015 11:49 AM, Andrew Cagney wrote:
[inline]
On 5 May 2015 at 13:18, Robert Relyea rrel...@redhat.com wrote:
The target Mechanism is the operation you are going to use the target key
for, It shouldn't match the mechanism used to derive the key. It is
basically used to set the
[inline]
On 5 May 2015 at 13:18, Robert Relyea rrel...@redhat.com wrote:
The target Mechanism is the operation you are going to use the target key
for, It shouldn't match the mechanism used to derive the key. It is
basically used to set the appropriate key type and flags on the resultant
key.
/html/rfc7296#page-48
The code works - at least in the sense that it computes the same values as
the test vectors found on http://csrc.nist.gov/groups/STM/cavp/index.html
The thing I'm not sure about is how the code is using PK11_Derive target
parameter for its intermediate(2) operations
://tools.ietf.org/html/rfc7296#page-48
The code works - at least in the sense that it computes the same values as
the test vectors found on http://csrc.nist.gov/groups/STM/cavp/index.html
The thing I'm not sure about is how the code is using PK11_Derive target
parameter for its intermediate(2) operations
target
parameter for its intermediate(2) operations.
For instance, when doing concatenation and xoring, the derive parameter
might have sane with values like:
CKM_CONCATENATE_DATA_AND_BASE
CKM_CONCATENATE_BASE_AND_DATA
CKM_CONCATENATE_BASE_AND_KEY
CKM_XOR_BASE_AND_DATA
while
5 matches
Mail list logo
