diff options
| author | Fabian Dellwing <fabian.dellwing@gmail.com> | 2023-04-10 07:06:51 +0200 |
|---|---|---|
| committer | Ali Mohammad Pur <Ali.mpfard@gmail.com> | 2023-04-12 11:40:06 +0330 |
| commit | e78db6417ab5df80b10d155b146fae43e047e905 (patch) | |
| tree | b6692b987d8b415b47abc967511a6b71ee978432 | |
| parent | 93232d4e6d51a2f954ddafff7cae950655e32b74 (diff) | |
| download | serenity-e78db6417ab5df80b10d155b146fae43e047e905.zip | |
LibTLS: Remove outdated comment about ECC
PR #18166 introduced the ability to parse ECC certificates. If we
now fail here the reason is mostlikely something new and we should
prevent this rabbit hole from happening.
| -rw-r--r-- | Userland/Libraries/LibTLS/TLSv12.cpp | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/Userland/Libraries/LibTLS/TLSv12.cpp b/Userland/Libraries/LibTLS/TLSv12.cpp index b1df727bae..ff01c9acfd 100644 --- a/Userland/Libraries/LibTLS/TLSv12.cpp +++ b/Userland/Libraries/LibTLS/TLSv12.cpp @@ -521,8 +521,6 @@ ErrorOr<Vector<Certificate>> DefaultRootCACertificates::parse_pem_root_certifica for (auto& cert : certs) { auto certificate_result = Certificate::parse_certificate(cert.bytes()); - // If the certificate does not parse it is likely using elliptic curve keys/signatures, which are not - // supported right now. It might make sense to cleanup cacert.pem before adding it to the system. if (certificate_result.is_error()) { // FIXME: It would be nice to have more informations about the certificate we failed to parse. // Like: Issuer, Algorithm, CN, etc |