Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Re-add host to "Login attempt for nonexistent user" log #316

Merged
merged 1 commit into from
Oct 21, 2024

Conversation

MichaIng
Copy link
Contributor

#83 removed the host from the final message part of early exit messages, and added it to the initial message part instead. This was however done for "Login attempt for nonexistent user" as well, which is no early exit message, but allows the client to keep trying. Those log entries hence now do not contain a host anymore.

This PR reverts this part of #83 to restore the missing host, and re-enable software like Fail2Ban to track these login failures.


As mentioned in #83, I guess "Login attempt with wrong user" (when Dropbear runs as non-root user) is no early exit message as well, and hence needs to be reverted the same way. Probably someone can verify this quicker than me.

mkj#83 removed the host from the final message part of early exit messages, and added it to the initial message part instead. This was however done for "Login attempt for nonexistent user" as well, which is no early exit message, but allows the client to keep trying. Those log entries hence now do not contain a host anymore.

This PR reverts this part of mkj#83 to restore the missing host, and re-enable software like Fail2Ban to track these login failures.

Signed-off-by: MichaIng <[email protected]>
@mkj
Copy link
Owner

mkj commented Oct 21, 2024

Thanks, sorry for the delay with this

@MichaIng MichaIng deleted the fix-nonexisting-user-log branch October 26, 2024 23:18
@MichaIng
Copy link
Contributor Author

@mkj thanks for merging.

For completeness, the same should be done for "Login attempt with wrong user" as well, right?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants