Mercurial > libervia-backend
view docker/backend-dev-e2e/certificates/README @ 4351:6a0a081485b8
plugin autocrypt: Autocrypt protocol implementation:
Implementation of autocrypt: `autocrypt` header is checked, and if present and no public
key is known for the peer, the key is imported.
`autocrypt` header is also added to outgoing message (only if an email gateway is
detected).
For the moment, the JID is use as identifier, but the real email used by gateway should be
used in the future.
rel 456
| author | Goffi <goffi@goffi.org> |
|---|---|
| date | Fri, 28 Feb 2025 09:23:35 +0100 |
| parents | 73e04040d577 |
| children |
line wrap: on
line source
Those certificates are used to activate TLS for end-2-end testing (to be as close as possible as production environment), they are used in other containers needing TLS certificates (notably Prosody). To generate them, minica has been used. Minica can be found at https://github.com/jsha/minica. The following commands have been used: $ minica --domains "server1.test,*.server1.test,server2.test,server3.test,libervia-backend.test,libervia-web.test" $ chmod 0644 minica.pem server1.test/cert.pem && chmod 0640 server1.test/key.pem Note that certificates are valid for 2 years and 30 days, so they must be renewed after this delay.