Changes between Initial Version and Version 1 of Ticket #21451, comment 12

Ticket #21451, comment 12

-              initial
+              v1
+yep, that's the point of Yoda's link @ OP,
+pebkac.  sort of.
+https://www.scrye.com/wordpress/nirik/2023/01/31/error-rpmdbnextiterator-skipping-in-fedora-38/
+{{{
+our server side TLS policy here is
+tho ...
+        https://wiki.mozilla.org/Security/Server_Side_TLS#Modern_compatibility
+it's not clear to me why curl fails @ vb site, but OK @ oracle
+and wget's good at both.
+that includes
+        Cipher suites (TLS 1.3): TLS_AES_128_GCM_SHA256:TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256
+        Cipher suites (TLS 1.2): (none)
+clients, for a fair while now, match.  we typically don't allow non-TLS 1.3 anymore.
+checking, virtualbox.org's ssl report
+        https://www.ssllabs.com/ssltest/analyze.html?d=virtualbox.org
+shows no tls 1.3 support; only 1.2.  and of those, only 1 strong,
+        TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
+adding that suite to
+        CipherSuites
+in
+        /etc/ssl/openssl.conf
+does the trick.
+curl & dnf curl with the new repo gpgkey url work fine, now.
+wget wasn't sentitive to openssl config, as
+        ldd `which wget` |grep -Ei "ssl|tls"
+        libgnutls.so.30 => /lib64/libgnutls.so.30 (0x00007efd79200000)
+        ldd `which curl` |grep -Ei "ssl|tls"
+        libssl.so.3 => /lib64/libssl.so.3 (0x00007fad4132c000)
+it would be helpful virtualbox.org server to get bumped to include tls1.3 support.
+}}}