Re: [Tails-dev] Tests without transparent proxying

Delete this message

Reply to this message
Author: anonym
Date:  
To: The Tails public development discussion list
Subject: Re: [Tails-dev] Tests without transparent proxying
12/05/2011 10:21 PM, alan@???:
>
>> From: anonym <anonym@???>
>> Date: Mon, 5 Dec 2011 02:08:39 +0100
>>
> [...]
>>
>>> - "Torify HTP" (that actually torifies wget):
>>
>> Woops...
>>
>>>     I'm surprised, again,
>>>     to see wget does not take into account the http_proxy environment
>>>     variable.

>>
>> Init scripts are supposed to be self-contained w.r.t. to environment,
>> and in particular they don't load /etc/environment. Since there are
>> potentially other reasons for the environment to get lost I feel it's
>> safer to set the proxy it in wgetrc.
>>
> So what about:
>
>     --- a/config/chroot_local-includes/etc/init.d/htpdate
>     +++ b/config/chroot_local-includes/etc/init.d/htpdate
>     @@ -47,7 +47,7 @@ log() {
>      }

>
>      do_start() {
>     -       start-stop-daemon -S -q -p ${PIDFILE} -bm -x /usr/local/sbin/htpdate -- \
>     +       start-stop-daemon -S -q -p ${PIDFILE} -bm -x http_proxy="http://127.0.0.1:8118/" /usr/local/sbin/htpdate -- \
>                     -d \
>                     -l "$LOG" \
>                     -a "$HTTP_USER_AGENT" \


I think it must be https_proxy (or is http_proxy used for https if
https_proxy is unset?), but sure why not add it? It will, however, be
redundant since wgetrc already has proxies set.