August Johann

@shred : Thanks for adding this feature to acme4j :+1:. Unfortunately I wasn't able to use it as is. There are some obstacles to overcome. Perhaps you can shed some...

Indeed, the headers are needed. Please find the secured header fields inside the ` smime.p7s`: ``` 4650:d=6 hl=3 l= 161 cons: SEQUENCE 4653:d=7 hl=2 l= 11 prim: OBJECT :1.2.840.113549.1.9.16.2.55 4666:d=7...

Please see "Securing Header Fields with S/MIME" ([RFC 7508](https://www.rfc-editor.org/rfc/rfc7508.html)) for more information.

These are fantastic news! I'm burning to test the latest version of acme4j. When do you plan to release a new version with these changes?

Sure, keep in mind that the used S/MIME certificate has a limited lifetime. ⌛

@shred LGTM, I've run some tests with good cases and [acme4j accepted all server sent messages](https://gitlab.com/platynum/certification-authority/flows/-/blob/development/test/acme4j/src/test/java/SmimeTest.java) so far! Thank you very much.

No, this is not possible.

Thanks for merging https://github.com/laverdet/isolated-vm/pull/429. When do you plan to release it?

Works fine with 4.7.2

@Daniel-Nashed For small environments, you could run your own ACME CA ([server-side](https://gitlab.com/platynum/certification-authority/flows/-/tree/development) and [client-side](https://gitlab.com/platynum/certification-authority/flows/-/tree/development/examples/acme-client) ([older binaries](https://gitlab.com/platynum/certification-authority/flows/-/releases))). [Run the software using node.js](https://platynum.gitlab.io/certification-authority/documentation/documentation/main/installation/npm.html). There is a docker container (https://hub.docker.com/r/platynum/certification-authority) providing this service,...