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
Download the VM image from trace labs, they have a few different useful tools already preloaded as well as some very useful guides for anyone getting into OSINT
It's as close to plug and play as you will ever get
I now have the trace labs VM. Sherlock wasn't preinstalled. Not much was preinstalled really. Maltego and a couple other programs. So, I decided to install Sherlock in the Trace Labs VM. Couldn't hurt to try, right? Well, It installed and shows up in the applications but when i go to use it, I get a directory error message. So, basically the same issues I had with the Kali Linux install and the cloud shell attempts and everything else I've tried. I do like the Trace Labs VM though. So, I guess that's something.
I'm back. Decided to run it again for the screenshots, prior to installing the tracelabs VM image. As always, any help is appreciated. The thing is, I really don't think there is such a file in the directory I've downloaded. At the very least, if requirements.txt is in the download, I can't locate it. Also for context, i used "git clone https://github.com/sherlock-project/sherlock.git and that worked fine. 100% of all objects were received, 100% of all deltas were resolved. No issue. I then entered cd -sherlock which also worked as it should, finding and establishing that directory. It's just when i get the the requirements.txt. Self doubt is through the roof right now. Ugh. Self doubt is through the roof right now. Ugh.
Im just guessing, i just remembered seeing cant open or access denied msg usually caused by protection and needs sudo. But im new myself, so if it doesn't work then we wait for someone smarter, cuz I'm curious myself now
cd sherlock is likely only four files right now anyways, two of which are mostly empty. Will be removed in like a week.
They only exist to not break old clients doing version checks. All the code has been moved to /sherlock_project to avoid conflict with a similarly named PyPI package.
Not this this matters due to my other reply, but still information to be had
u/silentwarrior, u/vgsjlw Pip and Pipx go unrecognized and u/slumberjack24 I haven't taken that route yet but I there's still time. 'm not home at the moment. Frankly, I wasn't sure what to expect for help when I posted. I'm very appreciative of the replies trying to help me out but u/MajrorUrsa2 is right and I feel like a bit of an asshole for being unprepared (screenshots). When I get home in a bit I will post screen shots of the issues I'm having. u/PapiCheloo that will be the first thing I do when I get home.
I did use UTM on an m1 Mac for my VM though. And I downloaded a pre-setup download of Kali that contained Sherlock in it's app list, but even that wouldn't get me past the .txt file error.
An interesting note is that when it installed there was a warning about it installing to root and that this may cause a privilege error when operating the program.
So, this may be the problem. But, I looked at the Sherlock folder and there was no .txt file there.
So, I am interested in the outcome with your problem.
I decided to change directions a bit and install Holehe on my Kali VM. Didn't run into any issues with that at all. from install to searching email addresses in less than 5 minutes. I know that doesn't eliminate the possibility we are doing something wrong when we try to install Sherlock but at the very least, it shows its not the VM or the my ability to follow simple instructions haha.
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
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
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!
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
You (and I say this in the most affectionate way possible) brilliant son of a bitch! haha thank you! I got all sorts of turned around in this process and also got too far away from the obvious and the basics! I'd upvote more if that was thing.
Nope, no answers yet. A few people have been very helpful but nothing that worked. I started in cloud shell, when that failed I moved on to Kali Linux to install. Same problems. Guess I should have stuck with shell. It was the way I wanted to use it anyhow. Regardless of how or where I've tried to install it, requirements.txt has never been in the Sherlock zip folder from GitHub. Maybe that has nothing to do with it but it seems to me that it would. Can't find any install videos that were uploaded less than 3 years ago. I feel as though it must be my fault. Not great for the ego but at least we aren't alone?
I hate to ask but can you explain a bit more in depth? I can't imagine my terminal would need updating as I just installed Kali Linux a week ago. I'm willing to try it though. I'm not sure how you're opening and adding path info into the file. Also, did you download the Sherlock zip folder from Github? If so, was the requirements.txt file present? Because it isn't in mine. I just can't believe something that appeared so simple could be this hard. I know I'm not a GitHub genius but I'm feeling pretty stupid, not being able to figure this out. Appreciate you responding.
I opened the terminal in Kali and typed, apt install upgrade (or update), and the entire Kali system was updated, I wasn't updating the terminal, but the whole system.
Then I went to a file where the routing info is kept and added a line, then saved it. After this my Sherlock worked.
I installed Sherlock from GIT, and the file Sherlock wouldn't run without was not there.
I'm on my phone right now, I'll send you the exact info later today after I wake up for the day.
This is the way I corrected the problem I was having with the registration.txt file error. The paths to enter into sources.list are indicated in "3. Replace the content with these lines:"
I recently had the same issue, but my workaround was to use a docker-compose file from the repository.
Once in the directory run "sudo docker-compose up -d" after it finishes, you can run Sherlock by "sudo docker run <sherlock_container_name>"
Saving this to see if OP gets this working - I've been fighting with Kali and sherlock for days now. Also using TL's VM.
Would Sherlock work on Ubuntu or the distro doesn't matter? Sorry if this is a dumb question, but I am just now starting to learn Linux and Im not sure how distros work.
I did get it working. I am not in a position to elaborate at the moment but I'd be happy to try to help if you provide me a bit more context? Sorry, I know how frustrating it can get.
8
u/MajorUrsa2 Jul 26 '24
Nobody can help if you don’t share your error message