On 30 Jan 2022, knuttle <
keith_...@sbcglobal.net> wrote in
news.software.readers:
Here are descriptions of those lines according the the stunnel
documentation. I don't really understand their implication, but I guess
it has to do with verifying that the e-s host is trusted. I've been
operating just fine without them for several years, but I'm using your
settings now and they work well, too. It maybe even connects faster,
but that might be my imagination.
==============
verifyChain = yes | no
verify the peer certificate chain starting from the root CA
For server certificate verification it is essential to also require
a specific certificate with checkHost or checkIP.
The self-signed root CA certificate needs to be stored either in
the file specified with CAfile, or in the directory specified with
CApath.
default: no
-----------
CAfile = CA_FILE
Certificate Authority file
This file contains multiple CA certificates, to be used with the
verifyChain and verifyPeer options.
-----------
checkHost = HOST
host of the peer certificate subject
Multiple checkHost options are allowed in a single service section.
Certificates are accepted if no subject checks were specified, or the
host name of the peer certificate matches any of the hosts specified
with checkHost.
This option requires OpenSSL 1.0.2 or later.
-----------
OCSPaia = yes | no
validate certificates with their AIA OCSP responders
This option enables stunnel to validate certificates with the list
of OCSP responder URLs retrieved from their AIA (Authority Information
Access) extension.