Include additional split to 'parse_fullname' to address new LinkedIn formatting

#282 Open
Repository
lijantropique
Branch
staging
Repository
LaNMaSteR53
Branch
staging

Bitbucket cannot automatically merge this request.

The commits that make up this pull request have been removed.

Bitbucket cannot automatically merge this request due to conflicts.

Review the conflicts on the Overview tab. You can then either decline the request or merge it manually on your local system using the following commands:

git checkout staging
git remote add lijantropique/recon-ng https://bitbucket.org/lijantropique/recon-ng.git
git fetch lijantropique/recon-ng
git merge --no-ff -m 'Merged in lijantropique/recon-ng/staging (pull request #282)' remotes/lijantropique/recon-ng/staging
Author
  1. Oscar J. Delgado
Reviewers
Description

Apparently LinkedIn has changed the structure of the name to:

<full name> - <position \(optional\) > - <company> \| LinkedIn

As result, the ‘contacts’ table is not properly completed, and sometimes the first name field includes also job description and even the company, while the other fields are empty. Modules using this table (e.g. mangle) are affected as well.

Solution proposed: Add an additional split to break the new structure. Note that some names that uses hyphen are not affected as long as they don’t have spaces around the hyphen (which is very uncommon for names).

Comments (0)