Example 3-2. theHarvester LinkedIn results
root@rosebud:~# theharvester -d gmail.com -l
1000
-b linkedin
*******************************************************************
* *
* | |_| |__ ___ /
\
/
\_
_ _ _ ____ _____ ___| |_ ___ _ __ *
* | __|
'_ \ / _ \ / /_/ / _` | '
__
\ \
/ / _
\/
__| __/ _
\
'
__| *
* | |_| | | | __/ / __ /
(
_| | |
\
V / __/
\_
_
\
||
__/ | *
*
\_
_|_| |_|
\_
__|
\/
/_/
\_
_,_|_|
\_
/
\_
__
||
___/
\_
_
\_
__|_| *
* *
* TheHarvester Ver. 2.7 *
* Coded by Christian Martorella *
* Edge-Security Research *
* cmartorella@edge-security.com *
*******************************************************************
[
-
]
Searching in Linkedin..
Searching
100
results..
Searching
200
results..
Searching
300
results..
Searching
400
results..
Searching
500
results..
Searching
600
results..
Searching
700
results..
Searching
800
results..
Searching
900
results..
Searching
1000
results..
Users from Linkedin:
====================
This is another case that may require multiple searches. Fortunately, in this case you
can write a little script to make your life easier. In
Example 3-3
, you can see a simple
Python script that will run through a few providers, given a domain name provided
on the command line. This script could be beefed up substantially if it was intended
to be used across multiple users who didn’t necessarily understand how it worked.
For my own personal use, though, this works perfectly. What you should end up with
is a number of files, both XML and HTML, for each of the providers that returned
results.
