> On 14 Jul 2018, at 14:58, Sebastian Nielsen wrote:
> This also means any single tails installation media can be used by unlimited
> users. And that would also make it more interesting for internet cafés and
> such to install Tails on their public computers, since tails then become
>
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
> On 4 Mar 2018, at 00:13, Jacob Adams wrote:
>
> The biggest hurdle I faced when setting up my GPG key was creating and
> storing it offline. I am looking to create a proper interface for a PGP
> Clean Room Live CD that walks a user through setting up a set of USB
> flash
On 2017/04/27 14:41, forgottenbeast wrote:
> Thanks for your thorough reply, to be honest I hadn't thought about
> those issues.
>
> In the spirit of using already developed solutions I reckon truecrypt's
> successor, veracrypt, must have been given some thoughts, what were the
> conclusions? In
On 2017/04/27 08:10, forgottenbeast wrote:
> This way we would be able to write some random data here and there in
> the persistent volume (random locations) at every boot without taking
> much risks regarding the integrity of existing persistent data. Either
> there IS a persistent volume and the
> On 14 Mar 2017, at 08:32, intrigeri wrote:
>
> I personally combine two approaches, depending on the need:
>
> * build a modified ISO image
> * start Tails and modify files in there (it *is* writable, but of
> course the modifications go to a ramdisk)
If you know your
On 24/03/16 13:40, sajolida wrote:
>
> in
> #10543#note-6 [1] you'll find my snippet to add custom files to
> /etc/apt/sources.list.d/.
>
> [1]: https://labs.riseup.net/code/issues/10543#note-6
This is *exactly* my use case. Thank you!
A
signature.asc
Description: OpenPGP digital signature
On 23/03/16 18:30, sajolida wrote:
>
> You can use the "link" type in persistence.conf. I've done similar
> things already while playing with #10543.
Could you point to a doc/howto for doing that? It might save me some
grief in something else I'm playing with...
Thanks.
A
signature.asc
Hi, Regina.
You have encrypted your message so that only one (unknown) person can
read it:
gpg: decryption failed: No secret key
Note: The message is encrypted for the following User ID's / Keys:
0x45D5D028F59FF9BF
A
signature.asc
Description: OpenPGP digital signature
On 29/02/16 18:26, m...@riseup.net wrote:
>
> Another bigger issue that should be considered is: Implementing a
> failsafe mechanism that wipes the persistent drive if a number of failed
> attempts are made.
>
> I really think that type of protection is needed. Say after 5 failed
> attempts it
On 03/02/16 12:34, sajolida wrote:
>
> git config --add transfer.fsckobjects true
That fixes it per-repository. To change your user defaults:
git config --add --global transfer.fsckobjects true
A
signature.asc
Description: OpenPGP digital signature
>
> I tested this on Debian Unstable, with an iso I already had
> downloaded. There were some warnings about my internal hdd:
> austin@debian-laptop:~$ tails-installer-launcher
> [creator.py:622 (detect_supported_drives)] WARNING: Skipping device
> '/org/freedesktop/UDisks2/block_devices/sda'
Andrew Gallagher
> On 10 Jan 2016, at 08:40, emmapeel <emmap...@aktivix.org> 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
> 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
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
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
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
Hi, all.
I've written a tool to clone the contents of a mounted persistent volume
(or any other given directory tree) to a fresh or existing persistent
volume on another tails drive. It was done as part of a pet project, but
this functionality really belongs in tails itself.
It consists of two
18 matches
Mail list logo