From fb7f329460d8116e80b52034ebe9cef21fc80673c27bcc374b667241f5095e41 Mon Sep 17 00:00:00 2001 From: Nicholas Johnson Date: Sat, 21 Jan 2023 00:00:00 +0000 Subject: Upgrade journal theme --- content/entry/oxen-security-fail.md | 1 + 1 file changed, 1 insertion(+) (limited to 'content/entry/oxen-security-fail.md') diff --git a/content/entry/oxen-security-fail.md b/content/entry/oxen-security-fail.md index 5ca19fa..60146c4 100644 --- a/content/entry/oxen-security-fail.md +++ b/content/entry/oxen-security-fail.md @@ -2,6 +2,7 @@ title: "Oxen Security Fail" date: 2021-09-28T00:00:00 draft: false +makerefs: false --- Lately I've been doing research on the Oxen Privacy Tech Foundation and their various projects. On 19 September while looking at Session, I noticed getsession.org was missing the Strict-Transport-Security header[1]. So I decided to also check the security headers for oxen.io[2], lokinet.org[3], and optf.ngo[4] and what do you know, they're also missing HTTP security headers. -- cgit v1.2.3