From: Sergey Matveev Date: Wed, 24 Jul 2024 08:56:57 +0000 (+0300) Subject: I do not use Xombrero for a long time X-Git-Url: http://www.git.stargrave.org/?a=commitdiff_plain;h=f2ea83c60d9c05583b43a4cd70a57ce490673de1;p=tofuproxy.git I do not use Xombrero for a long time --- diff --git a/doc/why.texi b/doc/why.texi index 7e8aa24..1022e90 100644 --- a/doc/why.texi +++ b/doc/why.texi @@ -10,10 +10,7 @@ OpenSSL... All of them sucks, comparing to Go's @code{crypto/tls}. @item I am tired that everyone provides very limited certificates trust management capabilities, like either certificate or SPKI @url{https://en.wikipedia.org/wiki/Certificate_pinning, pinning} with -@url{https://en.wikipedia.org/wiki/Trust_on_first_use, TOFU}. Even my -beloved @url{https://en.wikipedia.org/wiki/Xombrero, Xombrero} browser -still pins only the whole certificate, but its public key would be much -more sufficient and convenient to work with. +@url{https://en.wikipedia.org/wiki/Trust_on_first_use, TOFU}. @item I am tired that many clients provides very few information about certificates and connections at all. @@ -27,8 +24,6 @@ kind of @url{https://en.wikipedia.org/wiki/Privoxy, Privoxy}, but it is not friendly with TLS connections, obviously. Or use yet another browser-specific plugin. -@item Xombrero sometimes has problems with HTTP-based authorization. - @item Hardly anyone does @url{https://en.wikipedia.org/wiki/DNS-based_Authentication_of_Named_Entities, DANE} checks.