Do I have to dismount VeraCrypt volumes before shutting down or restarting Ubuntu?
Is there an auto-dismount in veracrypt or should I always unmount veracrypt volumes manually before shutting down to prevent a broken filesystem/container?
I found the answer for Windows in the veracrypt FAQ, but not for Linux / Ubuntu.
mount shutdown veracrypt
add a comment |
Is there an auto-dismount in veracrypt or should I always unmount veracrypt volumes manually before shutting down to prevent a broken filesystem/container?
I found the answer for Windows in the veracrypt FAQ, but not for Linux / Ubuntu.
mount shutdown veracrypt
It was necessary for truecrypt: wiki.archlinux.org/…
– Tim
Jun 4 '17 at 5:47
1
FYI: VeraCrypt's official FAQ as it is no longer maintained on CodePlex
– Damian
Jul 16 at 15:37
add a comment |
Is there an auto-dismount in veracrypt or should I always unmount veracrypt volumes manually before shutting down to prevent a broken filesystem/container?
I found the answer for Windows in the veracrypt FAQ, but not for Linux / Ubuntu.
mount shutdown veracrypt
Is there an auto-dismount in veracrypt or should I always unmount veracrypt volumes manually before shutting down to prevent a broken filesystem/container?
I found the answer for Windows in the veracrypt FAQ, but not for Linux / Ubuntu.
mount shutdown veracrypt
mount shutdown veracrypt
edited Jul 24 '17 at 13:58
karel
57k11127146
57k11127146
asked Jul 16 '16 at 9:57
oceanBT
1,014267
1,014267
It was necessary for truecrypt: wiki.archlinux.org/…
– Tim
Jun 4 '17 at 5:47
1
FYI: VeraCrypt's official FAQ as it is no longer maintained on CodePlex
– Damian
Jul 16 at 15:37
add a comment |
It was necessary for truecrypt: wiki.archlinux.org/…
– Tim
Jun 4 '17 at 5:47
1
FYI: VeraCrypt's official FAQ as it is no longer maintained on CodePlex
– Damian
Jul 16 at 15:37
It was necessary for truecrypt: wiki.archlinux.org/…
– Tim
Jun 4 '17 at 5:47
It was necessary for truecrypt: wiki.archlinux.org/…
– Tim
Jun 4 '17 at 5:47
1
1
FYI: VeraCrypt's official FAQ as it is no longer maintained on CodePlex
– Damian
Jul 16 at 15:37
FYI: VeraCrypt's official FAQ as it is no longer maintained on CodePlex
– Damian
Jul 16 at 15:37
add a comment |
3 Answers
3
active
oldest
votes
There are so-called run levels and script are executed when a new run level is entered. On Ubuntu, these are stored in /etc/rc<run level>.d
. Run level 0 is shutdown and run level 6 is reboot. So you want your script to be in /etc/rc0.d
and in /etc/rc6.d
.
Create the file /etc/init.d/unmount-veracrypt-volumes.sh
and make this its content:
#!/bin/sh
veracrypt -d -f
sleep 3
Then execute these commands:
sudo chown root /etc/init.d/unmount-veracrypt-volumes.sh
sudo chmod 751 /etc/init.d/unmount-veracrypt-volumes.sh
sudo ln -s /etc/init.d/unmount-veracrypt-volumes.sh /etc/rc0.d/K00-unmount-veracrypt-volumes.sh
sudo ln -s /etc/init.d/unmount-veracrypt-volumes.sh /etc/rc6.d/K00-unmount-veracrypt-volumes.sh
I chose K00
so the script is executed as the very first one when one of the run levels is entered. Those scripts are executed in increasing ASCII order, so the smaller the number of the symlink's name, the earlier a script is executed.
3
You have not clarified if this is necessary - does veracrypt not do this automatically ?
– Tim
Jun 4 '17 at 5:47
@Tim Oh, I didn't read the question very precisely. I'm sorry. I don't know that.
– UTF-8
Jun 4 '17 at 13:35
I realize that my answer doesn't provide an answer to the question asked but I feel like deleting it would harm people who come here to learn how to implement automatic dismounting after they decided they want to do it.
– UTF-8
Jun 5 '17 at 0:48
1
of course, leave it
– Tim
Jun 5 '17 at 8:47
Suggesting this instead of a systemd unit in 2017 is ... questionable.
– 0xC0000022L
Sep 10 at 19:42
|
show 1 more comment
As of March 2017, a user going by the name of Bob indicates that volumes are not automatically unmounted. It is probably a good idea to take UTF-8's advice and create the run level/init script.
I noticed a bad side effect from doing this. If I suspend, the storage is unmounted. I didn't want that. I never saw trouble in 5 years of using Truecrypt/Veracrypt without formally unmounting, I'll probably go back to that.
– pauljohn32
Dec 22 at 20:56
add a comment |
Here is an update, which should be the right answer!
I learned in the veracrypt forums that the option to control dismounting upon shutdown and/or suspend was introduced in version 1.19. There is no need to create the init.d scripts described above.
You can see this for yourself. I use the Ubuntu ppa provided a veracrypt package, in which there is a file called /etc/default/veracrypt
in which the following setings are included:
# If enabled, the following option calls 'veracrypt -d' at shutdown. Although
# all filesystems are unmounted automatically at shutdown, only calling
# 'veracrypt -d' will stop the VeraCrypt processes and remove any device mappings.
# It probably isn't necessary to do this, but it shouldn't hurt.
VERACRYPT_SHUTDOWN_UNMOUNT="yes"
# If enabled, the following option calls 'veracrypt -d' during suspend and hibernate.
VERACRYPT_SUSPEND_UNMOUNT="yes"
In case you want to try, here's the ppa file:
deb http://ppa.launchpad.net/unit193/encryption/ubuntu cosmic main
deb-src http://ppa.launchpad.net/unit193/encryption/ubuntu cosmic main
and the version as of 2018-12-26, veracrypt-1.23.0vanirl~18.10
.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
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%2faskubuntu.com%2fquestions%2f799277%2fdo-i-have-to-dismount-veracrypt-volumes-before-shutting-down-or-restarting-ubunt%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
There are so-called run levels and script are executed when a new run level is entered. On Ubuntu, these are stored in /etc/rc<run level>.d
. Run level 0 is shutdown and run level 6 is reboot. So you want your script to be in /etc/rc0.d
and in /etc/rc6.d
.
Create the file /etc/init.d/unmount-veracrypt-volumes.sh
and make this its content:
#!/bin/sh
veracrypt -d -f
sleep 3
Then execute these commands:
sudo chown root /etc/init.d/unmount-veracrypt-volumes.sh
sudo chmod 751 /etc/init.d/unmount-veracrypt-volumes.sh
sudo ln -s /etc/init.d/unmount-veracrypt-volumes.sh /etc/rc0.d/K00-unmount-veracrypt-volumes.sh
sudo ln -s /etc/init.d/unmount-veracrypt-volumes.sh /etc/rc6.d/K00-unmount-veracrypt-volumes.sh
I chose K00
so the script is executed as the very first one when one of the run levels is entered. Those scripts are executed in increasing ASCII order, so the smaller the number of the symlink's name, the earlier a script is executed.
3
You have not clarified if this is necessary - does veracrypt not do this automatically ?
– Tim
Jun 4 '17 at 5:47
@Tim Oh, I didn't read the question very precisely. I'm sorry. I don't know that.
– UTF-8
Jun 4 '17 at 13:35
I realize that my answer doesn't provide an answer to the question asked but I feel like deleting it would harm people who come here to learn how to implement automatic dismounting after they decided they want to do it.
– UTF-8
Jun 5 '17 at 0:48
1
of course, leave it
– Tim
Jun 5 '17 at 8:47
Suggesting this instead of a systemd unit in 2017 is ... questionable.
– 0xC0000022L
Sep 10 at 19:42
|
show 1 more comment
There are so-called run levels and script are executed when a new run level is entered. On Ubuntu, these are stored in /etc/rc<run level>.d
. Run level 0 is shutdown and run level 6 is reboot. So you want your script to be in /etc/rc0.d
and in /etc/rc6.d
.
Create the file /etc/init.d/unmount-veracrypt-volumes.sh
and make this its content:
#!/bin/sh
veracrypt -d -f
sleep 3
Then execute these commands:
sudo chown root /etc/init.d/unmount-veracrypt-volumes.sh
sudo chmod 751 /etc/init.d/unmount-veracrypt-volumes.sh
sudo ln -s /etc/init.d/unmount-veracrypt-volumes.sh /etc/rc0.d/K00-unmount-veracrypt-volumes.sh
sudo ln -s /etc/init.d/unmount-veracrypt-volumes.sh /etc/rc6.d/K00-unmount-veracrypt-volumes.sh
I chose K00
so the script is executed as the very first one when one of the run levels is entered. Those scripts are executed in increasing ASCII order, so the smaller the number of the symlink's name, the earlier a script is executed.
3
You have not clarified if this is necessary - does veracrypt not do this automatically ?
– Tim
Jun 4 '17 at 5:47
@Tim Oh, I didn't read the question very precisely. I'm sorry. I don't know that.
– UTF-8
Jun 4 '17 at 13:35
I realize that my answer doesn't provide an answer to the question asked but I feel like deleting it would harm people who come here to learn how to implement automatic dismounting after they decided they want to do it.
– UTF-8
Jun 5 '17 at 0:48
1
of course, leave it
– Tim
Jun 5 '17 at 8:47
Suggesting this instead of a systemd unit in 2017 is ... questionable.
– 0xC0000022L
Sep 10 at 19:42
|
show 1 more comment
There are so-called run levels and script are executed when a new run level is entered. On Ubuntu, these are stored in /etc/rc<run level>.d
. Run level 0 is shutdown and run level 6 is reboot. So you want your script to be in /etc/rc0.d
and in /etc/rc6.d
.
Create the file /etc/init.d/unmount-veracrypt-volumes.sh
and make this its content:
#!/bin/sh
veracrypt -d -f
sleep 3
Then execute these commands:
sudo chown root /etc/init.d/unmount-veracrypt-volumes.sh
sudo chmod 751 /etc/init.d/unmount-veracrypt-volumes.sh
sudo ln -s /etc/init.d/unmount-veracrypt-volumes.sh /etc/rc0.d/K00-unmount-veracrypt-volumes.sh
sudo ln -s /etc/init.d/unmount-veracrypt-volumes.sh /etc/rc6.d/K00-unmount-veracrypt-volumes.sh
I chose K00
so the script is executed as the very first one when one of the run levels is entered. Those scripts are executed in increasing ASCII order, so the smaller the number of the symlink's name, the earlier a script is executed.
There are so-called run levels and script are executed when a new run level is entered. On Ubuntu, these are stored in /etc/rc<run level>.d
. Run level 0 is shutdown and run level 6 is reboot. So you want your script to be in /etc/rc0.d
and in /etc/rc6.d
.
Create the file /etc/init.d/unmount-veracrypt-volumes.sh
and make this its content:
#!/bin/sh
veracrypt -d -f
sleep 3
Then execute these commands:
sudo chown root /etc/init.d/unmount-veracrypt-volumes.sh
sudo chmod 751 /etc/init.d/unmount-veracrypt-volumes.sh
sudo ln -s /etc/init.d/unmount-veracrypt-volumes.sh /etc/rc0.d/K00-unmount-veracrypt-volumes.sh
sudo ln -s /etc/init.d/unmount-veracrypt-volumes.sh /etc/rc6.d/K00-unmount-veracrypt-volumes.sh
I chose K00
so the script is executed as the very first one when one of the run levels is entered. Those scripts are executed in increasing ASCII order, so the smaller the number of the symlink's name, the earlier a script is executed.
edited Jun 4 '17 at 13:35
answered Jun 3 '17 at 21:20
UTF-8
3,63352049
3,63352049
3
You have not clarified if this is necessary - does veracrypt not do this automatically ?
– Tim
Jun 4 '17 at 5:47
@Tim Oh, I didn't read the question very precisely. I'm sorry. I don't know that.
– UTF-8
Jun 4 '17 at 13:35
I realize that my answer doesn't provide an answer to the question asked but I feel like deleting it would harm people who come here to learn how to implement automatic dismounting after they decided they want to do it.
– UTF-8
Jun 5 '17 at 0:48
1
of course, leave it
– Tim
Jun 5 '17 at 8:47
Suggesting this instead of a systemd unit in 2017 is ... questionable.
– 0xC0000022L
Sep 10 at 19:42
|
show 1 more comment
3
You have not clarified if this is necessary - does veracrypt not do this automatically ?
– Tim
Jun 4 '17 at 5:47
@Tim Oh, I didn't read the question very precisely. I'm sorry. I don't know that.
– UTF-8
Jun 4 '17 at 13:35
I realize that my answer doesn't provide an answer to the question asked but I feel like deleting it would harm people who come here to learn how to implement automatic dismounting after they decided they want to do it.
– UTF-8
Jun 5 '17 at 0:48
1
of course, leave it
– Tim
Jun 5 '17 at 8:47
Suggesting this instead of a systemd unit in 2017 is ... questionable.
– 0xC0000022L
Sep 10 at 19:42
3
3
You have not clarified if this is necessary - does veracrypt not do this automatically ?
– Tim
Jun 4 '17 at 5:47
You have not clarified if this is necessary - does veracrypt not do this automatically ?
– Tim
Jun 4 '17 at 5:47
@Tim Oh, I didn't read the question very precisely. I'm sorry. I don't know that.
– UTF-8
Jun 4 '17 at 13:35
@Tim Oh, I didn't read the question very precisely. I'm sorry. I don't know that.
– UTF-8
Jun 4 '17 at 13:35
I realize that my answer doesn't provide an answer to the question asked but I feel like deleting it would harm people who come here to learn how to implement automatic dismounting after they decided they want to do it.
– UTF-8
Jun 5 '17 at 0:48
I realize that my answer doesn't provide an answer to the question asked but I feel like deleting it would harm people who come here to learn how to implement automatic dismounting after they decided they want to do it.
– UTF-8
Jun 5 '17 at 0:48
1
1
of course, leave it
– Tim
Jun 5 '17 at 8:47
of course, leave it
– Tim
Jun 5 '17 at 8:47
Suggesting this instead of a systemd unit in 2017 is ... questionable.
– 0xC0000022L
Sep 10 at 19:42
Suggesting this instead of a systemd unit in 2017 is ... questionable.
– 0xC0000022L
Sep 10 at 19:42
|
show 1 more comment
As of March 2017, a user going by the name of Bob indicates that volumes are not automatically unmounted. It is probably a good idea to take UTF-8's advice and create the run level/init script.
I noticed a bad side effect from doing this. If I suspend, the storage is unmounted. I didn't want that. I never saw trouble in 5 years of using Truecrypt/Veracrypt without formally unmounting, I'll probably go back to that.
– pauljohn32
Dec 22 at 20:56
add a comment |
As of March 2017, a user going by the name of Bob indicates that volumes are not automatically unmounted. It is probably a good idea to take UTF-8's advice and create the run level/init script.
I noticed a bad side effect from doing this. If I suspend, the storage is unmounted. I didn't want that. I never saw trouble in 5 years of using Truecrypt/Veracrypt without formally unmounting, I'll probably go back to that.
– pauljohn32
Dec 22 at 20:56
add a comment |
As of March 2017, a user going by the name of Bob indicates that volumes are not automatically unmounted. It is probably a good idea to take UTF-8's advice and create the run level/init script.
As of March 2017, a user going by the name of Bob indicates that volumes are not automatically unmounted. It is probably a good idea to take UTF-8's advice and create the run level/init script.
edited Jun 7 '17 at 2:17
answered Jun 5 '17 at 5:43
b_laoshi
2,542927
2,542927
I noticed a bad side effect from doing this. If I suspend, the storage is unmounted. I didn't want that. I never saw trouble in 5 years of using Truecrypt/Veracrypt without formally unmounting, I'll probably go back to that.
– pauljohn32
Dec 22 at 20:56
add a comment |
I noticed a bad side effect from doing this. If I suspend, the storage is unmounted. I didn't want that. I never saw trouble in 5 years of using Truecrypt/Veracrypt without formally unmounting, I'll probably go back to that.
– pauljohn32
Dec 22 at 20:56
I noticed a bad side effect from doing this. If I suspend, the storage is unmounted. I didn't want that. I never saw trouble in 5 years of using Truecrypt/Veracrypt without formally unmounting, I'll probably go back to that.
– pauljohn32
Dec 22 at 20:56
I noticed a bad side effect from doing this. If I suspend, the storage is unmounted. I didn't want that. I never saw trouble in 5 years of using Truecrypt/Veracrypt without formally unmounting, I'll probably go back to that.
– pauljohn32
Dec 22 at 20:56
add a comment |
Here is an update, which should be the right answer!
I learned in the veracrypt forums that the option to control dismounting upon shutdown and/or suspend was introduced in version 1.19. There is no need to create the init.d scripts described above.
You can see this for yourself. I use the Ubuntu ppa provided a veracrypt package, in which there is a file called /etc/default/veracrypt
in which the following setings are included:
# If enabled, the following option calls 'veracrypt -d' at shutdown. Although
# all filesystems are unmounted automatically at shutdown, only calling
# 'veracrypt -d' will stop the VeraCrypt processes and remove any device mappings.
# It probably isn't necessary to do this, but it shouldn't hurt.
VERACRYPT_SHUTDOWN_UNMOUNT="yes"
# If enabled, the following option calls 'veracrypt -d' during suspend and hibernate.
VERACRYPT_SUSPEND_UNMOUNT="yes"
In case you want to try, here's the ppa file:
deb http://ppa.launchpad.net/unit193/encryption/ubuntu cosmic main
deb-src http://ppa.launchpad.net/unit193/encryption/ubuntu cosmic main
and the version as of 2018-12-26, veracrypt-1.23.0vanirl~18.10
.
add a comment |
Here is an update, which should be the right answer!
I learned in the veracrypt forums that the option to control dismounting upon shutdown and/or suspend was introduced in version 1.19. There is no need to create the init.d scripts described above.
You can see this for yourself. I use the Ubuntu ppa provided a veracrypt package, in which there is a file called /etc/default/veracrypt
in which the following setings are included:
# If enabled, the following option calls 'veracrypt -d' at shutdown. Although
# all filesystems are unmounted automatically at shutdown, only calling
# 'veracrypt -d' will stop the VeraCrypt processes and remove any device mappings.
# It probably isn't necessary to do this, but it shouldn't hurt.
VERACRYPT_SHUTDOWN_UNMOUNT="yes"
# If enabled, the following option calls 'veracrypt -d' during suspend and hibernate.
VERACRYPT_SUSPEND_UNMOUNT="yes"
In case you want to try, here's the ppa file:
deb http://ppa.launchpad.net/unit193/encryption/ubuntu cosmic main
deb-src http://ppa.launchpad.net/unit193/encryption/ubuntu cosmic main
and the version as of 2018-12-26, veracrypt-1.23.0vanirl~18.10
.
add a comment |
Here is an update, which should be the right answer!
I learned in the veracrypt forums that the option to control dismounting upon shutdown and/or suspend was introduced in version 1.19. There is no need to create the init.d scripts described above.
You can see this for yourself. I use the Ubuntu ppa provided a veracrypt package, in which there is a file called /etc/default/veracrypt
in which the following setings are included:
# If enabled, the following option calls 'veracrypt -d' at shutdown. Although
# all filesystems are unmounted automatically at shutdown, only calling
# 'veracrypt -d' will stop the VeraCrypt processes and remove any device mappings.
# It probably isn't necessary to do this, but it shouldn't hurt.
VERACRYPT_SHUTDOWN_UNMOUNT="yes"
# If enabled, the following option calls 'veracrypt -d' during suspend and hibernate.
VERACRYPT_SUSPEND_UNMOUNT="yes"
In case you want to try, here's the ppa file:
deb http://ppa.launchpad.net/unit193/encryption/ubuntu cosmic main
deb-src http://ppa.launchpad.net/unit193/encryption/ubuntu cosmic main
and the version as of 2018-12-26, veracrypt-1.23.0vanirl~18.10
.
Here is an update, which should be the right answer!
I learned in the veracrypt forums that the option to control dismounting upon shutdown and/or suspend was introduced in version 1.19. There is no need to create the init.d scripts described above.
You can see this for yourself. I use the Ubuntu ppa provided a veracrypt package, in which there is a file called /etc/default/veracrypt
in which the following setings are included:
# If enabled, the following option calls 'veracrypt -d' at shutdown. Although
# all filesystems are unmounted automatically at shutdown, only calling
# 'veracrypt -d' will stop the VeraCrypt processes and remove any device mappings.
# It probably isn't necessary to do this, but it shouldn't hurt.
VERACRYPT_SHUTDOWN_UNMOUNT="yes"
# If enabled, the following option calls 'veracrypt -d' during suspend and hibernate.
VERACRYPT_SUSPEND_UNMOUNT="yes"
In case you want to try, here's the ppa file:
deb http://ppa.launchpad.net/unit193/encryption/ubuntu cosmic main
deb-src http://ppa.launchpad.net/unit193/encryption/ubuntu cosmic main
and the version as of 2018-12-26, veracrypt-1.23.0vanirl~18.10
.
answered 2 days ago
pauljohn32
2,209822
2,209822
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- 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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2faskubuntu.com%2fquestions%2f799277%2fdo-i-have-to-dismount-veracrypt-volumes-before-shutting-down-or-restarting-ubunt%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
It was necessary for truecrypt: wiki.archlinux.org/…
– Tim
Jun 4 '17 at 5:47
1
FYI: VeraCrypt's official FAQ as it is no longer maintained on CodePlex
– Damian
Jul 16 at 15:37