Add Parrot Security OS to setup script

[dmknght]

Veil version

Veil | [Version]: 3.1.11 (apt version: Version: 3.1.11-0kali1)

OS Used - all info (architecture, linux flavor, etc)

Parrot Security OS 4.5 amd64

How did you install Veil? (Apt, Clone from Github, etc.)

sudo apt install veil && veil

Did you run the setup script?

Yes

Error message

[!] ERROR #2-3: Can’t find the Metasploit Framework (/opt/metasploit-framework/embedded/framework/). Run: /usr/share/veil/config/setup.sh --force --silent

Expected behavior

Veil should detect metasploit-framework path on Parrot Security OS

Any additional info you want to tell me

By default, veil has hard-coded metasploit-framework path. Parrot OS as same as path.

But, veil detects Parrot Security OS as regular Linux distribution, which caused "can't find path" issue

Forum issue URL https://community.parrotsec.org/t/veil-evasion-doesnt-install/5626/12

Suggestion: Add Parrot to line 196

[ChrisTruncer]

I can’t control how Veil is packaged in apt, so that’s not something that I can change. I personally don’t have Parrot, but since you do, would you like to test the fix and then submit a pull request? I can review it then and get it merged in.

…

________________________________ From: dmknght <[email protected]> Sent: Friday, February 8, 2019 7:24 AM To: Veil-Framework/Veil Cc: Subscribed Subject: [EXTERNAL E-MAIL]: [Veil-Framework/Veil] Add Parrot Security OS to setup script (#284) Veil version Veil | [Version]: 3.1.11 (apt version: Version: 3.1.11-0kali1) OS Used - all info (architecture, linux flavor, etc) Parrot Security OS 4.5 amd64 How did you install Veil? (Apt, Clone from Github, etc.) sudo apt install veil && veil Did you run the setup script? Yes Error message [!] ERROR #2-3: Can’t find the Metasploit Framework (/opt/metasploit-framework/embedded/framework/). Run: /usr/share/veil/config/setup.sh --force --silent Expected behavior Veil should detect metasploit-framework path on Parrot Security OS Any additional info you want to tell me By default, veil has hard-coded metasploit-framework path. Parrot OS as same as path. [screenshot from 2019-02-08 21-12-56]<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuser-images.githubusercontent.com%2F29118926%2F52483728-32216580-2be7-11e9-8e49-5ce74c9a2bf1.png&data=02%7C01%7Cchris%40fortynorthsecurity.com%7C7fabfc427bae478857aa08d68dd113ab%7C13e7061fe89b41a78b92ac403c961ded%7C1%7C0%7C636852326454686042&sdata=4QvUYaGwBvMNHnd%2BhBCNlqgJd%2F3bpREPyU8jKBUcOY4%3D&reserved=0> But, veil detects Parrot Security OS as regular Linux distribution, which caused "can't find path" issue [screenshot from 2019-02-08 21-11-18]<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuser-images.githubusercontent.com%2F29118926%2F52483948-acea8080-2be7-11e9-8f74-c264c60e3e52.png&data=02%7C01%7Cchris%40fortynorthsecurity.com%7C7fabfc427bae478857aa08d68dd113ab%7C13e7061fe89b41a78b92ac403c961ded%7C1%7C0%7C636852326454696047&sdata=vCZbCvZpctky%2FxyxGTh9pVHgzZy7ZXYpWOAG6SGapC0%3D&reserved=0> Suggestion: Add Parrot to line 196 — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FVeil-Framework%2FVeil%2Fissues%2F284&data=02%7C01%7Cchris%40fortynorthsecurity.com%7C7fabfc427bae478857aa08d68dd113ab%7C13e7061fe89b41a78b92ac403c961ded%7C1%7C0%7C636852326454696047&sdata=ttj40rXQubvg%2Bmk%2Fcr7%2B3tA4JL%2BoNYxFJ7anxxaNwEQ%3D&reserved=0>, or mute the thread<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FABmORl2Sy7gspAiOB_WmGTdJQzln0Dclks5vLYiAgaJpZM4av6Le&data=02%7C01%7Cchris%40fortynorthsecurity.com%7C7fabfc427bae478857aa08d68dd113ab%7C13e7061fe89b41a78b92ac403c961ded%7C1%7C0%7C636852326454706066&sdata=XfQEbdjdM%2F1UpF2prGPtCXBLSAfMjbFfIz44FjaEzCE%3D&reserved=0>. [EXTERNAL E-MAIL] - ATTENTION: This e-mail was sent from an external source!

[dmknght]

I believe if you update script and release next version, Kali and Parrot repository will update it and problem will be solved in next version. I am testing setup script. I will create pull request as soon as possible