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

[FR]: Gopher (port 70) #3238

Closed
drbeco opened this issue Mar 17, 2022 · 3 comments · May be fixed by #3240
Closed

[FR]: Gopher (port 70) #3238

drbeco opened this issue Mar 17, 2022 · 3 comments · May be fixed by #3240

Comments

@drbeco
Copy link

drbeco commented Mar 17, 2022

This is not a filter "request" per se.

I've created a new filter for gopher (gophernicus, port 70), and I would like to submit it to the project, if that is ok.

This filter will prevent attempts to send a SIGINT by checking syslog gophernicus error File not found and banning the IP.

Environment:

  • Fail2Ban version : Fail2Ban v0.11.2
  • OS, including release name/version : Slackware 15.0 x86_64

Service, project or product which log or journal should be monitored

  • Name of filter or jail in Fail2Ban (if already exists) : /etc/fail2ban/filter.d/gopher.conf
  • Service, project or product name, including release name/version : gopher / gophernicus server
  • Repository : none. A single file. I can create it as repository, but it is overkill
  • Service type : filter
  • Ports and protocols the service is listening : 70 / tcp

Please let me know how to proceed to provide the filter to this project. Thanks

@sebres
Copy link
Contributor

sebres commented Mar 17, 2022

You can create a new pull request (you'd need some branch firstly in your clone, which can be also created automatically if you'd add new filter).
The details and minimum requirements (like mandatory log-file with test-cases and change log entry) are described in PR template.

You could also provide it here together with log-file excerpt containing matched log-entries and a sample jail (port, logpath, etc).

@drbeco
Copy link
Author

drbeco commented Mar 18, 2022

I'm gonna try a PR. Please let me know if I did it right, or if you need anything to be changed.

@sebres
Copy link
Contributor

sebres commented Mar 18, 2022

thus closing it now, further in #3240

@sebres sebres closed this as completed Mar 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants