[FEATURE] Add heroku and ngrok support

[Roo7K1d]

I want to add support for 2 SaaS providers:

• Heroku
• ngrok

HELP WANTED!

If you do want to help and contribute please open a pull request once you have adjusted the code :)

[anoduck]

Hmmm... Heroku I haven't used in years, and ngrok has changed a whole butt load since I last touched it. But, after performing a few minutes of research, both seem relatively easy to set up.

For Ngrok, you will need to dockerize your app, which is no biggie. Then you will need to run your new dockerized app along with Ngrok's own dockerized instance, and with some tinkering it should be running.

https://hub.docker.com/r/ngrok/ngrok

For Heroku, you will need to add some files to your repo, and then setup heroku to pull changes from the repo to the heroku dyno instance.

I will look into it some more later on.

[anoduck]

@Roo7K1d It isn't really important, but remove bs4 from the requirements file. It is a dummy package created by the developer of beautifulsoup4 to prevent anyone from name squatting. The bs4 package either redirects to beautifulsoup4 or is empty and provides no actual code that is used.

You can read it in the page description here: https://pypi.org/project/bs4/

[anoduck]

Don't know why, but I found myself working on it last night. I have not tested it yet, but ngrok integration is pretty much complete, along with dockerizing everything as well. I even took liberty to upgrading all the dependencies to the latest versions, along with correcting a few needed tidbits to allow it to run in python3.11.2. It didn't take long to do either, a few hours, that is all.

The kicker is for some reason or another GitHub is not allowing me to push my changes to my fork from my development server. So, I might have to push them to a different repository hosting service until that can get fixed, and mirror the repo on github.

[anoduck]

@Roo7K1d Weirdness ... I got an error trying to push my changes from my development server, but when I copied everything to my desktop and pushed from there, it went through like butter. ...go figure? 🤷🏻

Regardless, the work completed last night is now in my forked repo. I will not create a PR until it has been tested, and I know it will work.

You might want to take a look at requirements.txt, or try it out on your box to ensure everything still runs as smooth as silk.

[anoduck]

D0x-K1t now runs on docker and Ngrok tunnels to an external address.

[Roo7K1d]

Great work!
It would be awesome if you could also create a DOCKERFILE for standalone hosting of this project within a container (which is not ngrok).

If you do not have the time to adjust the README according to all your improvements i will do that for you.

Feel free to open a PR once you got everything working and tested!

[anoduck]

It took me all of 16mins to reconfigure to allow the standalone operation, without testing. If you could please test run Docker-compose, build the image, and put it through it's paces. Being the developer, you know how this puppy should run. Tweaks can be made here and there to allow better performance.

[Roo7K1d]

I have now tested everything and it works just fine! Thanks for your help!

[anoduck]

@Roo7K1d Ran into a little snag with heroku that I was not aware of. As you probably know, they were purchased by salesforce recently, and as of a result now require a payment method for use. I don't mind doing adding my info, but it would probably be better for longevity to put it in your name.

I don't know if you have crossed this bridge with heroku yet or not, but they now require multifactor authentication for account creation.

[anoduck]

@Roo7K1d We might think about moving this thread to discussions, but I had an idea. I wouldn't consider it a brilliant idea, because it is not necessarily original, but it would be a first if implemented.

When I am performing recon on a target, I always find there are a lot of false positives. That is, there are phone numbers, addresses, associates, or emails assigned to the target that do not necessarily belong to the target. The only way I know of weeding out these false positives, is by relying on multiple sources of information to confirm each other. Which is something no OSINT recon tool does at this moment. Just food for thought.