From 92ceb2f568df5d575f4e60ea5ef24cc668cff440 Mon Sep 17 00:00:00 2001 From: Peter Hofmann Date: Sun, 3 May 2020 18:48:54 +0200 Subject: [PATCH] Manpage: Don't be too specific about TLS backend It's GnuTLS on my system, but I don't know if it's a hard requirement or if it will change some days. Also, there is no real need to specify it. --- man1/lariza.usage.1 | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/man1/lariza.usage.1 b/man1/lariza.usage.1 index 2b78b8e..6e571cb 100644 --- a/man1/lariza.usage.1 +++ b/man1/lariza.usage.1 @@ -1,4 +1,4 @@ -.TH lariza 1 "2020-05-02" "lariza" "User Commands" +.TH lariza 1 "2020-05-03" "lariza" "User Commands" .\" -------------------------------------------------------------------- .SH NAME lariza.usage \- extended usage hints @@ -153,10 +153,10 @@ Those bundled web extensions are automatically compiled when you run make sure to link them to the directory mentioned above. .\" -------------------------------------------------------------------- .SH "TRUSTED CERTIFICATES" -By default, \fBlariza\fP trusts whatever CAs are trusted by WebKit, i.e. -by your GnuTLS installation. If you wish to trust additional -certificates, such as self-signed certificates, the first thing you -should do is try to add the appropriate CAs to your system-wide store. +By default, \fBlariza\fP trusts whatever CAs are trusted by WebKit. If +you wish to trust additional certificates, such as self-signed +certificates, the first thing you should do is try to add the +appropriate CAs to your system-wide store. .P If you wish to add simple exceptions, you can grab the certificate and store it in the directory \fI~/.config/lariza/certs\fP. The filename -- 2.39.2