Skip to content

Conversation

@darkk
Copy link
Contributor

@darkk darkk commented Nov 17, 2025

That improves UX in #9411 cases: warning is better than silence.

That improves UX in opnsense#9411 cases: warning is better than silence.
// Two+ session_id() cookies confuse _SESSION management. They should go before we continue.
// It's hard to reset them from the server-side as we don't know the right scope with confidence.
if (($c = session_id_cookies_count()) >= 2) {
auth_log(sprintf("%d %s cookies from %s, no way to proceeed", $c, session_name(), $_SERVER['REMOTE_ADDR']), LOG_NOTICE);
Copy link
Contributor Author

@darkk darkk Nov 17, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One one hand, it opens a way to flood logs of the OPNsense box with curl. So, maybe, these log lines should be added to /usr/local/opnsense/scripts/syslog/lockout_handler.

On another hand, lockout_handler does nothing about log lines like sshd-session 79000 - [meta sequenceId="135327"] Connection closed by 10.91.66.130 port 34902, so it seems to be focused on nothing but authentication attempts. There is already a way to flood audit log with TCP connection attempts to OpenSSH daemon anyway. 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant