mirrors/arti.git/doc/dev/SecurityResponse.md, branch main mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=main 2026-05-07T12:08:01Z hsservice, llcrypto, SecurityResponse: use cfg({true,false}) 2026-05-07T12:08:01Z Nick Mathewson nickm@torproject.org 2026-05-04T13:45:55Z urn:sha1:0c4ed480afc9a96b37db9630c7ee3185a69fa999 SecurityResponse: Clarity suggestions from @diziet. 2026-03-26T18:10:13Z Nick Mathewson nickm@torproject.org 2026-03-26T18:10:13Z urn:sha1:cf3b2d9bea692e692016f2935aba6fce913d591f Notably, make it clear that we actually need to analyze issues! Try to document our policy for upstream RUSTSEC issues 2026-03-23T16:45:39Z Nick Mathewson nickm@torproject.org 2026-03-23T16:45:39Z urn:sha1:ba37d2bc77b3c11326d695c7ca3f6926da1e8df4 SecurityResponse: Add a note about failing verification builds 2025-10-01T15:51:53Z Ian Jackson ijackson@chiark.greenend.org.uk 2025-09-29T13:02:22Z urn:sha1:18685c2d6c8746760a9b6eae1e60547f9e63d863 As per https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/3233#note_3253024 Start a security response policy, capturing workflow from !3151 2025-10-01T15:51:53Z Ian Jackson ijackson@chiark.greenend.org.uk 2025-09-04T16:06:30Z urn:sha1:bc4b0e8acbd9f41ca1f836ae64ec41c97d475e0f