mirror of
http://git.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/nihilist/blog-contributions.git
synced 2025-07-02 11:56:40 +00:00
anonproxy + sensitive vm finish
This commit is contained in:
nihilist
parent
d8f1c456ac
commit
0e8b0fcc59
23 changed files with 251 additions and 25 deletions
|
|
@ -70,13 +70,12 @@
|
|||
<p><h2><u>OPSEC Recommendations:</u></h2></p>
|
||||
<ol>
|
||||
<li><p>Hardware : (Personal Computer / Laptop)</p></li>
|
||||
<li><p>Host OS: <a href="../linux/index.html">Linux</a></p></li>
|
||||
<li><p>Host OS: <a href="../linux/index.html">Linux</a>, but in <a href="../livemode/index.html">live mode</a></p></li>
|
||||
<li><p>Hypervisor: <a href="../hypervisorsetup/index.html">libvirtd QEMU/KVM</a></p></li>
|
||||
<li><p>Harddrive (HDD): 500GB and encrypted with <a href="../veracrypt/index.html">Veracrypt (with a 250Gb Hidden Volume)</a></p></li>
|
||||
<li><p>Virtual Machine:<a href="../whonixqemuvms/index.html">Whonix</a></p></li>
|
||||
</ol>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</div><!-- /row -->
|
||||
</div> <!-- /container -->
|
||||
</div><!-- /grey -->
|
||||
|
|
@ -86,8 +85,26 @@
|
|||
<div class="container">
|
||||
<div class="row">
|
||||
<div class="col-lg-8 col-lg-offset-2">
|
||||
<h2><b>How to setup the VMs inside the Veracrypt volumes</b></h2> </br> </br>
|
||||
<p>First, we're going to setup our veracrypt volumes on our 500Gb harddrive:</p>
|
||||
<h2><b>Deniability Requirement</b></h2> </br> </br>
|
||||
<p>First of all as you have seen, the requirement is that we do this setup from the Host OS, in <a href="../livemode/index.html">live mode</a>. That is because we want to make sure that there is no forensic evidence to be saved on the system drive as we have explained <a href="../livemode/index.html">previously.</a> </p>
|
||||
|
||||
<img src="../livemode/4.png" class="imgRz">
|
||||
<p>While in Live mode we can't write anything new on the system disk (such as the system logs, kernel logs, non-standard logs) <b>which can all be potential forensic evidence that the hidden volume exists</b>. Instead, everything is written into RAM, and we can easily erase all of those contents with a simple reboot. While in live mode however, we can write to non-system drives, which is where we will setup a big enough veracrypt volume to store the Whonix VMs that we will use for long-term sensitive use.</p>
|
||||
</div>
|
||||
</div><!-- /row -->
|
||||
</div> <!-- /container -->
|
||||
</div><!-- /grey -->
|
||||
|
||||
<!-- +++++ Second Post +++++ -->
|
||||
<div id="anon2">
|
||||
<div class="container">
|
||||
<div class="row">
|
||||
<div class="col-lg-8 col-lg-offset-2">
|
||||
<h2><b>How to setup the VMs inside the Hidden Volume</b></h2> </br> </br>
|
||||
<p>So before we start, make sure you reboot the Host OS to go into live mode:</p>
|
||||
<img src="../deniability/7.png" class="imgRz">
|
||||
|
||||
<p>Then, once in live mode we're going to setup our veracrypt volumes on our 500Gb harddrive:</p>
|
||||
<img src="2.png" class="imgRz">
|
||||
<img src="3.png" class="imgRz">
|
||||
<p>Here we're using a non-system drive, as we want to be able to store our veracrypt hidden volume contents in a persistent manner, accross reboots. (if we were to have the veracrypt volume on the system drive, it would be wiped off upon rebooting since the Host OS is in live mode.)</p>
|
||||
|
|
@ -119,7 +136,7 @@
|
|||
</div> <!-- /container -->
|
||||
</div><!-- /white -->
|
||||
|
||||
<div id="anon2">
|
||||
<div id="anon3">
|
||||
<div class="container">
|
||||
<div class="row">
|
||||
<div class="col-lg-8 col-lg-offset-2">
|
||||
|
|
@ -313,7 +330,7 @@ Network Whonix-Internal has been undefined
|
|||
</div> <!-- /container -->
|
||||
</div><!-- /white -->
|
||||
|
||||
<div id="anon1">
|
||||
<div id="anon2">
|
||||
<div class="container">
|
||||
<div class="row">
|
||||
<div class="col-lg-8 col-lg-offset-2">
|
||||
|
|
@ -373,12 +390,12 @@ kill -9 $(pidof vlc)
|
|||
</div> <!-- /container -->
|
||||
</div><!-- /white -->
|
||||
|
||||
<div id="anon2">
|
||||
<div id="anon3">
|
||||
<div class="container">
|
||||
<div class="row">
|
||||
<div class="col-lg-8 col-lg-offset-2">
|
||||
<h2><b>Emergency shutdown script setup</b></h2> </br> </br>
|
||||
<p>Now that we're done setting up both the hidden and the decoy volumes, we're going to setup the script that will launch either of the 2 script.sh scripts we just wrote, on top of also erasing all potential proof that the sensitive VM exists (meaning we erase all logs, all kernel logs, we fill the ram with random content 3 times, and we erase the command history): </p>
|
||||
<h2><b>Emergency shutdown shortcut</b></h2> </br> </br>
|
||||
<!--<p>Now that we're done setting up both the hidden and the decoy volumes, we're going to setup the script that will launch either of the 2 script.sh scripts we just wrote, on top of also erasing all potential proof that the sensitive VM exists (meaning we erase all logs, all kernel logs, we fill the ram with random content 3 times, and we erase the command history): </p>
|
||||
<p>First we need to make sure we can run veracrypt commands without requiring to be a sudo user:</p>
|
||||
<pre><code class="nim">
|
||||
[ nowhere ] [ /dev/pts/1 ] [/mnt]
|
||||
|
|
@ -514,15 +531,15 @@ stress -m 1 --vm-bytes $(free -ght | grep Mem | cut -d ' ' -f 12 | cut -d 'G' -f
|
|||
[ nowhere ] [ /dev/pts/1 ] [~]
|
||||
→ chmod +x wipe.sh
|
||||
|
||||
</pre></code>
|
||||
</pre></code>-->
|
||||
<p>Now that we're setup, we need to be able to run that script using a shortcut to be ran from our desktop environment, I am currently using Cinnamon, therefore to create a shortcut for cinnamon you do as follows:</p>
|
||||
<img src="30.png" class="imgRz">
|
||||
<img src="31.png" class="imgRz">
|
||||
<!--<img src="31.png" class="imgRz">
|
||||
<img src="32.png" class="imgRz">
|
||||
<p>So basically from here, if you are not in a QEMU VM, you simply need to hit the shortcut <b>"SUPER+R"</b>.</p>
|
||||
<p>If you are focused in a QEMU VM, you need to do <b>"CTRL+ALT"</b> (to focus out of the QEMU VM), and then <b>"SUPER+R"</b> to run the wipe.sh script from the Host OS.</p>
|
||||
<p>If you are focused in a QEMU VM, you need to do <b>"Ctrl+Alt"</b> (to focus out of the QEMU VM), and then <b>"SUPER+R"</b> to run the wipe.sh script from the Host OS.</p>-->
|
||||
<img src="37.png" class="imgRz">
|
||||
<p>Now i'm also going to setup an optional shortcut <b>"Super+V"</b> to only run the /mnt/veracrypt1/script.sh script just so it is easier to setup the whonix VMs when inside the veracrypt hidden volume.</p>
|
||||
<p>Now we're setting up the shortcut <b>"Super+V"</b> to run the <b>/mnt/veracrypt1/script.sh</b> script just so it is quicker to setup the whonix VMs when inside the veracrypt hidden volume. Now to shut down the Host OS, there is already a default cinnamon shortcut which is <b>"Ctrl+Alt+End"</b>.</p>
|
||||
<img src="36.png" class="imgRz">
|
||||
<p>And we're now all setup! So let's try it out in both scenarios (from the decoy volume, and from the hidden volume):</p>
|
||||
</div>
|
||||
|
|
@ -543,19 +560,19 @@ stress -m 1 --vm-bytes $(free -ght | grep Mem | cut -d ' ' -f 12 | cut -d 'G' -f
|
|||
<p>Then we open VLC, and we hit "Open file" and browse to our non-sensitive files:</p>
|
||||
<img src="33.png" class="imgRz">
|
||||
<img src="34.png" class="imgRz">
|
||||
<p>Then suddenly someone busts your front door, and you quickly press <b>"Super+R"</b>, the VLC window immediately closes, and in 4 seconds you have the Veracrypt volume unmounted and the veracrypt window closed. Meanwhile the wipe.sh script is doing the remaining cleaning up operations in the background, which it will complete under 30 seconds.</p>
|
||||
<p>Then suddenly someone busts your front door, and you quickly press <b>"Super+V"</b> the VLC window immediately closes, and then <b>"Ctrl+Alt+End"</b> and in a few seconds you have the Host OS shutting down. And as the Host OS shuts down, all the RAM contents are erased (even though there was nothing sensitive in it this time).</p>
|
||||
<img src="" class="imgRz">
|
||||
<p>And that's it ! if the adversary didnt get to your desk by the time you pressed the shortcut, he didnt get to see the content you were playing on your monitor. </p>
|
||||
|
||||
<h2><b>Hidden Volume Scenario (using the sensitive VM)</b></h2>
|
||||
<p></p>
|
||||
<p>Now to test emergency shutdown on the hidden volume side, we first open the hidden volume:</p>
|
||||
<img src="23.png" class="imgRz">
|
||||
<img src="24.png" class="imgRz">
|
||||
<p>Once the hidden volume is mounted, we hit <b>"Super+V"</b> to quickly setup the whonix VMs:</p>
|
||||
<img src="38.png" class="imgRz">
|
||||
<p>And after a while of doing some actual sensitive stuff on the whonix VM you hear your front door being busted down, so you quickly hit <b>"CTRL+ALT"</b> to focus out of the VM, and then you hit <b>"Super+R"</b> to trigger the emergency shutdown procedure:</p>
|
||||
<p>And after a while of doing some actual sensitive stuff on the whonix VM you hear your front door being busted down, so you quickly hit <b>"Ctrl+Alt"</b> to focus out of the VM, and then you hit <b>"Ctrl+Alt+End"</b> to trigger the emergency shutdown:</p>
|
||||
<img src="39.png" class="imgRz">
|
||||
<p>Here it also only takes 4 seconds after pressing <b>"Super+R"</b> to have your whonix VMs shutdown, and the veracrypt hidden volume closed, with the veracrypt window closed. And in the background, the script doing the remaining cleaning steps which will take 30 seconds to complete.</p>
|
||||
<p>Here it also only takes approximately 4 seconds after pressing <b>"Ctrl+Alt+End"</b> to have your Host OS shutdown, erasing all the forensic evidence regarding the existence of the veracrypt hidden volume and the Sensitive Whonix VM it contains.</p>
|
||||
<p>And that's it ! You now have a Sensitive VM ready to be used, and you have implemented the necessary measures to protect the deniability of it's existance, from an adversary.</p>
|
||||
</div>
|
||||
</div><!-- /row -->
|
||||
|
|
@ -569,7 +586,9 @@ stress -m 1 --vm-bytes $(free -ght | grep Mem | cut -d ' ' -f 12 | cut -d 'G' -f
|
|||
<div class="row">
|
||||
<div class="col-lg-8 col-lg-offset-2">
|
||||
<h2><b>In what context is there Deniability ?</b></h2>
|
||||
<p>With this setup, you have deniability the moment that the script finishes running, regarding the existance of the veracrypt hidden volume, and the whonix sensitive VMs. <b>Meaning that it is impossible for an adversary that seizes your computer to prove the existance of the Whonix Sensitive VMs after the wipe.sh script finished running.</b></p>
|
||||
<p>With this setup, you have deniability the moment that the script finishes running, regarding the existance of the veracrypt hidden volume, and the whonix sensitive VMs. <b>Meaning that it is impossible for an adversary that seizes your computer to prove the existance of the Whonix Sensitive VMs after shutting down the Host OS.</b></p>
|
||||
<p>Below is all an adversary will be able to see, if he were to seize your laptop after you manage to shut it down:</p>
|
||||
<img src="40.png" class="imgRz">
|
||||
<p>Of course, if you are ever forced to, <b>ONLY give your decoy password to the adversary.</b> The existance of the hidden volume, and of the secret password thats used to reveal it must remain a secret at all costs, it must remain known only by you.</p>
|
||||
<p>If you are ever dragged into court, <b>the judge will appreciate much more if you actually hand over your laptop, and show that you are willing to cooperate with the authorities by providing your password to unlock it</b>, rather than starting to pretend you forgot your password (which can end badly like in <a href="https://lawblog.legalmatch.com/2018/07/23/florida-man-jailed-allegedly-forgetting-password-on-cell-phones/">this court case</a>, where the defendant was found to be in contempt of court, and thrown in jail for 6 months for it). </p>
|
||||
<p>If ever asked by the authorities on why you used veracrypt in your laptop, you can simply claim that it was to put your stash of adult content in it. Nothing incriminating about it, and it is plausible given that you dont want that laying around on your desktop, due to being of a private matter.</p>
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue