Added content

This commit is contained in:
arcanedev 2021-08-11 22:27:23 +00:00
parent a89f4736f8
commit ac1ded4d37
No known key found for this signature in database
GPG Key ID: 13BA4BD4C14170C0
1 changed files with 4 additions and 3 deletions

View File

@ -277,7 +277,7 @@ Properly implemented cryptographic usage of keys provides a substantial barrier
For the justified paranoid, keep a hardware-based key or a separate USB/MicroSD for the sole purpose of key storage. Create hundreds of keys varying in bit length. Take mental note of the key (or keys) that you decide to use. Only connect designated key storage device into the system when the volume decryption is necessary.
Note:
Look into: OnlyKey, NitroKey, and SoloKey
Look into OnlyKey, NitroKey, and SoloKey
### Cryptographic Software
While we would love to maintain idealism and believe that we could write something that would retain relevance in perpetuity, we understand that this is not the nature of the technological system. To successfully orchestrate safe operations, I must address software-based cryptographic solutions.
@ -438,7 +438,7 @@ For instance, create a function for mounting your encrypted drive, closing out a
As previously noted, secure deletion is generally impossible on SSDs. Also, any bad sectors on a drive (SSD or HDD) cannot be securely erased by software. Such bad sectors must be erased physically.
Kali and Parrot include a LUKS "nuke" feature which erases the LUKS headers. This can be used to ensure an encrypted drive cannot be decrypted, even if your password can be broken. This feature can also be installed on any Linux-based OS. Installation of the LUKS nuke feature may conflict with Secure Boot on OSs which don't support it by default.
With the Bourne Again Shell (BASH) built into GNU/Linux systems, you can create simple functions that will perform these tasks. See Appendix A.
With the Bourne Again Shell (BASH) built into GNU/Linux systems, you can create simple functions that will perform these tasks. ([See Appendix A](#appendix-a)
Paste the text from Appendix A inside a text file > Rename the script to script.sh > Run "chmod +x script.sh" to make the script executable > Now all you must do is open a terminal and type "./script.sh" and do your will.
That wasn't so painful now, was it?
@ -564,9 +564,10 @@ For the hollow men (federal agents or contractors) who stumbled upon my work by
*"If ye love wealth better than liberty, the tranquility of servitude better than the animating contest of freedom, go home from us in peace. We ask not your counsels or arms. Crouch down and lick the hands which feed you. May your chains set lightly upon you, and may posterity forget that ye were our countrymen."* - Samuel Adams
## Appendix A: Cryptography Script
## Appendix A
```
#!/bin/bash
# Simple Cryptographic container script
function mount_partition() {
veracrypt -k </path/to/keyfile> --pim=<#> </path/to/mount/file/>
}