Project

General

Profile

Actions

Bug #16782

open

Trying to cancel ping (option 7) from console menu drops user into password change flow

Added by → luckman212 1 day ago. Updated about 20 hours ago.

Status:
Feedback
Priority:
Normal
Assignee:
Category:
Console Menu
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Release Notes:
Default
Affected Plus Version:
26.03
Affected Architecture:

Description

This is a relatively minor issue, but it is strange/unexpected.

Choosing option '7' (Ping host) from the console menu, and then trying to cancel with ^c instead of providing a hostname to ping sends the user into a forced "Password MUST be changed" flow. Attempting to ^c again will terminate the entire SSH session.

Screenshot attached.


Files

clipboard-202604060909-xjx2c.png (565 KB) clipboard-202604060909-xjx2c.png → luckman212, 04/06/2026 01:09 PM
Actions #1

Updated by Jim Pingle 1 day ago

I can't reproduce this here. Is that on a fresh installation? Can you reproduce it every time you invoke the option? Was the password every actually changed to something other than the default?

That would normally only happen if the current menu was started before the password was changed on the first post-install boot. Once the password has been changed, that shouldn't be displayed.

Actions #2

Updated by → luckman212 1 day ago

No, this isn't a fresh installation.

Yes I can reproduce it every time.

I also just tested on another 2100 running 26.03 (which was very recently clean-installed) and was able to reproduce it there as well.

Yes in both cases, the password has definitely been changed from the default.

FYI- I can reproduce it from the serial console (in addition to via SSH)

Actions #3

Updated by Steve Wheeler about 24 hours ago

  • Status changed from New to Confirmed

To reproduce this you must hit ctl+c twice quite rapidly. So it appears to escape the menu before ctl+c is captured.

Actions #4

Updated by Jim Pingle about 20 hours ago

  • Assignee set to Jim Pingle
  • Target version set to 26.07

Spamming ^C is a bad practice in general, but unfortunately common. The script drawing the menu can capture its own signals, but not signals for child processes. If you press ^C multiple times rapidly it will kill other things running to render the menu and could have other impacts, but in this case it appears to be canceling the password check.

This change appears to catch that case and not fall into the password change for me:

diff --git a/src/etc/rc.initial b/src/etc/rc.initial
index ed2cbab19a..cd88fa4c51 100755
--- a/src/etc/rc.initial
+++ b/src/etc/rc.initial
@@ -68,7 +68,7 @@ case "$(/usr/bin/head -1 /etc/default-config-flavor | /usr/bin/tr -d '[:space:]'
 esac

 # If the password check fails, print an error and prompt to change it.
-if [ ${PWCHECK} -ne 0 ]; then
+if [ ${PWCHECK} -ne 0 ] && [ -n "${PWCHECK_TEXT}" ]; then
        echo "*** *** *** *** *** ***" 
        echo ${PWCHECK_TEXT}
        echo "Password MUST be changed." 
Actions #5

Updated by Jim Pingle about 20 hours ago

  • Status changed from Confirmed to Feedback

Fixed in Plus commit 72e0fb9b7910195ad402e72480728fce8ef0867b

Actions

Also available in: Atom PDF