SSL intercept with Windows certificate: No valid signing SSL certificate configured for HTTP_port



  • You can import a CA certificate generated elsewhere in Certificate Manager and, then, use it as the CA for generating mimetic certificates for ssl_bump in Squid Proxy.

    You can generate that certificate in a Windows computer and copy and paste crt and key. It will be imported. But there would be CR+LF (Windows style line feeds) on that certificate/key that will be imported to the xml config file. When it is chosen in Squid general settings page, it will be exported to serverkey.pem with incorrect line endings that will no be accepted by squid with a FATAL error in system.log:

    squid: No valid signing SSL certificate configured for HTTP_port xxx.xxx.xxx.xxx
    

    This can be solved easily just replacing \r\n with \n when exporting it. I'll do a PR on that. Just would like to know if something like that could also occur with Mac style new lines \r (I am not sure if that format still exists).


Log in to reply