Fair enough, thanks. This causes issues in companies using certificates
signed by their internal (private) root.
There are ways to work around the issue, of course, but it adds more
hoops to jump through.
On 2018-01-10 14:48, Eion Robb wrote:
I made an attempt at loading certs from the Windows store, however its
not possible to do this in libpurple without also using the win32
SSL/TLS system - certificates and SSL/TLS transports are tied together.
Unfortunately a lot of protocols had issues when going via Window's
stunnel SSL libraries instead of via NSS, and this would cause
connections to hang.
On 11 January 2018 at 10:20, <pid...@alexoren.com
<mailto:pid...@alexoren.com>> wrote:
On 2018-01-10 1:16 PM, Dave Warren wrote:
Is there any particular reason that pidgin doesn't use the
existing Windows certificate store? This would seem to alleviate
the need to juggle with certificates manually.
Or did I miss part of the plot here?
Probably because Pidgin is not a primarily Windows program and
nobody wrote a plugin to do that
_______________________________________________
Support@pidgin.im <mailto:Support@pidgin.im> mailing list
Want to unsubscribe? Use this link:
https://pidgin.im/cgi-bin/mailman/listinfo/support
<https://pidgin.im/cgi-bin/mailman/listinfo/support>
_______________________________________________
Support@pidgin.im mailing list
Want to unsubscribe? Use this link:
https://pidgin.im/cgi-bin/mailman/listinfo/support
