Summary: | security/ca_root_nss patch to make it ASCII | ||||||
---|---|---|---|---|---|---|---|
Product: | Ports & Packages | Reporter: | Goran Mekić <meka> | ||||
Component: | Individual Port(s) | Assignee: | Ports Security Team <ports-secteam> | ||||
Status: | Closed FIXED | ||||||
Severity: | Affects Only Me | CC: | joneum, w.schwarzenfeld | ||||
Priority: | --- | Flags: | bugzilla:
maintainer-feedback?
(ports-secteam) |
||||
Version: | Latest | ||||||
Hardware: | Any | ||||||
OS: | Any | ||||||
Attachments: |
|
what is the current status? Does ports-secteam have to be active here? If I rewrite patch to only change that one ofending character and not link any files, I think that would be perfect. Or we might upstream it? ping! |
Created attachment 195307 [details] ca_root_nss-3.38.diff A single character in ca-root-nss.crt makes it non-ascii: # file work/ca-root-nss.crt work/ca-root-nss.crt: ISO-8859 text With this patch, the given file is ASCII again, and it adds a new symlink which some programs (I tested net-im/gajim) require. I am not sure this is the proper way to handle this situation, so please advise if I need to send different patch.