From e78db6417ab5df80b10d155b146fae43e047e905 Mon Sep 17 00:00:00 2001 From: Fabian Dellwing Date: Mon, 10 Apr 2023 07:06:51 +0200 Subject: 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. --- Userland/Libraries/LibTLS/TLSv12.cpp | 2 -- 1 file changed, 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> 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 -- cgit v1.2.3