Plausible deniability in hacking and crypytography 10-03-2012, 07:49 PM
#1
Here I'm going to describe certain techniques and concepts related to plausibly denying involvement in hacking and existence or importance of cryptographic materials.
Plausible deniability in hacking
If you get accused of illegal activities related to hacking, there are some ways to bullshit yourself out of trouble. Some of more useful are:
Emergency virus pack - get yourself a DVD or USB or something filled with spyware servers, trojans, keyloggers and all the fun stuff. Yes, I mean the ones that infect you, no the ones that control the malware. In case of emergency, run them on your system. As many of those program allow to launch attacks from your computer, you have a nice 'I'm the victim here' defense ready.
Wardrivability - if you use a Wi-Fi router, turn logs off. Then either turn the security off or set it to something easily hackable like WEP (preferably with a weak password). This gives you a similar defence as you may pretend that someone broken into your network but you have no logs to prove it.
Wardrivability ++ -do the same thing as in the previous one but don't turn off logs, just delete those that incriminate you. Borrow a laptop/use a spare one, spoof MAC in it and 'break' into your own network. Do suspicious shit, especially accessing hacking-related websites and then watch your pursuer chase a hacker that doesn't exist.
Fake computer illiteracy - as an addition to any (or both) of those attacks, you may try to pretend to be really bad with computers. Backup all your data that may prove otherwise, store on removable media, place Eraser (or sth like that) on removable media and use it to securely wipe this stuff from your computer. Hide the storage media. Stop visiting security/tech/hacking/nerd sites for some time, stick to facebook and other mainstream sites, maybe gaming. For additional points use Internet Explorer with at least 2 toolbars installed. This one of course won't work if you have a known job or education related to computers.
Plausible deniability in cryptography
Multiple-meaning primitive ciphers/codes - if you communicate using primitive, non-mathematical ciphers (word replacements, acronyms, symbols), be sure to create plausible alternate meanings for them.
Encrypted files pretending to be malfromed data - this is especially good for TrueCrypt containers. As they can have any format, you can make them look as any kind of file, assuming that this file is broken and unreadable. Example: get a season of a TV show on HDD, delete a random episode, make a TrueCrypt container the size of one episode, give it an appropriate name and place it in an appropriate catalog.
Hidden container 1: I just store passwords - make a password database (i.e. with KeePass). Make a small container with a hidden/nested container inside it. Place a database in the outer one and more secret things in the inner.
Hidden container 2: The bad hides the worse - sometimes you need to hide something large in size that nobody can find (maybe a big database you've hacked and downloaded, maybe some super secret leaks). You can use similar approach: make a big container with other one hidden/nested. Unfortunately, you need an outer container filled with some big files that you'd plausibly want to hide. Your best bet here is a lot of random porn, second call would be warez.
Hidden container 3: Good secrets hide the bad secrets - this is quite specific. Basically, if you work on any kind of secret or confidential data (might be something as mundane as unreleased version of software if you work in software development, for example), you can use it just the way you'd use passwords/porn/warez in previous examples. This is very good as it's very plausible.
Plausibly hiding files inside files - I'm sure you're familiar with techniques of merging files together without binding them. Doing it plausibly is simply the case of filesizes. Your best bet is hiding small things in pictures and music files while hiding larger ones in video. Bonus points if music and video are VBR so the correct size of unmerged file will be harder to calculate.
Plausible deniability in hacking
If you get accused of illegal activities related to hacking, there are some ways to bullshit yourself out of trouble. Some of more useful are:
Emergency virus pack - get yourself a DVD or USB or something filled with spyware servers, trojans, keyloggers and all the fun stuff. Yes, I mean the ones that infect you, no the ones that control the malware. In case of emergency, run them on your system. As many of those program allow to launch attacks from your computer, you have a nice 'I'm the victim here' defense ready.
Wardrivability - if you use a Wi-Fi router, turn logs off. Then either turn the security off or set it to something easily hackable like WEP (preferably with a weak password). This gives you a similar defence as you may pretend that someone broken into your network but you have no logs to prove it.
Wardrivability ++ -do the same thing as in the previous one but don't turn off logs, just delete those that incriminate you. Borrow a laptop/use a spare one, spoof MAC in it and 'break' into your own network. Do suspicious shit, especially accessing hacking-related websites and then watch your pursuer chase a hacker that doesn't exist.
Fake computer illiteracy - as an addition to any (or both) of those attacks, you may try to pretend to be really bad with computers. Backup all your data that may prove otherwise, store on removable media, place Eraser (or sth like that) on removable media and use it to securely wipe this stuff from your computer. Hide the storage media. Stop visiting security/tech/hacking/nerd sites for some time, stick to facebook and other mainstream sites, maybe gaming. For additional points use Internet Explorer with at least 2 toolbars installed. This one of course won't work if you have a known job or education related to computers.
Plausible deniability in cryptography
Multiple-meaning primitive ciphers/codes - if you communicate using primitive, non-mathematical ciphers (word replacements, acronyms, symbols), be sure to create plausible alternate meanings for them.
Encrypted files pretending to be malfromed data - this is especially good for TrueCrypt containers. As they can have any format, you can make them look as any kind of file, assuming that this file is broken and unreadable. Example: get a season of a TV show on HDD, delete a random episode, make a TrueCrypt container the size of one episode, give it an appropriate name and place it in an appropriate catalog.
Hidden container 1: I just store passwords - make a password database (i.e. with KeePass). Make a small container with a hidden/nested container inside it. Place a database in the outer one and more secret things in the inner.
Hidden container 2: The bad hides the worse - sometimes you need to hide something large in size that nobody can find (maybe a big database you've hacked and downloaded, maybe some super secret leaks). You can use similar approach: make a big container with other one hidden/nested. Unfortunately, you need an outer container filled with some big files that you'd plausibly want to hide. Your best bet here is a lot of random porn, second call would be warez.
Hidden container 3: Good secrets hide the bad secrets - this is quite specific. Basically, if you work on any kind of secret or confidential data (might be something as mundane as unreleased version of software if you work in software development, for example), you can use it just the way you'd use passwords/porn/warez in previous examples. This is very good as it's very plausible.
Plausibly hiding files inside files - I'm sure you're familiar with techniques of merging files together without binding them. Doing it plausibly is simply the case of filesizes. Your best bet is hiding small things in pictures and music files while hiding larger ones in video. Bonus points if music and video are VBR so the correct size of unmerged file will be harder to calculate.


![[+]](https://sinister.li/images/modern/collapse_collapsed.png)