PDA

View Full Version : theharvester doesn't output anything



ld4lpha
2016-03-26, 03:55
I have run theharvester from a root shell, and it drops no output. I then cloned the git repo and ran the script directly from within that cloned directory, and it works as expected. I haven't delved too deeply into figuring this one out, and am wondering if anyone has seen this before and/or has any idea why this is happening. Any help is much appreciated!

The output of both commands is below (the bottom one is clipped for brevity):


root@hostname:/home/ld4lpha# theharvester -d cnn.com -b all -l 300 > /home/ld4lpha/Desktop/harvest

************************************************** *****************
* *
* | |_| |__ ___ /\ /\__ _ _ ____ _____ ___| |_ ___ _ __ *
* | __| '_ \ / _ \ / /_/ / _` | '__\ \ / / _ \/ __| __/ _ \ '__| *
* | |_| | | | __/ / __ / (_| | | \ V / __/\__ \ || __/ | *
* \__|_| |_|\___| \/ /_/ \__,_|_| \_/ \___||___/\__\___|_| *
* *
* TheHarvester Ver. 2.6 *
* Coded by Christian Martorella *
* Edge-Security Research *
* [email protected] *
************************************************** *****************


Full harvest..
[-] Searching in Google..
Searching 0 results...
Searching 100 results...
Searching 200 results...
Searching 300 results...
[-] Searching in PGP Key server..
[-] Searching in Bing..


root@hostname:/home/ld4lpha/Desktop/theHarvester# ./theHarvester.py -d cnn.com -b all -l 300 >> /home/ld4lpha/Desktop/harvest

************************************************** *****************
* *
* | |_| |__ ___ /\ /\__ _ _ ____ _____ ___| |_ ___ _ __ *
* | __| '_ \ / _ \ / /_/ / _` | '__\ \ / / _ \/ __| __/ _ \ '__| *
* | |_| | | | __/ / __ / (_| | | \ V / __/\__ \ || __/ | *
* \__|_| |_|\___| \/ /_/ \__,_|_| \_/ \___||___/\__\___|_| *
* *
* TheHarvester Ver. 2.6 *
* Coded by Christian Martorella *
* Edge-Security Research *
* [email protected] *
************************************************** *****************


Full harvest..
[-] Searching in Google..
Searching 0 results...
Searching 100 results...
Searching 200 results...
Searching 300 results...
[-] Searching in PGP Key server..
[-] Searching in Bing..
Searching 50 results...
Searching 100 results...
Searching 150 results...
Searching 200 results...
Searching 250 results...
Searching 300 results...
[-] Searching in Exalead..
Searching 50 results...
Searching 100 results...
Searching 150 results...
Searching 200 results...
Searching 250 results...
Searching 300 results...
Searching 350 results...


[+] Emails found:
------------------
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
@cnn.com

[+] Hosts found in search engines:
------------------------------------
[-] Resolving hostnames IPs...
23.235.44.73:www.cnn.com
23.235.44.73:edition.cnn.com
157.166.224.109:money.cnn.com
106.186.16.40:sportsillustrated.cnn.com
157.166.226.110:transcripts.cnn.com
23.235.40.73:www.cnn.com
157.166.226.108:money.cnn.com
23.235.40.73:edition.cnn.com
192.0.79.33:news.blogs.cnn.com
192.0.79.33:newday.blogs.cnn.com
192.0.79.33:ac360.blogs.cnn.com
192.0.79.32:politicalticker.blogs.cnn.com
192.0.79.32:newsroom.blogs.cnn.com
157.166.248.146:weather.cnn.com
107.21.200.223:rss.cnn.com
23.235.40.73:us.cnn.com
23.235.40.73:go.cnn.com
192.0.79.33:thechart.blogs.cnn.com
192.0.79.32:religion.blogs.cnn.com
192.0.79.33:globalpublicsquare.blogs.cnn.com
192.0.79.32:cnnpressroom.blogs.cnn.com
192.0.79.32:sanjayguptamd.blogs.cnn.com
157.166.239.216:weather.edition.cnn.com
23.235.44.73:smartlink.cnn.com
104.236.210.125:podcast.cnn.com
192.0.79.32:cnnradio.cnn.com
192.0.78.13:cnnespanol.cnn.com
54.243.244.144:m.cnn.com
192.0.79.32:cnnphotos.blogs.cnn.com
and so on...

sickn3ss
2016-03-26, 08:12
You might want to open a bug report on our bugtracker that way someone can look into it.

ld4lpha
2016-03-26, 16:15
Good call. Thanks. Here's the link to the bug report for future reference:

https://bugs.kali.org/view.php?id=3191