Bitlbee, Purple-Sipe-Lync, and Certificates
- Postfix, iPhone, Apple Mail and the reject
- Updating the SSL certs on the Unifi Controller
- Firefox and org-protocol URL Capture
- System Hangs on Shutdown
- Let's Encrypt Certificates and Arch
- /bin/mail as MTA
- Filtering bots with erc
- DSCP Tagging with iptables
- Bitlbee, Purple-Sipe-Lync, and Certificates
- daemontools, Apache, and the Whole Process Group
- Comma Trouble
- Emacs DNS Mode
- Wrangling Namespaces in Python
- Using Skype from Emacs
- Choosing the Right Technology
- Django, Testing, and Sessions
- KMS, xvideo-intel, and Arch Linux
- Verizon UMW-190 and Arch Linux
- Hawking Range Extender and Linux
- CUPS driver for the Dell 1320C Printer on Arch
- SANE and the Canon LIDE 20
- Getting easypg working in Ubuntu
Bitlbee, Purple-Sipe-Lync, and Certificates
Published 2013-10-02
I use bitlbee for IRC, Jabber, Google Talk, and for work, M$ lync, the latter under protest. After building bitlbee to use libpurple, I could connect to the company's lync silliness, but I always got the certificate warnings (the company has its own root CA). Even accepting the cert didn't help – I got the warnings each time I connected.
Simple fix was to copy the company's root CA into /etc/ssl/certs (under Arch Linux - is that the standard path now?).
FYI: looks like libpurple puts the accepted cert in ~/.purple/certificates/x509/tls_peers, but I found a stale version in /var/lib/bitlbee/purple/certificates/x509/tls_peers/.
In the past I had to use the export NSS_SSL_CBC_RANDOM_IV=0 hack to get lync to work, but no more.
org-mode