intrigeri wrote (05 Dec 2011 19:06:40 GMT) :
> So, hey, folks, heads up! Nobody bases new work on top of the
> feature/no_transparent_proxy branch until anonym replies to this
> email and releases the lock.
FTR the branch history was rewritten already so I guess the lock is released.
Cheers!
--
Hi,
anonym wrote (06 Dec 2011 12:36:10 GMT) :
> 12/05/2011 10:21 PM, a...@boum.org:
>> - 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 -- \
> I think it m
12/05/2011 04:14 PM, anonym:
> 12/05/2011 02:08 AM, anonym:
>> 12/02/2011 10:15 PM, intrigeri:
>>>
>>> - "Torify seahorse": does Seahorse really ignore the global GNOME
>>> HTTP proxy settings? Bug report?
>>
>> When I did the tests the indymedia hidden service were unavailable, so I
>> tried
12/05/2011 10:21 PM, a...@boum.org:
>
>> From: 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
>>> variabl
> From: 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 sel
anonym wrote (05 Dec 2011 01:08:39 GMT) :
> Yeah you're right. I'll rewrite the commit messages when I can
> verify that no one else is working on that branch.
I doubt anyone other than you or I may be working on that branch these
days. If I'm wrong, they'll just have to rebase on top of your
rewr
12/05/2011 02:08 AM, anonym:
> 12/02/2011 10:15 PM, intrigeri:
>>
>> - "Torify seahorse": does Seahorse really ignore the global GNOME
>> HTTP proxy settings? Bug report?
>
> When I did the tests the indymedia hidden service were unavailable, so I
> tried hkp://keys.gnupg.net, which consist
12/02/2011 10:15 PM, intrigeri:
>> * Since we configured apt to use polipo on port 8118
>
> Was fixed for a while in my tree, but I forgot to push.
> I am sorry for the inconvenience it caused.
While it builds I still get apt-related proxy errors the stage after the
actual iso is created.
> Abou
intrigeri wrote (02 Dec 2011 21:15:37 GMT) :
>> * Who marked "iceweasel FTP" as working?
> I did. I'll try reproducing this again.
Indeed I get a "425 - Failed to establish connection" error with
current feature/no_transparent_proxy. FYI, the fact it was not working
in 0.9 (and earlier) is a known
Hi,
(about
https://tails.boum.org/todo/the_end_of_transparent_proxying__63__/)
Great to see you testing that stuff!
> * Who marked "iceweasel FTP" as working?
I did. I'll try reproducing this again.
> * Since we configured apt to use polipo on port 8118
Was fixed for a while in my tree, but
10 matches
Mail list logo
