|
Revision tags: constraints-v0.1.0, interceptor-v0.8.2, rtcp-v0.7.2, mdns-v0.5.2, v0.6.0, interceptor-v0.8.1, media-v0.5.0, data-v0.6.0, sctp-v0.7.0, srtp-v0.9.1, rtcp-v0.7.1, rtp-v0.6.8, dtls-v0.7.0, ice-v0.9.0, turn-v0.6.1, stun-v0.4.4, mdns-v0.5.1, sdp-v0.5.3, util-v0.7.0 |
|
| #
c0579c37 |
| 04-Nov-2022 |
Anton Kaliaev <[email protected]> |
[peer_connection] RTCCertificate: rework `from_pem` and `serialize_pem` (#333)
which makes it possible to serialise and persist a certificate to disk. Both methods require `pem` feature to be enable
[peer_connection] RTCCertificate: rework `from_pem` and `serialize_pem` (#333)
which makes it possible to serialise and persist a certificate to disk. Both methods require `pem` feature to be enabled (I think having a feature is good since I don't expect many people to use persistent certificate). Previous implementation of `from_pem` was incorrect. It used a given certificate as a CA (hence the 2nd argument) instead of just using the certificate directly (see the related TODO in tests where `cert1 == cert3` should be matching).
API reflects one in Pion - https://github.com/pion/webrtc/blob/master/certificate.go#L179 (see `CertificateFromPEM` and `PEM` functions).
Also
- modify `RTCCertificate::get_fingerprints` to return `Vec<Fingerprint>`. No need for `Result`.
- refactor `dtls::crypto::Certificate`
- fixes TODO where two certificates should be equal when `from_pem` is being used.
show more ...
|
|
Revision tags: ice-v0.8.2, v0.5.1, ice-v0.8.1, v0.5.0, data-v0.5.0, dtls-v0.6.0, ice-v0.8.0, interceptor-v0.8.0, mdns-v0.5.0, media-v0.4.7, rtcp-v0.7.0, rtp-v0.6.7, sctp-v0.6.1, sdp-v0.5.2, srtp-v0.9.0, stun-v0.4.3, turn-v0.6.0, util-v0.6.0, test-tag |
|
| #
e04c4c13 |
| 24-Aug-2022 |
David Braden <[email protected]> |
[DTLS] Add NamedCurve::P384 (#254)
|
| #
ffe74184 |
| 23-Aug-2022 |
Martin Algesten <[email protected]> |
Move all to top level
|