naltun / eyes Goto Github PK

@sahitpj, I found this StackOverflow thread.

🤔

Hey @naltun since we are developing a package wouldn't it be good to use CI?

I ran into a problem the other day, when the 'HTTP Header Grab' feature didn't follow the redirect.

Off the top of my head I can't remember which function did this, but under net/http is a function that will follow redirects up to 10x.

This first got me thinking... And then I received a 'Exhausted API use`, etc. notice today.

The use of APIs is well-done because it allows a user to add an extra layer of security; but even then, I am not aware of HackerTarget's privacy policy. This could be considered a security vulnerability.

Even when pentesting, etc. we should always keep security and privacy of ourselves + our property (machines, etc.) at the forefront of concerns. If we are using HackerTarget's API insecurely, then we're still in trouble.

So considering that most people who would ever touch this program would be considering personal safety, maybe it's just better to implement each feature natively.

I am looking for feedback.

Hey @naltun since, this project is going on well, I was thinking we should move these projects into an organization. That way, I think we can put it forward as a product and would be useful to the community

hey @naltun as proposed, I think we can work on adding the mage file, or have you figured out any other alternatives, so that using them doesn't have to be restricted to us.

Yes, logo.

A logo would be cool. If a gopher can be leveraged, too, that'd be great. I don't know how to make SVG images (I'd imagine that's the format that it'd be in), so any help on this would be appreciated.

Hey @naltun I think in the README, we can mention users how to run our pkg, by using go build and then running the executable

Will be useful for first timers, what do you say ?

Here, we should be returning the error as a string (via err.Error()). linkgrab.GetLinks() may need additional tidying.

I think eyes has the potential to really become a well-rounded, quality pentesting tool.

To realize this goal, I am looking for contributors to the project; anywhere from 1-2, for now.

If you'd like to help out, please respond to this issue. I am looking to keep development of eyes completely in the open.

Thanks.

So we can keep the README 'developed on' badges true, for anyone contributing to the project, please let me know which OS you are developing with. :)

Linux || *BSD || MacOS || (yes, even...) Windows, whatever you're working on, feel free to let me know.

Hey @naltun, since we were redesigning this module, I was wondering how the structure would be:

• like a main src within which we keep all our submodules
• or submodules just placed outside.