| 1 |
Dnia 2015-01-25, o godz. 12:29:54 |
| 2 |
Michał Górny <mgorny@g.o> napisał(a): |
| 3 |
|
| 4 |
> Add a minimal SOCKSv5-over-UNIX-socket proxy to Portage, and start it |
| 5 |
> whenever ebuilds are started with network-sandbox enabled. Pass the |
| 6 |
> socket address in PORTAGE_SOCKS5_PROXY and DISTCC_SOCKS_PROXY variables. |
| 7 |
> The proxy can be used to escape the network sandbox whenever network |
| 8 |
> access is really desired, e.g. in distcc. |
| 9 |
> |
| 10 |
> The proxy currently supports IPv4 only, and does not report bound |
| 11 |
> address (reports 0.0.0.0:0). No authentication is supported (UNIX |
| 12 |
> sockets provide a security layer). |
| 13 |
|
| 14 |
Resubmitted with a number of fixes as: |
| 15 |
|
| 16 |
[PATCH v2] Support escaping network-sandbox through SOCKSv5 proxy |
| 17 |
|
| 18 |
-- |
| 19 |
Best regards, |
| 20 |
Michał Górny |
Archives