Improving bing_linkedin_cache results

Issue #244 resolved
Ethan Robish
created an issue

@Brian King @B Fehrman

I'm wondering if including quotes around the company in the search terms would improve results generally. It seemed to be the case in my particular instance. I had a company named "Acme Bank" and with the current implementation ended up with a ton of contacts with the last name of "Acme" in the results. By including quotes, it seemed to filter out these folks.

Can you think of any reason not to do this?

Before change:

"site:\"%slinkedin.com/in/\" && %s" % (subdomain, company),
"site:%slinkedin.com -jobs && %s" % (subdomain, company),
"site:%slinkedin.com instreamset:(url):\"pub\" -instreamset:(url):\"dir\" && %s" % (subdomain, company)

After change:

"site:\"%slinkedin.com/in/\" && \"%s\"" % (subdomain, company),
"site:%slinkedin.com -jobs && \"%s\"" % (subdomain, company),
"site:%slinkedin.com instreamset:(url):\"pub\" -instreamset:(url):\"dir\" && \"%s\"" % (subdomain, company)

Comments (3)

  1. Tim Tomes repo owner

    Relocated the recon_web source code.

    Fixed several bugs in the bing_linkedin_cache module. Resolves issue #240. (@Brian King)

    Added a new module that harvests hosts and netblocks via MX and SPF DNS records for a domain. (@KoreLogicSecurity)

    Enhanced the parser in the bing_linkedin_cache module. Resolves issue #244. (@Ethan Robish)

    Modified the certificate_transparency module to return more hosts. (@Sigurd Kolltveit)

    Refactored location parsing logic to fix a bug in the whois_miner module. Resolves issue #241.

    → <<cset 9fdc4d7e7cd4>>

  2. Log in to comment