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

Add honeytrap service banners #53

Open
glaslos opened this issue Mar 13, 2017 · 7 comments
Open

Add honeytrap service banners #53

glaslos opened this issue Mar 13, 2017 · 7 comments

Comments

@glaslos
Copy link
Member

glaslos commented Mar 13, 2017

Honeytrap has a couple of service banners we could use to get to the next stages for connections requiring a banner.
Can be found here: https://github.com/armedpot/honeytrap/tree/master/etc/responses

@glaslos glaslos changed the title Add honeytrap responses Add honeytrap service banners Mar 22, 2023
@milinddethe15
Copy link

Hi, I am new to this project and want to contribute in it.

To solve this issue:

  • Instead of sending random data, banner has to be sent, specific to the target port.

Please correct me if I have understood it wrong.
Thanks!

@glaslos
Copy link
Member Author

glaslos commented Jan 16, 2025

Correct, for certain ports. See the linked responses in the issue.

@milinddethe15
Copy link

working on this!!

@milinddethe15
Copy link

@glaslos should the reponses be saved and read it from /config folder when running glutton or like, glutton should read the responses while compiling?

@glaslos
Copy link
Member Author

glaslos commented Jan 27, 2025

It should be incorporated either into the TCP handler or as separate handlers.

@milinddethe15
Copy link

Should I use go:embed to import responses files?
This will make sure glutton binary don't need external /responses folder while running.

@glaslos
Copy link
Member Author

glaslos commented Jan 28, 2025

Keep the responses in byte slices.

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

No branches or pull requests

2 participants