Summary: | net-im/libpurple: Pidgin exclusively uses net-im/libpurple's bundled TLS certs | ||
---|---|---|---|
Product: | Ports & Packages | Reporter: | Andras Farkas <deepbluemistake> |
Component: | Individual Port(s) | Assignee: | Joe Marcus Clarke <marcus> |
Status: | Closed FIXED | ||
Severity: | Affects Some People | Flags: | bugzilla:
maintainer-feedback?
(marcus) |
Priority: | --- | ||
Version: | Latest | ||
Hardware: | Any | ||
OS: | Any |
Description
Andras Farkas
2021-11-20 20:39:26 UTC
I'll note that libpurple's bundled certificates are up to date in the latest version (though that package isn't available on quarterly yet) Even so, it might be preferable to have the packages using FreeBSD's certs. How do other ports handle this? Ping. I found this bug ca be solved by the following: mv /usr/local/share/purple/ca-certs /somewhere/else I think the correct solution would be to not bundle libpurple's certs. A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=c80dda3bf578ae5c0e9e02beec4a1be2609f0d44 commit c80dda3bf578ae5c0e9e02beec4a1be2609f0d44 Author: Joe Marcus Clarke <marcus@FreeBSD.org> AuthorDate: 2021-12-26 16:04:38 +0000 Commit: Joe Marcus Clarke <marcus@FreeBSD.org> CommitDate: 2021-12-26 16:04:38 +0000 net-im/libpurple: Point to the system TLS certs. PR: 259954 net-im/libpurple/Makefile | 4 +++- net-im/libpurple/pkg-plist | 3 --- 2 files changed, 3 insertions(+), 4 deletions(-) Fixed in 2.14.8_1. It should now point to the system TLS certs. This is foxed now. |