-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
[Other] #499
Comments
This is something that has to be done manually for what you are doing, this is not something that we can include as it's an issue with uvloop not us
…________________________________
From: eNigma <notifications@github.com>
Sent: Sunday, August 9, 2020 4:42:29 AM
To: laramies/theHarvester <theHarvester@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Subject: [laramies/theHarvester] [Other] (#499)
Feature Request or Bug or Other
Other
Describe the feature request or bug or other
I just installing theHarvester on termux running aarch64, intall the requirements manually, just in case if I get the same error few weeks back. till the part of uvloop, tried with pip install uvloop after that run
python theHarvester.py
getting import error on uvloop, found a workaround in this uvloop<MagicStack/uvloop#260>
To Reproduce
Steps to reproduce the behaviour:
1. install all requirements/base.txt except uvloop
2. pip install uvloop
3. see error :
...
ImportError: dlopen failed: cannot locate symbol "uv__pthread_sigmask"
...
Expected behaviour
expect after install uvloop, theHarvester can run normally. but I have to uninstall it and use the workaround provided to compile uvloop manually using :
pkg install libuv
pip download uvloop
expand the tar.gz archive somewhere and cd into it
python setup.py build_ext --use-system-libuv
python setup.py install
additional step when get permission error on ./configure :
chmod +x vendor/libuv/configure
python setup.py install
after that I can run theHarvester.
Can it be included in step to install theHarvester ? or do we need to do it manually ?
Screenshots
* I was too happy and forgot to take the error screenshot, but this is the result :
[Screenshot_20200809-103608]<https://user-images.githubusercontent.com/68355570/89724355-450b3500-da2c-11ea-8e53-5671cda0c9b8.png>
System Information (System that tool is running on):
* OS: Android 7.1 aarch64, Termux
* Version : Python 3.8.5
Additional context
Just in case, so I'm asking about it. thanks for the awesome tool 👍
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<#499>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AA3V2QUBIPGVALFLRWNPJZTR7YLKLANCNFSM4PY7IKTQ>.
|
ah, you right, it is somethig with the uvloop part that really need a little treatment. anyways, the tool is running and I know how to make it work. |
If you would like perhaps you can create a PR for an edit for the wiki for termux users? |
well, never do something like that, I'll try that later. One question tho, how do you get rid of google blocking your ip ? should I use proxy or something ? I use ssh app to connect to my internet provider using my data plan package that only can be use to browsing internet, etc with this app (ssh/shadowsock v-mesh) similar like vpn with socks5 listening on localhost:1080. wonder which ip google blocked, my real ip or my ssh server ip. alas, I'm still trying "do something" with harvester, my first experience with this tool :D because few months back can't make it work. |
Proxies would be the way to go we may add support for socks proxy eventually it would be pretty trivial to include just been busy. |
Don't worry about this little problem, look like I should take my time, limiting my scan and enjoy a cup of coffee. I just wonder whats wrong with google :D keep the good work dev 👍 |
Google detects that we are basically being a bot and that then gets us blocked, thanks for the kind words and I will have a word and see about adding socks proxy support for everyone
…________________________________
From: eNigma <notifications@github.com>
Sent: Monday, August 10, 2020 12:33:32 AM
To: laramies/theHarvester <theHarvester@noreply.github.com>
Cc: J.Townsend <townsend891@hotmail.com>; Comment <comment@noreply.github.com>
Subject: Re: [laramies/theHarvester] [Other] (#499)
Proxies would be the way to go we may add support for socks proxy eventually it would be pretty trivial to include just been busy.
Don't worry about this little problem, look like I should take my time, limiting my scan and enjoy a cup of coffee. I just wonder whats wrong with google :D
keep the good work dev 👍
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#499 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AA3V2QV2B4NHBP6TXQFXRO3R74W4ZANCNFSM4PY7IKTQ>.
|
aha, just enjoy your time dev, no need to hurry. one does not simply, scanning site like this in an android device :D |
going to close this out as there is #469 to add socks proxy support, so please track that, thanks |
Thank you! |
Feature Request or Bug or Other
Other
Describe the feature request or bug or other
I just installing theHarvester on termux running aarch64, intall the requirements manually, just in case if I get the same error few weeks back. till the part of uvloop, tried with
pip install uvloop
after that runpython theHarvester.py
getting import error on uvloop, found a workaround in this uvloop
To Reproduce
Steps to reproduce the behaviour:
requirements/base.txt
exceptuvloop
pip install uvloop
Expected behaviour
expect after install uvloop, theHarvester can run normally. but I have to uninstall it and use the workaround provided to compile uvloop manually using :
expand the tar.gz archive somewhere and cd into it
additional step when get permission error on
./configure
:after that I can run theHarvester.
Can it be included in step to install theHarvester ? or do we need to do it manually ?
Screenshots
System Information (System that tool is running on):
Additional context
Just in case, so I'm asking about it. thanks for the awesome tool 👍
The text was updated successfully, but these errors were encountered: