Would've been nice to know that four years ago, too. The same thread includes more information on the same kind of problem I was having from it I can surmise that if I'd created an empty CRL and had my root CA cert point to it, I probably would've been able to get it working. That's.hardly ideal, but it would probably have solved my problem, if it existed four years ago when I last tried to get this working. On the other hand, there's a forum thread from late last year in which the fb2k developer appears to have addressed the issue at least in part, by making it possible to whitelist hosts and thus bypass certificate validity checking.
It didn't change anything about fb2k's behavior, though, which led me to surmise that fb2k was doing something wonky in its TLS implementation.
#Clementine music player mac no song or artist info windows
That was enough to stop applications using the Windows TLS stack, such as Internet Explorer, from complaining any longer about being unable to verify the certificate. That's why, in the process of investigating the issue, I added the root CA cert I'd created, and used to sign the server cert, to the Windows certificate store. Well, yes, I'm not completely ignorant of how TLS works, so that was of course my first thought on discovering fb2k lacked any interface by which I could tell it to trust my server cert.
0 kommentar(er)
