-
In the [nitro-enclave-python-demo](https://github.com/richardfan1126/nitro-enclave-python-demo)/[attestation_verifier](https://github.com/richardfan1126/nitro-enclave-python-demo/tree/master/attestati…
-
### Background and motivation
In order to comply with the executive order on supply chain security, that includes inventory management (SCIM) and bill of materials (SBOM), .NET needs to implement A…
-
During interop-testing we have run into a few possible interop-problems.
Section 4.2 of [RFC8152](https://tools.ietf.org/html/rfc8152#section-4.2) states the following:
> The structure can be e…
-
OCSP stapling data is mentioned in:
Section 4.2 (QueryRequest Message), which talks about including it, e.g., "The TAM provides OCSP data so that the TEEP Agent can validate the status of the TAM c…
-
I've been trying to switch to 1.0 but for some reason signature validation is failing. I'm using the OpenSSL adapter. I can't see anything obvious I'm doing wrong, but I'm sure it is something simple.…
-
## Problem statement
NCC Group found a (known) footgun in our API:
> The library does not prevent a user from manually populating the signature field or modifying the protected header after call…
-
# Draft for adding each type of suit manifests into "4.4 Update Message"
[4.4 Update Message](https://datatracker.ietf.org/doc/html/draft-ietf-teep-protocol#section-4.4)
The Update Message has a S…
-
First issue spotted by the fuzz tests!
`Sign1Message.UnmarshalCBOR` does not check that the message strictly follows the `COSE_Sign1` definition. It does check for the presence of `COSE_Sign1_Tagge…
-
Currently JWS Compact Serialization (https://datatracker.ietf.org/doc/html/rfc7515#section-7.1) is elaborated in this draft.
Do we also need support for JWS JSON Serialization (esp. General JWS JSO…
-
Found via fuzzing.
`Sign1Message.UnmarshalCBOR` does not check that the payload and the signature strictly follow the `COSE_Sign1` definition.
### What did you do?
```go
package main
impo…