On Fri, Oct 18, 2013 at 03:03:42PM +0200, intrigeri wrote:
> Hi,
>
> Branch: security/vidalia_in_its_own_user (no APT stuff)
> No ticket.
>
> Please review and merge into testing (and devel) in time for
> 0.21 final.
Tested, merged and pushed into devel and testing.
bert.
__
On Sun, Oct 20, 2013 at 02:29:51PM +0200, intrigeri wrote:
> intrigeri wrote (20 Oct 2013 11:45:54 GMT) :
> > Actually, please merge feature/linux-3.10.11 into testing only, and
> > please merge feature/linux-3.11-1 into devel (it his
> > feature/linux-3.10.11 in, plus the revert, plus the switch t
On Sat, Oct 19, 2013 at 04:54:46PM +0200, intrigeri wrote:
> Hi,
>
> Tails 0.20.1 and 0.21~rc1 are affected by #6377
> aka. https://trac.torproject.org/projects/tor/ticket/8478.
>
> This is fixed in bugfix/browser-resizing with a new Torbutton package
> (no Git commits) that cherry-picks the rele
berta...@ptitcanardnoir.org wrote (21 Oct 2013 12:36:23 GMT) :
> Done, get a 1000x594 Torbrowser window compared to a 1000x573 one without
> this patch. Closer to 200x100 aspect ratio, so I merged and pushed it in
> testing and devel.
Thanks. I've asked upstream what they think about it:
https://t
Hi,
Mike Perry wrote (02 Apr 2013 08:52:56 GMT) :
> #8511 might cause you problems if you use a $TOR_SOCKS_PORT env var with
> a value other than 9151, though. You may want to either add iptables
> redirect rule for 9151 or add an additional SocksPort line to your torrc
> rather than messing with
Hi,
Mike Perry wrote (25 Sep 2013 02:37:38 GMT) :
> I think you mostly want to pick up the patch for Bug #8478.
Thanks for the hint, done for Tails 0.21. Slightly weird results:
https://trac.torproject.org/projects/tor/ticket/8478#comment:25
> However, you should probably start investigating 1.6
Hi!
intrigeri:
> unset TOR_CONTROL_PORT and TOR_CONTROL_HOST (non-working
> anyway, since we are forbidding access to the control port for
> the amnesia user)
What's your rationale behind that? Probably "GETINFO address"?
Would that be worth adding to Tails design doc? Haven't seen it
Hi,
adrelanos wrote (21 Oct 2013 15:33:11 GMT) :
>> since we are forbidding access to the control port for the
>> amnesia user)
> What's your rationale behind that? Probably "GETINFO address"?
Exactly.
> Would that be worth adding to Tails design doc? Haven't seen it there.
It's not
I added to Redmine more logo ideas, submitted by Andrew Pilkington from
Picasso Fish [1]. That a totally different look from what Carmie
proposed so far. I particularity like the bottom-right one, the mask
made with question marks.
See: https://labs.riseup.net/code/attachments/351/TailsConcept3.pd
On 17/10/13 16:21, Alan wrote:
> On Mon, 14 Oct 2013 11:41:28 +0200
> sajol...@pimienta.org wrote:
>
_("You are going to install Tails on the %(vendor)s %(model)s
device (%(size)s). " "All data on the selected drive will be lost.
" "Continue?")
>>> I'm afraid that the phrasi
On 21/09/13 12:07, intrigeri wrote:
> Alan tried to test this during the low-hanging fruits session, and
> failed, so I:
>
> * cleaned up the feature-consistent-peristence-path APT suite
> (that apparently had an old version of devel merged in, which
> certainly helps for early testing, but is a n
sajol...@pimienta.org wrote (21 Oct 2013 20:14:08 GMT) :
> I merged devel and testing into it. I think it has to be merged into
> testing but I'd rather not do that myself.
Once we're frozen, we don't merge into testing branches based
on devel.
Oh well, yes we can, but then we have to go through
intrigeri:
>> You might be interested in the solution I came up with for Whonix. It's
>> called Control Port Filter Proxy. [1] In essence, "wretch a proxy in
>> between Tor Browser and control port, allow a few hand selected, white
>> listed control port commands, discard the rest". I'd be interest
13 matches
Mail list logo