Tspi_DecodeBER_TssBlob(3) TCG Software Stack Developer's Reference Tspi_DecodeBER_TssBlob(3)NAME
Tspi_DecodeBER_TssBlob - unwraps a BER-encoded TSS blob.
SYNOPSIS
#include <tss/tspi.h>
TSS_RESULT Tspi_DecodeBER_TssBlob(UINT32 berBlobSize, BYTE* berBlob,
UINT32* blobType, UINT32* rawBlobSize,
BYTE* rawBlob);
DESCRIPTION
Tspi_DecodeBER_TssBlob is used to unwrap a BER-encoded blob in accordance with the ASN.1 data definitions in the Portable Data section of
the Trusted Computing Group Software Stack Specification Version 1.2.
PARAMETERS
berBlobSize
Size of the BER-encoded blob.
berBlob
Pointer to the BER-encoded blob.
blobType
Pointer to the type of blob being unwrapped (refer to the TSS_BLOB_TYPE_* constants).
rawBlobSize
Pointer to the size of the rawBlob buffer. On input this parameter contains a pointer to the maximum size of the supplied rawBlob buffer.
On output this parameter contains a pointer to the actual size of the unwrapped blob. On input, if this parameter points to a value of 0,
then this function will return the size of the buffer required to hold the unwrapped blob without writing to the rawBlob buffer.
Note: The output data must be shorter than the BER-encoding, so berBlobSize is a useful upper limit on rawBlob buffer size.
rawBlob
Pointer to a buffer to hold the unwrapped blob.
RETURN CODES
Tspi_EncodeDER_TssBlob returns TSS_SUCCESS on success, otherwise one of the following values are returned:
TSS_E_BAD_PARAMETER
TSS_E_INTERNAL_ERROR - An error occurred internal to the TSS.
CONFORMING TO
Tspi_DecodeBER_TssBlob conforms to the Trusted Computing Group Software Specification Version 1.2
SEE ALSO Tspi_DecodeBER_TssBlob(3).
TSS 1.2 2007-06-12 Tspi_DecodeBER_TssBlob(3)
Check Out this Related Man Page
Tspi_DecodeBER_TssBlob(3) TCG Software Stack Developer's Reference Tspi_DecodeBER_TssBlob(3)NAME
Tspi_DecodeBER_TssBlob - unwraps a BER-encoded TSS blob.
SYNOPSIS
#include <tss/tspi.h>
TSS_RESULT Tspi_DecodeBER_TssBlob(UINT32 berBlobSize, BYTE* berBlob,
UINT32* blobType, UINT32* rawBlobSize,
BYTE* rawBlob);
DESCRIPTION
Tspi_DecodeBER_TssBlob is used to unwrap a BER-encoded blob in accordance with the ASN.1 data definitions in the Portable Data section of
the Trusted Computing Group Software Stack Specification Version 1.2.
PARAMETERS
berBlobSize
Size of the BER-encoded blob.
berBlob
Pointer to the BER-encoded blob.
blobType
Pointer to the type of blob being unwrapped (refer to the TSS_BLOB_TYPE_* constants).
rawBlobSize
Pointer to the size of the rawBlob buffer. On input this parameter contains a pointer to the maximum size of the supplied rawBlob buffer.
On output this parameter contains a pointer to the actual size of the unwrapped blob. On input, if this parameter points to a value of 0,
then this function will return the size of the buffer required to hold the unwrapped blob without writing to the rawBlob buffer.
Note: The output data must be shorter than the BER-encoding, so berBlobSize is a useful upper limit on rawBlob buffer size.
rawBlob
Pointer to a buffer to hold the unwrapped blob.
RETURN CODES
Tspi_EncodeDER_TssBlob returns TSS_SUCCESS on success, otherwise one of the following values are returned:
TSS_E_BAD_PARAMETER
TSS_E_INTERNAL_ERROR - An error occurred internal to the TSS.
CONFORMING TO
Tspi_DecodeBER_TssBlob conforms to the Trusted Computing Group Software Specification Version 1.2
SEE ALSO Tspi_DecodeBER_TssBlob(3).
TSS 1.2 2007-06-12 Tspi_DecodeBER_TssBlob(3)
About a year ago, a friend of mine who worked on the OReilly Snort book took a propsal he and I had worked on for a book on Trusted Computing. Though the editor thought the content was good and worthwhile, he felt that there wasn't enough of a market to justify printing such a work.
How many... (0 Replies)
Tim Bass
Thu, 15 Nov 2007 23:55:07 +0000
*I predict we may experience less*debates*on the use of the term “event cloud”*related to*CEP in the future, now that both IBM and Google* have made announcements about “cloud computing” and “computing cloud”, IBM Turning Data Centers Into ‘Computing... (0 Replies)
I wanted to do an "Alternate Disk Migration" via my NIM server to update several clients (all LPARs in a p670) from 5.1 ML6 to 5.2 ML3. As a prerequisite the procedure says "if the system has the Trusted Computing Base enabled it has to be switched off before".
Well, i didn't give this too much... (3 Replies)