Date: Sat, 20 Nov 2021 20:39:26 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 259954] net-im/pidgin: Pidgin exclusively uses net-im/libpurple's bundled TLS certs Message-ID: <bug-259954-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D259954 Bug ID: 259954 Summary: net-im/pidgin: Pidgin exclusively uses net-im/libpurple's bundled TLS certs Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: marcus@FreeBSD.org Reporter: deepbluemistake@gmail.com Assignee: marcus@FreeBSD.org Flags: maintainer-feedback?(marcus@FreeBSD.org) While LetsEncrypt has had recent changes, I've noticed the following: Pidgin exclusively uses net-im/libpurple's bundled TLS certs, and doesn't u= se FreeBSD's own store of TLS certs. This means even if FreeBSD utilities can connect to services using recent LetsEncrypt certificates, Pidgin refuses to connect. (for example, the jabber.at XMPP server) I feel it would be nice if libpurple or Pidgin could be configured to use t= he OS's TLS certificates. I think this is probably a ports/package issue, but if I should report this upstream instead, let me know. package versions: libpurple-2.14.4 pidgin-2.14.4 $ uname -a FreeBSD nyann.tanasinn.mochi 13.0-RELEASE-p4 FreeBSD 13.0-RELEASE-p4 #0: Tue Aug 24 07:33:27 UTC 2021=20=20=20=20 root@amd64-builder.daemonology.net:/usr/obj/usr/src/amd64.amd64/sys/GENERIC= =20 amd64 $ freebsd-version -kru 13.0-RELEASE-p4 13.0-RELEASE-p4 13.0-RELEASE-p5 --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-259954-7788>