My view is that we should not be executing the setup script on first run, as this could easily break kali in future upstream updates. We are probably better off seeing what wine configurations are applied, and applying those via postinst scripts.

Unfortunately... lots.
Source: https://github.com/Veil-framework/veil-Evasion/blob/master/setup/setup.sh

Summary:

Python

• Python 2.7.5
• pywin32
• pycrypto
• 3x ZIP files - all are required to install Python via WINE.

Ruby

• Ruby 1.8.7
• Ruby gem ocra
• 1x ZIP file (not sure what it does)

Go

• Cross compile to allow Windows i386 builds.

Hello,
I pushed the new version 2.21.1-0kali1 i sana and kali-dev only. I upgraded the setup/setup.sh to avoid the remove of veil-evasion and few other details about installation. I also packaged python-symmetric-jsonrpc for sana and kali-dev-only.
I packaged the version 2.12.1 because it's the latest upstream tagged release.

Anyway of getting python-symmetric-jsonrpc for moto main?

This way, I can make a PR upstream, fixing the setup.sh - then it can be tagged as a new release.

The tool supports kali 1.0 as thats the only thing thats out.
Else, I can't make a PR/merge upstream until sana has been released (and the package would then need to be updated again after launch).

I just pushed python-symmetric-jsonrpc in moto. Maybe it will take few hours before it reaches the mirrors.

Pull request made: https://github.com/Veil-Framework/Veil-Evasion/pull/197

Asked author to tag release after merging.

Merged & tagged!
Any releases from v2.21.1.1 onwards, should have the fixes ~ https://github.com/Veil-Framework/Veil-Evasion/releases/

Note, I've tested 2.21.1-0kali1 release (on kali 2) and there's various issues with the program's setup method (not the packaging).

Example of issues:

[>] Please enter a command: use 17

=========================================================================
 Veil-Evasion | [Version]: 2.21.1
=========================================================================
 [Web]: https://www.veil-framework.com/ | [Twitter]: @VeilFramework
=========================================================================

 Payload: native/Hyperion loaded

 Required Options:

 Name           Current Value   Description
 ----           -------------   -----------
 original_exe                   The executable to run Hyperion on

 Available commands:

    set             set a specific option value
    info            show information about the payload
    generate        generate payload
    back            go to the main menu
    exit            exit Veil

 [>] Please enter a command: set original_exe  /usr/share/windows-binaries/whoami.exe
 [>] Please enter a command: generate

[*] Running Hyperion on /usr/share/windows-binaries/whoami.exe...

Error during Hyperion execution:

[>] Press any key to return to the main menu:

[>] Please enter a command: use python/meterpreter/rev_tcp

=========================================================================
Veil-Evasion | [Version]: 2.21.1

=========================================================================

Payload: python/meterpreter/rev_tcp loaded

Required Options:

Name Current Value Description

LHOST IP of the metasploit handler
LPORT 4444 Port of the metasploit handler
architecture 32 Select the final binary architecture
compile_to_exe Y Compile to an executable
expire_payload X Optional: Payloads expire after "X" days
use_pyherion N Use the pyherion encrypter

Available commands:

set             set a specific option value
info            show information about the payload
generate        generate payload
back            go to the main menu
exit            exit Veil

[>] Please enter a command: set LHOST 127.0.0.1
[>] Please enter a command: generate

=========================================================================
Veil-Evasion | [Version]: 2.21.1

=========================================================================

[*] Press [enter] for 'payload'
[>] Please enter the base name for output files:

[?] How would you like to create your payload executable?

 1 - Pyinstaller (default)
 2 - Pwnstaller (obfuscated Pyinstaller loader)
 3 - Py2Exe

[>] Please enter the number of your choice: 1
Error: PyInstaller for Python 2.6+ on Windows needs pywin32.
Please install from http://sourceforge.net/projects/pywin32/
mv: cannot stat ‘dist/payload1.exe’: No such file or directory
rm: cannot remove ‘.spec’: No such file or directory
rm: cannot remove ‘logdict.*’: No such file or directory

=========================================================================

So I uploaded veil-evasion_2.21.1.1-0kali1.dsc to kali-dev. I did not have the time to test it yet. I'd love if you could test it for me as soon as it's built.

In case it's not yet in sana, you can grab the .deb on http://repo.kali.org/kali/pool/main/v/veil-evasion/ and install it manually in your sana installation to test it.

I managed to test the package and it seems to work fine. Both your samples lead to the creation of a payload.exe file...

Ran the same two tests from before (native/Hyperion & python/meterpreter/rev_tcp) - working great!

The setup script completed without any issues.
In my eyes the self destructing issue/bug that started all of this, has been removed!

...If we want to, can do a automated setup install 'bash ./setup/setup.sh -s" (no user prompts - same output)