On Fri, Jan 14, 2022 at 08:24:51PM -0500, Karen Lewellen wrote: > Hi folks, > In an effort to be part of the solution for my shell service provider, I > have a question. > We are getting ssl certificate not trusted errors, which I understand post > issues at the end of November, can be corrected with new ssl certificate > files. > main issue is in lynx 2.9.dev5 > where there is a place to provide the ssl key file name. > Any good sources for them? Karen, I don't quite understand what you are up to. Some context seems missing: what application is complaining about a non-trusted certificate? What application is providing it? Where did you (or your provider) get this (not trusted) certificate from? You say lynx: that seems to be the client complaining. So I assume (am I right?) the server providing the certificate might be a Web server (Apache?). Does the error happen with another client? (e.g. Firefox). This is relevant because, apparently, some clients actively fetch missing intermediate certificates (FF, for one), some don't, so the latter have to be fed a complete cert chain up to a trusted root. Lastly, you mention "...to provide the ssl key file name". To whom? To the (I'm making that up, see above) server? This is server configuration, so it will depend on what server. If it's Apache (not necessarily the best choice, mind you, but probably the most widespread), here [1] is some documentation to get you started. The whole topic is somewhat involved, and I don't know what you know and what not, so it might take some back-and-forth. Just ask away! Cheers [1] https://httpd.apache.org/docs/2.4/ssl/ssl_howto.html -- t
Attachment:
signature.asc
Description: PGP signature