From a60565478f4e1b369bd6c9b51a04e3d157978741 Mon Sep 17 00:00:00 2001
From: Dante Catalfamo
Date: Mon, 18 Oct 2021 17:18:18 -0400
Subject: bsd-auth: Add security tagm remove why section, add missing monotext

---
 content/posts/WIP-how-bsd-authentication-works/index.org | 15 +++------------
 1 file changed, 3 insertions(+), 12 deletions(-)

diff --git a/content/posts/WIP-how-bsd-authentication-works/index.org b/content/posts/WIP-how-bsd-authentication-works/index.org
index c33a1c2..de3b6ac 100644
--- a/content/posts/WIP-how-bsd-authentication-works/index.org
+++ b/content/posts/WIP-how-bsd-authentication-works/index.org
@@ -3,8 +3,8 @@
 #+DRAFT: true
 #+SHOWTOC: true
 #+DESCRIPTION:
-#+TAGS[]: openbsd
-#+KEYWORDS[]: openbsd
+#+TAGS[]: openbsd security
+#+KEYWORDS[]: openbsd security
 #+SLUG:
 #+SUMMARY:
 
@@ -44,15 +44,6 @@
   permissions using [[https://man.openbsd.org/pledge][=pledge(2)=]] or [[https://man.openbsd.org/unveil][=unveil(2)=]]. The BSD Authentication
   system of configured through [[https://man.openbsd.org/login.conf][=login.conf(5)=]].
 
-* Why
-  :PROPERTIES:
-  :CUSTOM_ID: why
-  :END:
-
-  There isn't much on the internet about how to use BSD
-  Authentication. I was curious about how the internals worked, and I
-  figured someone else might be too :^)
-
 * Documentation
   :PROPERTIES:
   :CUSTOM_ID: documentation
@@ -2183,7 +2174,7 @@
   is returned.
 
   Then the path to the [[#modules][auth module]] is created similarly to how it is
-  created in [[#auth_verify][auth_verify]].
+  created in [[#auth_verify][=auth_verify=]].
 
   The challenge and class of the session are extracted and stored in
   variables =challenge= and =class= respectively.
-- 
cgit v1.2.3