From 6ffc460dbdad730aa14c20fae1950016cb63f854 Mon Sep 17 00:00:00 2001 From: Bryan Ashby Date: Fri, 20 Nov 2020 18:51:43 -0700 Subject: [PATCH] Fix --- docs/configuration/menu-hjson.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/configuration/menu-hjson.md b/docs/configuration/menu-hjson.md index b23c0ef4..db4e740b 100644 --- a/docs/configuration/menu-hjson.md +++ b/docs/configuration/menu-hjson.md @@ -258,7 +258,7 @@ someMenu: { } ``` -### Case Study: Adding a New User Password (NUP) +## Case Study: Adding a New User Password (NUP) You've got a super 31337 board and want to prevent lamerz! Let's run through adding a NUP to your application flow. Given the default menu system, two "pre" new user application menus exist due to the way Telnet vs SSH logins occur. We'll focus only on Telnet here. This menu is `newUserApplicationPre`. Let's say you want to display this preamble, but then ask for the NUP. If the user gets the password wrong, show them a `LAMER.ANS` and boot 'em.