mirror of
http://git.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/nihilist/blog-contributions.git
synced 2025-07-02 07:26:41 +00:00
updated
This commit is contained in:
nihilist
parent
dfca945e1a
commit
c279c93453
4 changed files with 75 additions and 23 deletions
|
|
@ -86,6 +86,7 @@
|
|||
When discussing the topic of OPSEC, an important concept that inevitably arises is compartmentalization. Broadly speaking, compartmentalization can be defined as separating different activities into different buckets in order to prevent them from being linked together. This concept is perhaps most commonly seen using online emails. You may want one email for all of your social media, a different email for all of your online purchases and a different email still for all health related items. This same concept can be applied to your online chats. In this tutorial, we will explore the different types of chats, how to compartmentalize them based on their contexts and when each one is optimal to use.
|
||||
</p>
|
||||
|
||||
|
||||
</div>
|
||||
</div><!-- /row -->
|
||||
</div> <!-- /container -->
|
||||
|
|
@ -96,6 +97,21 @@ When discussing the topic of OPSEC, an important concept that inevitably arises
|
|||
<div class="container">
|
||||
<div class="row">
|
||||
<div class="col-lg-8 col-lg-offset-2">
|
||||
<h2><b>OPSEC Requirements in Chats</b></h2> </br> </br>
|
||||
|
||||
<p>Another thing to note is that there are a ton of chat apps out there, and as we have explained <a href="../opsec4levels/index.html">previously</a>, depending on the level of Operational Security you are aiming for (wether it is privacy, anonymity or deniability), <b>the tool has to meet certain criterias to be suitable for the intended use</b>.</p>
|
||||
<img src="../opsec4levels/0.1.png" class="imgRz">
|
||||
<p>As you're going to see shortly, depending on the types of chats you want to have, the chat platform you use is very much dependant on meeting the OPSEC requirements to match the intended uses.</p>
|
||||
</div>
|
||||
</div><!-- /row -->
|
||||
</div> <!-- /container -->
|
||||
</div><!-- /white -->
|
||||
|
||||
<!-- +++++ Third Post +++++ -->
|
||||
<div id="anon1">
|
||||
<div class="container">
|
||||
<div class="row">
|
||||
<div class="col-lg-8 col-lg-offset-2">
|
||||
<h2><b>Types of Chats</b></h2> </br> </br>
|
||||
|
||||
<p>
|
||||
|
|
@ -115,10 +131,10 @@ The chart below describes 4 different types of chats. They are separated by thei
|
|||
<table class="tg"><thead>
|
||||
<tr>
|
||||
<th class="tg-c3ow"></th>
|
||||
<th class="tg-9353">Public Chat</th>
|
||||
<th class="tg-9353">Private Chat</th>
|
||||
<th class="tg-9353">Anonymous Chat</th>
|
||||
<th class="tg-9353">Deniable Chat</th>
|
||||
<th class="tg-9353"><b>Public Chats</b></br><img src="../logos/su2.png"></th>
|
||||
<th class="tg-9353"><b>Private Chats</b></br><img src="../logos/su0.png"></th>
|
||||
<th class="tg-9353"><b>Anonymous Chats</b></br><img src="../logos/on0.png"></th>
|
||||
<th class="tg-9353"><b>Deniable Chats</b></br><img src="../logos/de0.png"></th>
|
||||
</tr></thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
|
|
@ -137,24 +153,24 @@ The chart below describes 4 different types of chats. They are separated by thei
|
|||
</tr>
|
||||
<tr>
|
||||
<td class="tg-9353">Technical Requirements (Online)</td>
|
||||
<td class="tg-0pky">-None. No E2EE required</td>
|
||||
<td class="tg-0pky">-E2EE is required</td>
|
||||
<td class="tg-0pky">-E2EE is required<br>-No user IDs, no IP address linkability<br></td>
|
||||
<td class="tg-0pky">-E2EE is required<br>-No user IDs, no IP address linkability<br>-Disappearing messages</td>
|
||||
<td class="tg-0pky">-None. <b>(everything you say is public knowledge)</b></td>
|
||||
<td class="tg-0pky"><b>-FOSS Software</b><br><b>-E2EE is required</b></br>-You can self-host the chat server yourself</br><center><img src="../logos/ce0.png"></center></td>
|
||||
<td class="tg-0pky">-FOSS Software<br>-E2EE is required<br><b>-Upon signup, requires no phone numbers, no user IDs, and no IP address linkability (using Tor)<br></b></td>
|
||||
<td class="tg-0pky">-FOSS Software<br>-E2EE is required<br>-Upon signup, requires no phone numbers, no user IDs, and no IP address linkability (using Tor)<br><b>-Disappearing messages</b></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td class="tg-9353">Pros</td>
|
||||
<td class="tg-0pky">-Easiest to achieve<br>-No restrictions<br>-Suitable for any environment</td>
|
||||
<td class="tg-0pky">-Contents of conversation are secure<br>-Many apps now implement E2EE</td>
|
||||
<td class="tg-0pky">-May assume different anonymous identities for different conversations<br>-Suitable for exploring controversial topics<br></td>
|
||||
<td class="tg-0pky">-Contents of the conversation are visible only by the participants<br>-Many apps now implement E2EE</td>
|
||||
<td class="tg-0pky">-May assume different anonymous identities for different conversations<br>-Suitable for exploring controversial topics<br><b>-Anonymity is possible in public chats too!</b></td>
|
||||
<td class="tg-0pky">-Off the record<br>-No history of the conversation<br>-Suitable for sensitive topics</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td class="tg-9353">Cons</td>
|
||||
<td class="tg-0pky">-Anything said can be linked to your real identity</td>
|
||||
<td class="tg-0pky">-May still be known the conversation took place<br>-May be able to build patterns based on conversations</td>
|
||||
<td class="tg-0pky">-Requires specialized software</td>
|
||||
<td class="tg-0pky">-Requires specialized software<br>-Requires specialized settings configuration</td>
|
||||
<td class="tg-0pky"><b>-very few chat apps are FOSS on both the clientside and the serverside</b></br>-The identity of the participants are known<br>-May still be known the conversation took place<br>-May be able to build patterns based on conversations</td>
|
||||
<td class="tg-0pky"><b>-even fewer chat apps can be used to sign up anonymously</b></br>-Deanonymization may happen based on what the anonymous party says</td>
|
||||
<td class="tg-0pky">-Can't read the history of the chat beyond the time limit<br></td>
|
||||
</tr>
|
||||
</tbody></table>
|
||||
|
||||
|
|
@ -176,14 +192,14 @@ As with many things, these chats exist on a spectrum between being more convenie
|
|||
</div><!-- /white -->
|
||||
|
||||
<!-- +++++ Fourth Post +++++ -->
|
||||
<div id="anon1">
|
||||
<div id="anon2">
|
||||
<div class="container">
|
||||
<div class="row">
|
||||
<div class="col-lg-8 col-lg-offset-2">
|
||||
<h2><b>Examples</b></h2> </br> </br>
|
||||
<h2><img src="../logos/su2.png"> <b>Public Chat Example</b></h2> </br> </br>
|
||||
|
||||
<p>
|
||||
Let's take a look at a few examples to illustrate these concepts. First up is a <b>public chat</b> similar to what you'd find online, on social media, in public chat rooms, etc.
|
||||
Let's take a look at a few examples to illustrate these concepts. First up is a <b>public chat</b> similar to what you'd find online, on social media, in public chat rooms, etc.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -194,8 +210,17 @@ Let's take a look at a few examples to illustrate these concepts. First up is a
|
|||
This conversation, tied to Alice and Bob's real identities, is visible for anyone to see. Public chats such as this one pose the smallest barrier to entry as they can take place anytime/anywhere. Any information discussed, such as their plans together next weekend and mode of transportation, are now publicly known by anyone present at the time of the conversation. Alice and Bob may openly show their support for their favorite football teams, but what if there was some information they didn't want others to know?
|
||||
</p>
|
||||
|
||||
<br>
|
||||
<br>
|
||||
</div>
|
||||
</div><!-- /row -->
|
||||
</div> <!-- /container -->
|
||||
</div><!-- /white -->
|
||||
|
||||
<!-- +++++ Fourth Post +++++ -->
|
||||
<div id="anon1">
|
||||
<div class="container">
|
||||
<div class="row">
|
||||
<div class="col-lg-8 col-lg-offset-2">
|
||||
<h2><img src="../logos/su0.png"> <b>Private Chat Example</b></h2> </br> </br>
|
||||
|
||||
<p>
|
||||
For discussions involving information that is not necessarily meant for everyone to know about, we have <b>private chats</b>. In private chats, participants may still use their real identities, but the key differences is that the information is only accessible between the parties chatting and nobody else as the conversation is End-to-End Encrypted (E2EE).
|
||||
|
|
@ -209,9 +234,18 @@ For discussions involving information that is not necessarily meant for everyone
|
|||
Alice may be uncomfortable announcing to the world she's short on cash at the moment, but can confide in her friend Bob with this information. In this private chat, only Alice and Bob know what was discussed and a record of this conversation exists. Luckily many popular chat apps are starting to implement E2EE, but without also including metadata protections, patterns can still be gleaned based on which contacts you are talking to and how often. But there may be situations where someone may not want you to know who they are when they're speaking with you. What happens in that situation?
|
||||
</p>
|
||||
|
||||
<br>
|
||||
<br>
|
||||
</div>
|
||||
</div><!-- /row -->
|
||||
</div> <!-- /container -->
|
||||
</div><!-- /white -->
|
||||
|
||||
<!-- +++++ Fourth Post +++++ -->
|
||||
<div id="anon2">
|
||||
<div class="container">
|
||||
<div class="row">
|
||||
<div class="col-lg-8 col-lg-offset-2">
|
||||
|
||||
<h2><img src="../logos/on0.png"> <b>Anonymous Chat Example</b></h2> </br> </br>
|
||||
<p>
|
||||
For discussions where one participant (or multiple participants) don't want the conversation tied in any way to their real identity, we have <b>anonymous chats</b>. With increasing OPSEC requirements comes the need for more specialized software, which may be more inconvenient for certain people.
|
||||
</p>
|
||||
|
|
@ -224,9 +258,18 @@ For discussions where one participant (or multiple participants) don't want the
|
|||
In this example, Alice is speaking with someone who doesn't want to have their persona tied to their real identity (the participant is using an incognito profile). The nature of the conversation may include controversial topics such as insider information. To achieve an anonymous chat, there must specifically be no user identifiers and no IP address linkability. An added benefit of having no user identifies is that a person can create disposable personas on the fly and use a different anonymous identity for each new conversation. But what if we need to communicate and can leave no trace of the conversation ever having taken place?
|
||||
</p>
|
||||
|
||||
<br>
|
||||
<br>
|
||||
</div>
|
||||
</div><!-- /row -->
|
||||
</div> <!-- /container -->
|
||||
</div><!-- /white -->
|
||||
|
||||
<!-- +++++ Fourth Post +++++ -->
|
||||
<div id="anon1">
|
||||
<div class="container">
|
||||
<div class="row">
|
||||
<div class="col-lg-8 col-lg-offset-2">
|
||||
|
||||
<h2><img src="../logos/de0.png"> <b>Deniable Chat Example</b></h2> </br> </br>
|
||||
<p>
|
||||
For the next step up, <b>deniable chats</b>, we must build on everything we've discussed up to and further employ disappearing messages. This is the only chat type suitable for discussing sensitive topics.
|
||||
</p>
|
||||
|
|
|
|||
|
|
@ -87,7 +87,7 @@
|
|||
<li><a href="http://git.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/nihilist/blog-contributions/issues/71">✅</a><a href="internetsegmentation/index.html"> Internet usage segmentation (QEMU VMs + Identity Management)</a><img src="logos/kvm.png" class="logo"><img src="logos/su2.png" class="logo"><img src="logos/su0.png" class="logo"><img src="logos/on0.png" class="logo"><img src="logos/de0.png" class="logo"></li>
|
||||
<li><a href="http://git.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/nihilist/blog-contributions/issues/72">✅</a><a href="opsec/index.html"> OPSEC: Using the right Technology and Behavior </a><img src="logos/su2.png" class="logo"><img src="logos/su0.png" class="logo"><img src="logos/on0.png" class="logo"><img src="logos/de0.png" class="logo"></li>
|
||||
<li><a href="http://git.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/nihilist/blog-contributions/issues/56">✅</a><a href="multiple_identities/index.html"> How to maintain multiple Identities Online</a><img src="logos/on0.png" class="logo"></li>
|
||||
<li><a href="http://git.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/nihilist/blog-contributions/issues/232">❌ Public Chats / Private Chats / Anonymous Chats / Deniable Chats</a></li>
|
||||
<li><a href="http://git.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/nihilist/blog-contributions/issues/232">✅</a><a href="chats/index.html"> Public Chats / Private Chats / Anonymous Chats / Deniable Chats</a></li>
|
||||
<li><a href="http://git.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/nihilist/blog-contributions/issues/241">❌ 10 Things you must do if you are pro-freedom</a></li>
|
||||
|
||||
</ol></br>
|
||||
|
|
|
|||
|
|
@ -9,6 +9,14 @@
|
|||
<description>Nihilist`s Technical Blog</description>
|
||||
<atom:link href='https://blog.nihilism.network/rss/feed.xml' rel='self' type='application/rss+xml' />
|
||||
|
||||
<item>
|
||||
<title>Public Chats / Private Chats / Anonymous Chats / Deniable Chats</title>
|
||||
<link>http://blog.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/opsec/chats/index.html</link>
|
||||
<guid isPermaLink='false'>2025041600</guid>
|
||||
<description>In this tutorial we're going to differentiate all 4 types of Chats, being the public, private, anonymous and deniable chats, and briefly showcase how simpleX fits all of our needs.</description>
|
||||
</item>
|
||||
|
||||
|
||||
<item>
|
||||
<title>How to Verify One's Identity While Maintaining Anonymity Using PGP Canaries</title>
|
||||
<link>http://blog.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/opsec/pgpcanary/index.html</link>
|
||||
|
|
@ -955,6 +963,7 @@
|
|||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
</channel>
|
||||
|
|
|
|||
0
sed.sh
Executable file → Normal file
0
sed.sh
Executable file → Normal file
Loading…
Add table
Add a link
Reference in a new issue