As part of this process, there are some new onboarding screens for Kismet:
Kismet will now show a local-only text alert (not sent to the browser or other message bus clients) showing the new password which has been generated.
Kismet will also show an alert that a new password has been generated, and warning existing users of the git-master code that the old config option is no longer used.
The first time you visit Kismet with your browser (or the first time for a particular browser - the setting is stored in HTML5 local storage so it is specific per browser), you'll get a welcome screen asking to take you to the settings panel.
The settings panel now describes the need to change the login.
Subsequent visits to the Kismet page will warn you if the password is invalid, and offer to take you to the settings panel. If you're a guest on a server, or don't want to log in for some reason, these alerts can be silenced with the "Don't warn again" option.
Finally, the new settings handler can confirm the validity of the login and warn if it is not valid.
While these add a few extra steps, the added security of not having default logins potentially exposed to the Internet definitely outweighs it.
Installation-time passwords can still be set by using the httpd_username= and httpd_password= options in /usr/local/etc/kismet_httpd.conf, or in the per-user ~/.kismet/kismet_httpd.conf, and the random generated password can be changed by editing ~/.kismet/kismet_httpd.conf as well.
A huge thanks to all who support Kismet on Patreon - if you'd like to help, you can become a patron here!