Configuring persistent storage on Tails linux
When using tails linux, I am having difficult configuring persistent storage. I run a VMWare VM, and boot off the tails iso, and I have a vmdk configured as attached to the machine. The vmdk volume is formatted ext3 and lives at /dev/sda5p1
. I'd like to use it to store things like public keys and email addresses so that I don't have to go pull them down every time I fire up the machine again. However, I cannot update the fstab on the iso, and when I go to Applications > System Tools > Configure Persistent Storage, the app complains that I don't have any usb media attached. The vmdk is scsi, of course.
Is there a way to configure tails with a persistent device? Yes, I am aware that tails is amnesiac, but I'd just like a way to store non-sensitive data so that I'm not starting up "stateless" every time.
The only workaround I've been able to think of is to have a tarball at an easily-typed/remembered url I can (cd /tmp; wget -qO - http://foo | tar xvf - )
with. That's tedious, and not quite ideal.
linux tails
add a comment |
When using tails linux, I am having difficult configuring persistent storage. I run a VMWare VM, and boot off the tails iso, and I have a vmdk configured as attached to the machine. The vmdk volume is formatted ext3 and lives at /dev/sda5p1
. I'd like to use it to store things like public keys and email addresses so that I don't have to go pull them down every time I fire up the machine again. However, I cannot update the fstab on the iso, and when I go to Applications > System Tools > Configure Persistent Storage, the app complains that I don't have any usb media attached. The vmdk is scsi, of course.
Is there a way to configure tails with a persistent device? Yes, I am aware that tails is amnesiac, but I'd just like a way to store non-sensitive data so that I'm not starting up "stateless" every time.
The only workaround I've been able to think of is to have a tarball at an easily-typed/remembered url I can (cd /tmp; wget -qO - http://foo | tar xvf - )
with. That's tedious, and not quite ideal.
linux tails
add a comment |
When using tails linux, I am having difficult configuring persistent storage. I run a VMWare VM, and boot off the tails iso, and I have a vmdk configured as attached to the machine. The vmdk volume is formatted ext3 and lives at /dev/sda5p1
. I'd like to use it to store things like public keys and email addresses so that I don't have to go pull them down every time I fire up the machine again. However, I cannot update the fstab on the iso, and when I go to Applications > System Tools > Configure Persistent Storage, the app complains that I don't have any usb media attached. The vmdk is scsi, of course.
Is there a way to configure tails with a persistent device? Yes, I am aware that tails is amnesiac, but I'd just like a way to store non-sensitive data so that I'm not starting up "stateless" every time.
The only workaround I've been able to think of is to have a tarball at an easily-typed/remembered url I can (cd /tmp; wget -qO - http://foo | tar xvf - )
with. That's tedious, and not quite ideal.
linux tails
When using tails linux, I am having difficult configuring persistent storage. I run a VMWare VM, and boot off the tails iso, and I have a vmdk configured as attached to the machine. The vmdk volume is formatted ext3 and lives at /dev/sda5p1
. I'd like to use it to store things like public keys and email addresses so that I don't have to go pull them down every time I fire up the machine again. However, I cannot update the fstab on the iso, and when I go to Applications > System Tools > Configure Persistent Storage, the app complains that I don't have any usb media attached. The vmdk is scsi, of course.
Is there a way to configure tails with a persistent device? Yes, I am aware that tails is amnesiac, but I'd just like a way to store non-sensitive data so that I'm not starting up "stateless" every time.
The only workaround I've been able to think of is to have a tarball at an easily-typed/remembered url I can (cd /tmp; wget -qO - http://foo | tar xvf - )
with. That's tedious, and not quite ideal.
linux tails
linux tails
edited May 1 '14 at 12:46
Kev
70921129
70921129
asked Nov 4 '13 at 20:57
user269444
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
Tails is a Debian Linux, with Tor and several configurations and system checks to ensure your privacy.
It's designed for this goal and every piece of software is built with that in mind; if you want a persistence layer, you should do it as Tails wants you to do, as pointed by Jane.
As you want a custom install/version, you can install and configure Debian in a similar way, applying only restrictions/scripts that you want from Tails. It will be easier to archive what you want.
What most users need from tails is the network isolation, a whole system that don't leave traces and the "send everything through Tor" configurations. Map what you need and install it on Debian, borrow some configuration scripts and read how some features should work.
I strongly suggest that even running your new Debian Tails-flavoured Linux in a VM, you keep encrypting your disk with luks.
add a comment |
Full disclosure: I asked this question over at SO and was directed here; I am not trying to reputation-monster on purpose.
So looking over the Tails design doc, we see that:
- error out if not running from USB
- error out unless Tails was installed using Tails Installer (i.e. unless it's running from a GPT partition labeled Tails)
- error out if the device Tails is running from already has a persistent volume
It would thus seem that, as the current design of Tails stands, it is not possible to use a scsi device as any kind of persistent storage. Honestly, I'm not sure what the advantage of USB over SCSI in this case is, as the user is allowed to be as braindead as they like with their volumes and persistent data, but that is the way Tails is, and the decision is out of my hands. :(
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f669547%2fconfiguring-persistent-storage-on-tails-linux%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Tails is a Debian Linux, with Tor and several configurations and system checks to ensure your privacy.
It's designed for this goal and every piece of software is built with that in mind; if you want a persistence layer, you should do it as Tails wants you to do, as pointed by Jane.
As you want a custom install/version, you can install and configure Debian in a similar way, applying only restrictions/scripts that you want from Tails. It will be easier to archive what you want.
What most users need from tails is the network isolation, a whole system that don't leave traces and the "send everything through Tor" configurations. Map what you need and install it on Debian, borrow some configuration scripts and read how some features should work.
I strongly suggest that even running your new Debian Tails-flavoured Linux in a VM, you keep encrypting your disk with luks.
add a comment |
Tails is a Debian Linux, with Tor and several configurations and system checks to ensure your privacy.
It's designed for this goal and every piece of software is built with that in mind; if you want a persistence layer, you should do it as Tails wants you to do, as pointed by Jane.
As you want a custom install/version, you can install and configure Debian in a similar way, applying only restrictions/scripts that you want from Tails. It will be easier to archive what you want.
What most users need from tails is the network isolation, a whole system that don't leave traces and the "send everything through Tor" configurations. Map what you need and install it on Debian, borrow some configuration scripts and read how some features should work.
I strongly suggest that even running your new Debian Tails-flavoured Linux in a VM, you keep encrypting your disk with luks.
add a comment |
Tails is a Debian Linux, with Tor and several configurations and system checks to ensure your privacy.
It's designed for this goal and every piece of software is built with that in mind; if you want a persistence layer, you should do it as Tails wants you to do, as pointed by Jane.
As you want a custom install/version, you can install and configure Debian in a similar way, applying only restrictions/scripts that you want from Tails. It will be easier to archive what you want.
What most users need from tails is the network isolation, a whole system that don't leave traces and the "send everything through Tor" configurations. Map what you need and install it on Debian, borrow some configuration scripts and read how some features should work.
I strongly suggest that even running your new Debian Tails-flavoured Linux in a VM, you keep encrypting your disk with luks.
Tails is a Debian Linux, with Tor and several configurations and system checks to ensure your privacy.
It's designed for this goal and every piece of software is built with that in mind; if you want a persistence layer, you should do it as Tails wants you to do, as pointed by Jane.
As you want a custom install/version, you can install and configure Debian in a similar way, applying only restrictions/scripts that you want from Tails. It will be easier to archive what you want.
What most users need from tails is the network isolation, a whole system that don't leave traces and the "send everything through Tor" configurations. Map what you need and install it on Debian, borrow some configuration scripts and read how some features should work.
I strongly suggest that even running your new Debian Tails-flavoured Linux in a VM, you keep encrypting your disk with luks.
edited Sep 21 '16 at 8:10
Toby Speight
3,6061532
3,6061532
answered Sep 20 '16 at 19:05
OPSXCQOPSXCQ
1891
1891
add a comment |
add a comment |
Full disclosure: I asked this question over at SO and was directed here; I am not trying to reputation-monster on purpose.
So looking over the Tails design doc, we see that:
- error out if not running from USB
- error out unless Tails was installed using Tails Installer (i.e. unless it's running from a GPT partition labeled Tails)
- error out if the device Tails is running from already has a persistent volume
It would thus seem that, as the current design of Tails stands, it is not possible to use a scsi device as any kind of persistent storage. Honestly, I'm not sure what the advantage of USB over SCSI in this case is, as the user is allowed to be as braindead as they like with their volumes and persistent data, but that is the way Tails is, and the decision is out of my hands. :(
add a comment |
Full disclosure: I asked this question over at SO and was directed here; I am not trying to reputation-monster on purpose.
So looking over the Tails design doc, we see that:
- error out if not running from USB
- error out unless Tails was installed using Tails Installer (i.e. unless it's running from a GPT partition labeled Tails)
- error out if the device Tails is running from already has a persistent volume
It would thus seem that, as the current design of Tails stands, it is not possible to use a scsi device as any kind of persistent storage. Honestly, I'm not sure what the advantage of USB over SCSI in this case is, as the user is allowed to be as braindead as they like with their volumes and persistent data, but that is the way Tails is, and the decision is out of my hands. :(
add a comment |
Full disclosure: I asked this question over at SO and was directed here; I am not trying to reputation-monster on purpose.
So looking over the Tails design doc, we see that:
- error out if not running from USB
- error out unless Tails was installed using Tails Installer (i.e. unless it's running from a GPT partition labeled Tails)
- error out if the device Tails is running from already has a persistent volume
It would thus seem that, as the current design of Tails stands, it is not possible to use a scsi device as any kind of persistent storage. Honestly, I'm not sure what the advantage of USB over SCSI in this case is, as the user is allowed to be as braindead as they like with their volumes and persistent data, but that is the way Tails is, and the decision is out of my hands. :(
Full disclosure: I asked this question over at SO and was directed here; I am not trying to reputation-monster on purpose.
So looking over the Tails design doc, we see that:
- error out if not running from USB
- error out unless Tails was installed using Tails Installer (i.e. unless it's running from a GPT partition labeled Tails)
- error out if the device Tails is running from already has a persistent volume
It would thus seem that, as the current design of Tails stands, it is not possible to use a scsi device as any kind of persistent storage. Honestly, I'm not sure what the advantage of USB over SCSI in this case is, as the user is allowed to be as braindead as they like with their volumes and persistent data, but that is the way Tails is, and the decision is out of my hands. :(
edited Apr 1 '17 at 1:39
Pimp Juice IT
23.5k113970
23.5k113970
answered Nov 7 '13 at 18:25
Jane ArcJane Arc
1013
1013
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f669547%2fconfiguring-persistent-storage-on-tails-linux%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown