From 366ace3e5849d0d259915ddff22c8ec55e40b3ad Mon Sep 17 00:00:00 2001
From: Thomas Habets <thomas@habets.se>
Date: Fri, 5 May 2023 10:30:24 +0100
Subject: [PATCH] Add `TOTP codes are not accepted` bug template

---
 .../totp-codes-are-not-accepted.md            | 27 +++++++++++++++++++
 1 file changed, 27 insertions(+)
 create mode 100644 .github/ISSUE_TEMPLATE/totp-codes-are-not-accepted.md

diff --git a/.github/ISSUE_TEMPLATE/totp-codes-are-not-accepted.md b/.github/ISSUE_TEMPLATE/totp-codes-are-not-accepted.md
new file mode 100644
index 0000000..8513a33
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/totp-codes-are-not-accepted.md
@@ -0,0 +1,27 @@
+---
+name: TOTP codes are not accepted
+about: OTP codes are configured, but don't seem to be accepted, or only sometimes
+  accepted
+title: 'TOTP not accepted: '
+labels: ''
+assignees: ''
+
+---
+
+## Prerequisite
+
+Read [this](https://twitter.com/thomashabets/status/1133780752582217728), have a little chuckle to yourself.
+
+After that: no seriously really do confirm it. Most of the reported issues with TOTP follow that pattern.
+
+## PAM config
+
+E.g. `/etc/pam.d/ssh`, or `common-auth` if it uses that.
+
+## SSH config (or equivalent if not using SSH)
+
+`/etc/ssh/sshd_config`
+
+## Enable `debug` on the module, and paste what's logged
+
+Maybe from `/var/log/auth.log`.