-
----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------
> * Section 4. Per “the DTLS connections SH…
-
Following the tutorial in the README I noticed a couple of things:
First, in the examples it uses the file "dstcax3.pem" but there is written nothing on how get it.
```console
$ ./rfc7030-est-cli…
-
We are considering to use the server in production along with local CA implementation. We are aware that when we start the server we have the notification not to use it in Production mode. Is it possi…
-
DEVL_VM (@192.168.1.172/24) ~/pest/prebuild/pest-0.0.3/test $> ./test run 2.2
./test:DBG: Action 'run'
./test:OUT[test/2.2]: Running test 'Void whitelist, no enrollments' repeating it from a previou…
-
RFC8994 section 6.2.5.1 needs to be Extended to include an objective that describes where the EST server can be found that will take care of certificate renewals for devices which are already onboar…
-
> According to [BRSKI], Section 2.7, the pledge MUST use an Implicit
> Trust Anchor database (see EST [RFC7030]) to authenticate the Cloud
> Registrar service. The pledge MUST establish a …
upros updated
2 months ago
-
```
The Registar MUST also confirm the resulting CSR is formatted as
indicated before forwarding the request to a CA. _If the Registar is
communicating with the CA using a protocol like fu…
-
FedCM API currently uses the `.well-known/fedcm` folder in order to find the endpoint configuration. The `.well-known` folder is [specified](https://www.rfc-editor.org/rfc/rfc8615.html#:~:text=Well-kn…
-
264 BRSKI section 5.9.2 specifies that the pledge MUST send an EST
265 [RFC7030] CSR Attributes request to the registrar. The registrar MAY
which registrar - cloud or owner ?
upros updated
10 months ago
-
262 2.3. Pledge Certificate Identity Considerations
264 BRSKI section 5.9.2 specifies that the pledge MUST send an EST
265 [RFC7030] CSR Attributes request to the registrar. The registrar …
mcr updated
10 months ago