Broken setup about scapy-ssl_tls

[tintinweb]

Hi @CristianVladescu, appreciate your report!

When installing scapy-ssl_tls with pip or setup.py setuptools is creating a python package in the site-packages directory. To make layer files automatically available to scapy we're also copying relevant layer files to scapy/layers and patching the layer loader to include ssl_tls.

In your case you are building a version of python to /opt/Python-2.7.13 and then installing scapy-ssl_tls to that python environment. Installing it as a python package is by intention and makes the package available to other python projects. However, in your case you seem to mix up python versions/environments and I am not quite sure if it was intendet the way you're using it. I would suggest to run /opt/Python-2.7.13/bin/python2.7 -m pip install setuptools (make sure to have setuptools installed and compile python with ssl support, you'll probably need it anyway for all the crypto) to force pip to run with the custom python version and install the packages from there.

Installing from one python environment to the other using pip -t (this is running system's python interpreter): The main problem we have with pip -t is that we do not seem to have the custom target destination available in setup.py. Maybe this will get fixed when moving to python whl instead. Right now we try to find scapys location in the current python interpreters user and system site-packages location.

Please try installing it by running pip with the python environment from /opt and report back if that resolves your problems. Virtualenv might also be an alternative for you (see ci-runtests.sh which installs scapy-ssl_tls to a venv)

tin

[tintinweb]

feel free to reopen this issue if you feel like there's something we can do on our side.