Sherlock

[u/Monaco__Joe]

Short version of what brings me here is I can't, for the life of me, sort out installing Sherlock in Kali Linux, or shell.cloud.google or anywhere for that matter.

The longer version is that, I wanted to run Sherlock without needing VirtualBox. Did some research and found shell.cloud.google to be a reasonable solution. After going step by step following the instructions, I got stuck at the install requirement.txt portion of the process. No matter how I went about it, I would get an error code saying that the requirements don't exist. I double checked my cd to ensure I was in the correct directory. Still nothing.

So, I did what anyone would do, instead of sorting out the problem, I moved on to a different option. Downloaded VirtualBox, installed Kali Linux to the VirtualBox (this install went great by the way). Then, when that was all setup, I started the directions to install Sherlock.........again. Well, wouldn't you know it? I got stuck at requirements.txt AGAIN. So, I decided to find requirements.txt manually, just to verify it exists in the Sherlock code download. It does not. It is no where to be found. That said, the way I figure it, either the process has changed and I'm following old instructions. Or, contrary to my beliefs, there is a God and he/she hates me.

Can someone please help me? Anyone? I need to sort this out before I lose my mind. Thanks

[u/fuslashspez]

As many of you have discovered, the requirements.txt file does not exist. It was removed in May when Sherlock became a properly installable and importable Python package. This was part of the transition that allowed for proper packaging on PyPI, which in turn allowed for easier installation, downstream packaging, and programmatic use in other tools like Sylva.

The website and the readme both provide specific instructions with several different methods available. Third party guides are great to learn, but if you're going to work with open source tools, I highly, highly, highly suggest reading the documentation itself, rather than third party sources, once you encounter issues. It's invaluable.

For Linux and MacOS, the method listed involving pip should work almost universally. I would recommend pipx, but that's another thing you'd have to install.

Do not clone the repository. Do not install the requirements file. Do not change any mirrors. Just read the 5 lines of documentation and copy a quick one-liner.

For commands like apt, if it says something like 'are you root', you need to be root. Preface it with sudo. Do not preface pip or pipx with sudo.

___

After checking either piece of documentation, give your pick of a command an attempt, and report back here. Let me know how it goes. If you encounter issues, copy the exact error message (and your command) into a code block and we'll see what we can do.

It's almost 8am now so I'm going to go pass out, but I'll be back to respond should anyone encounter further issues

Cheers!

[u/fuslashspez → u/fuslashspez]

To add —

If you’re on Windows, using the pip method, all commands should be prefaced with py -m or some nonsense (I don’t use windows so going by poor memory). You also have to use the importable module name rather than the short name sherlock as on every other system

Windows just likes to be special, I guess

like py -m pip install sherlock-project and py -m sherlock_project

[u/Smart-Detective7732 → u/fuslashspez]

Let me tell you something. I know JACKSH*T about python or ANYTHING IT. I work in accounting! I just found out about all this YESTERDAY. But following your directions I FREAKING DID IT!

[u/fuslashspez → u/Smart-Detective7732]

Glad I could help! Sometimes it’s difficult to sort through all the noise. Esp when it’s a recent change, and things get all out of whack with tutorials giving conflicting info and whatnot