[no description] https://git.osdyson.ru/mirror/pkgsrc/atom?h=pkgsrc-2021Q2 2021-01-11T22:50:37Z 2021-01-11T22:50:37Z wiz wiz@pkgsrc.org 2021-01-11T22:50:37Z urn:sha1:2dc727b5cfa987e1c754f02f97d7d90bd0bb9960 2020-11-29T18:36:15Z wiz wiz@pkgsrc.org 2020-11-29T18:36:15Z urn:sha1:eead57befa548465aebc27b3a3fb1d245b3657d2 Sync with mozilla-rootcerts. 2020-06-12T10:35:11Z maya maya@pkgsrc.org 2020-06-12T10:35:11Z urn:sha1:f3a18c95be1eb8587c2c116651ab8114fb150938 Mozilla only trusts this for Turkish domains, see: https://wiki.mozilla.org/CA/Additional_Trust_Changes And users of mozilla-rootcerts likely don't implement the same fine-grained trust. Proposed on tech-pkg 2020-05-30T12:56:54Z tnn tnn@pkgsrc.org 2020-05-30T12:56:54Z urn:sha1:34cd4b217abc3e441feafa41712841c35c5d4cc4 2020-03-27T17:00:01Z gdt gdt@pkgsrc.org 2020-03-27T17:00:01Z urn:sha1:c9099ed8d99b9520054c793b48e6a1cef8da349a Mention the manual script approach, almost parenthetically, in the See also part about mozilla-rootcerts. 2020-03-27T13:42:53Z gdt gdt@pkgsrc.org 2020-03-27T13:42:53Z urn:sha1:8795a2a7bf95547de7daa0aec1ee2bbeb1d7742e Explain the purpose, and then explain the mechanism and why it is somewhat and very irregular in the pkgsrc and native cases. Point to mozilla-rootcerts as providing certificates without configuring them as trust anchors. 2020-03-12T13:43:35Z gdt gdt@pkgsrc.org 2020-03-12T13:43:35Z urn:sha1:740dbc80451c1d5ed26b867ddf942518610f6825 This was marked NOT_FOR_UNPRIVILEGED, but that is only appropriate when the package (abusively, as a pre-existing well-discussed compromise) writes outside of the pkgsrc prefix. Patch by Jason Bacon, with general approval on tech-pkg. ok dholland@ 2019-12-07T18:29:31Z sevan sevan@pkgsrc.org 2019-12-07T18:29:31Z urn:sha1:65a2b265e60bc3902deec7f264acf63330d088cb 2019-05-20T09:51:24Z adam adam@pkgsrc.org 2019-05-20T09:51:24Z urn:sha1:c63820575bef3d5784daec6cee4d6bd484ecafa4 2019-05-12T19:20:43Z maya maya@pkgsrc.org 2019-05-12T19:20:43Z urn:sha1:6d00d503871205413b369457256cba10ff28e11d