Hi, all.
Sorry it has been so long since I've written.
I have just uploaded v0.2.0 of tails-clone-persistent[1], which is
memory-safe and relies entirely on polkit and sudoers to manage
privilege escalation.
There are still a couple of minor niggles, but I'm hoping someone on the
list can help w
Andrew Gallagher wrote (10 Jan 2016 01:38:20 GMT) :
>> On 10 Jan 2016, at 00:01, intrigeri wrote:
>>
>> In Tails, we also directly access the block device as the amnesia
>> user, since
>> /etc/udev/rules.d/99-make-removable-devices-user-writable.rules allows
>> us to do that.
> Ah, this could be
Andrew Gallagher
> On 10 Jan 2016, at 08:40, emmapeel wrote:
>
> Ok, I didn't tried Andrew's script, but I can say that the 'permissions
> issue' was for the users that attended the most difficult part to follow.
>
> As in after backing up they lose the configurations,
> live-additional-softw
sajolida:
> Spencer:
>>> Emma Peel (in copy) could be
>>> interested as she's been giving a workshop on Tails backups last week
>>> and 32C3.
>>
Ok, I didn't tried Andrew's script, but I can say that the 'permissions
issue' was for the users that attended the most difficult part to follow.
As in
> On 10 Jan 2016, at 00:01, intrigeri wrote:
>
> In Tails, we also directly access the block device as the amnesia
> user, since
> /etc/udev/rules.d/99-make-removable-devices-user-writable.rules allows
> us to do that.
Ah, this could be the game changer. I'll look into that and see if it gives
anonym wrote (08 Jan 2016 17:43:04 GMT) :
> I leave it to sajolida and u to decide on how the backup tool should
> integrate into the installer (or if it should be separate),
Same here.
> and for u and intrigeri to clarify the privileges separation situation
> in the installer (I think it's run a
Andrew Gallagher:
> On 07/01/16 19:41, anonym wrote:
>>
>> I haven't tested it, but I did have a look at src/tcp-helper.c since the
>> necessity of memory unsafe code surprised me:
>
> For the record, I never intended to use C. It was originally written in
> perl (like the GUI wrapper), but setuid
On 07/01/16 19:41, anonym wrote:
>
> I haven't tested it, but I did have a look at src/tcp-helper.c since the
> necessity of memory unsafe code surprised me:
For the record, I never intended to use C. It was originally written in
perl (like the GUI wrapper), but setuidperl is no longer supported
Spencer:
>> Emma Peel (in copy) could be
>> interested as she's been giving a workshop on Tails backups last week
>> and 32C3.
>
> I found this [0] but no record of anything here [1]. Are there any
> recordings of this workshop, or workshops in general, from this event?
It was an ad-hoc session
On 07/01/16 14:16, sajolida wrote:
>
> But we're definitely lacking people writing code in Tails as well,
> especially Perl, so it's a good news in and off itself that you can
> write Perl and do Debian packages!
You may have to retract that after you read the code. ;-) I'm a sysadmin
more than a
Andrew Gallagher:
> On 13/12/15 17:46, sajolida wrote:
>>
>> If you're interested in plugging this in the current code [1] that would
>> be awesome. But as we haven't really finished the design decision around
>> the backup scenarios, I can't promise anything regarding it's official
>> acceptance y
On 13/12/15 17:46, sajolida wrote:
>
> If you're interested in plugging this in the current code [1] that would
> be awesome. But as we haven't really finished the design decision around
> the backup scenarios, I can't promise anything regarding it's official
> acceptance yet.
I have a reasonably
Andrew Gallagher:
> On 11/12/15 10:57, sajolida wrote:
>> We have "backup system for persistence" on our roadmap for 2016 [1][2]
>> and I'll be the one to work on the broad picture, UX design, etc. So I'm
>> definitely interested in your work but I wanted to test it before
>> answering (but couldn'
On 11/12/15 10:57, sajolida wrote:
>
> Hi Andrew, sorry for not answering earlier but as u said we're all too
> busy right now. It's the end of the year and we have to finish many
> projects.
Completely understandable! Sorry for nagging.
> We have "backup system for persistence" on our roadmap f
On 10/12/15 19:16, u wrote:
> Hi Andrew,
>
> Andrew Gallagher:
>> Nobody interested?
>
> I guess most of us are simply quite busy atm - but yes, as we created
> this ticket initially, we are interested in such a solution. Thank you
> for working on this.
Sorry, that may have come out more sarcas
u:
> Andrew Gallagher:
>> Nobody interested?
>
> I guess most of us are simply quite busy atm - but yes, as we created
> this ticket initially, we are interested in such a solution. Thank you
> for working on this.
Hi Andrew, sorry for not answering earlier but as u said we're all too
busy right
Hi Andrew,
Andrew Gallagher:
> Nobody interested?
I guess most of us are simply quite busy atm - but yes, as we created
this ticket initially, we are interested in such a solution. Thank you
for working on this.
I had a quick view, but I am not knowledgeable in Perl and just saw that
you use rsy
Nobody interested?
To be clear, I'm willing to put in the work. I just don't want to spend
too much time on it if it isn't going to go anywhere.
Andrew.
On 03/12/15 12:51, Andrew Gallagher wrote:
> Hi, all.
>
> I've written a tool to clone the contents of a mounted persistent volume
> (or any o
18 matches
Mail list logo
