intrigeri wrote (04 Feb 2015 10:36:45 GMT) :
> Good enough? Shall we try that and see? I've implemented #3 already,
> and can do #1 and #2 for Tails 1.3.1.
Thanks for the replies. Created #8852 to track the next steps.
___
Tails-dev mailing list
Tails-de
On Wed, Feb 04, 2015 at 12:10:31PM +0100, anonym wrote:
> On 04/02/15 11:36, intrigeri wrote:
> [...]
> > Good enough? Shall we try that and see? I've implemented #3 already,
> > and can do #1 and #2 for Tails 1.3.1.
>
> I'm convinced and have nothing more to add than "well done!". :)
I do too. T
On 04/02/15 11:36, intrigeri wrote:
[...]
> Good enough? Shall we try that and see? I've implemented #3 already,
> and can do #1 and #2 for Tails 1.3.1.
I'm convinced and have nothing more to add than "well done!". :)
Cheers!
___
Tails-dev mailing list
Hi,
anonym wrote (26 Jan 2015 12:17:22 GMT) :
> While I appreciate #1 forcing us to track upstream, I think these build
> failures that depend on things external to Tails (e.g. fetching from APT
> repos outside of our control) are quite problematic:
> * They further complicate things for potentia
On 23/01/15 20:50, intrigeri wrote:
> Hi,
>
> I'm working on #5525 ("Sandbox the web browser"), and have an AppArmor
> profile that works locally for most basic use cases. Now, I'm
> wondering how to integrate it into Tails and I need your input.
>
> This profile was derived from the one I've wor
intrigeri wrote (25 Jan 2015 08:50:32 GMT) :
> u wrote (24 Jan 2015 19:54:11 GMT) :
>> Do you want to point me at the Tails-specific patch so I can see what we
>> are talking about?
> I'll do that once I have implemented it as a patch. In the meantime:
> https://git-tails.immerda.ch/tails/tree/con
hi,
bertagaz wrote (25 Jan 2015 12:14:21 GMT) :
> While I think I could help with maintaining this profile when it breaks
> the build, I'm not much comfortable with this option from my CI hat point
> of view. It means that every devs would be notified of this breakage if/when
> automatic builds wi
On Fri, Jan 23, 2015 at 08:50:28PM +0100, intrigeri wrote:
>
> I'm working on #5525 ("Sandbox the web browser"), and have an AppArmor
> profile that works locally for most basic use cases. Now, I'm
> wondering how to integrate it into Tails and I need your input.
>
> I think we have two solutions
Hi,
u wrote (24 Jan 2015 19:54:11 GMT) :
>> => I'm in favor of #1.
> Me too.
OK, I'll start preparing things in this direction, then.
(Not to say we can't revert to #2 or something else later,
so more input is still welcome until the end of the month :)
> Indeed, as I am co-maintaining torbrows
Hi,
intrigeri:
> I'm working on #5525 ("Sandbox the web browser"), and have an AppArmor
> profile that works locally for most basic use cases. Now, I'm
> wondering how to integrate it into Tails and I need your input.
>
> This profile was derived from the one I've worked a lot on for
> torbrowser
On Fri, 23 Jan 2015 19:50:57 + (UTC)
intrigeri wrote:
> => I'm in favor of #1.
>
#1 also sounds like the best long-term option.
> Thoughts, opinions, volunteers?
> * it would be good if more of us learned the basics of AppArmor,
> anyway :)
AppArmor is something I really need to
Hi,
I'm working on #5525 ("Sandbox the web browser"), and have an AppArmor
profile that works locally for most basic use cases. Now, I'm
wondering how to integrate it into Tails and I need your input.
This profile was derived from the one I've worked a lot on for
torbrowser-launcher (https://mica
12 matches
Mail list logo
