oxeo0/opsec-blogposts
1
0
Fork 0
mirror of http://git.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/nihilist/opsec-blogposts.git synced 2025-05-16 15:07:09 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

fix typos

Browse source
This commit is contained in:
nihilist 2025-05-15 08:40:31 +02:00
parent 9f05f656f1
commit e142601b4d
6 changed files with 9 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

2
veracrypt/index.md
View file

@ -62,7 +62,7 @@ So now you have zuluCrypt on your system. **However before you start to use it,
![](../livemode/3.png)
By default, your host OS directly writes into the system drive all sorts of potential forensic evidence that an adversary may use against you, such as system logs, kernel logs, non-standard logs, etc, and unless if you remove each of those manually, you're never sure of wether or not the Host OS saved proof of the existence of the hidden volume onto the system drive. **That's why when you use zulucrypt to handle veracrypt hidden volumes (creating them or opening them) you absolutely need to use the Host OS in[live mode](../livemode/index.md) ONLY! **
By default, your host OS directly writes into the system drive all sorts of potential forensic evidence that an adversary may use against you, such as system logs, kernel logs, non-standard logs, etc, and unless if you remove each of those manually, you're never sure of whether or not the Host OS saved proof of the existence of the hidden volume onto the system drive. **That's why when you use zulucrypt to handle veracrypt hidden volumes (creating them or opening them) you absolutely need to use the Host OS in[live mode](../livemode/index.md) ONLY! **
![](../livemode/4.png)