Re: [Tails-dev] Pip is not torified by default

Delete this message

Reply to this message
Autor: Patrick
Data:  
Para: tails-dev
Assunto: Re: [Tails-dev] Pip is not torified by default
>You could get some stream isolation by adding a "username" with a
value not used by other apps.
>The file /usr/local/bin/curl shows how to create a random one each time.
>That'd be hard to do in a pip.conf file, but even a "username" created

once would create a different stream compared to other applications on
Tails, and that would provide *some* isolation.


Update: python3-pip is not included in latest Tails release


I was doing some more testing and noticed that its not included anymore
as of the latest release. Not exactly sure what in the building process
removed it.

When typing `pip`, `pip install <package>` returns bash not found and
`which pip` returns nothing.

`apt list --installed |grep python3-pip` returns nothing.

Python3-pip should be added back next release and with a global config
to torify it by default.
There are many nice python tools not included with tails that users may
like to install. Also pip seems like a easy way to test different python
tools for use and possible integration onto tails.

A persistent storage feature for user installed python packages could
also be designed to be a hook that adds the appropriate corresponding
.local folders to the persistence.conf upon activation of the feature.