webui.mod aux Issue

[michaelortmann]

This issue is for referencing everything webui related

Fixed by #1866: michaelortmann#1

Done: should we report any IANA "meaning strings" for status codes when we receive a websocket close? the map is here: https://datatracker.ietf.org/doc/html/rfc6455 page 65. i added the meaning for 1001 and consider this to be enough for our use case.

Rejected: feature request http auth, then cert auth, initial code: develop...michaelortmann:eggdrop:webui.http.auth
http auth would render michaelortmann#1 obsolete
update 20251219 http auth was discussed in irc, evaluated and tried. current state is we leave it as is and dont plan http auth.

Rejected: someone requested moving the webui settings in eggdrop.conf under telnet settings. but the current config file has each mods config after core config, so current state is we leave it as is.

Open: Evaluate / implement CertFP login for webui, see thommeys comment below.

[thommey]

20:00.57 < thommey> you have to import the client certificate into the browser, yeah
20:01.18 < thommey> openssl req -x509 -newkey rsa:4096 -sha256 -days 365 -nodes -subj "/CN=example.com/O=MyOrg/C=US" -keyout key.pem -out cert.pem && openssl pkcs12 -export -inkey key.pem -in cert.pem -name "my-cert" -out mycert.p12
20:01.29 < thommey> firefox -> settings -> certificates -> view certificates -> my certificates -> import
20:02.03 < thommey> the server has to ask for one then and you can pick which one you want to try to authenticate with (if you have multiple)
20:04.16 < thommey> for the server
20:04.23 < thommey> openssl req -x509 -newkey rsa:4096 -sha256 -days 365 -nodes -subj "/CN=example.com/O=MyOrg/C=US" -keyout key.pem -out cert.pem
20:04.25 < thommey> openssl s_server -cert cert.pem -key key.pem -www -accept 4433 -verify 1
20:04.45 < thommey> then browse with firefox to https://x.x.x.x:4433 and you get the prompt which client cert to use, and openssl s_server shows it
20:04.57 < thommey> also shows debug info in the browser
20:05.01 < thommey> -verify 1 requests the client cert
20:05.28 < thommey> eggdrop can already do client cert auth but seems like that would be more involved than what you're doing if you just feed user/password into a simulated telnet session
20:05.50 < thommey> you'd need to open one and bypass the authentication and check it yourself
20:06.00 < thommey> (with the existing routines for ssl-dcc)