fix stuff

opsec/anonsimplex/index.html

@@ -417,7 +417,7 @@ REDACTED
 [TRANSPORT]
 # Host is only used to print server address on start.
 # You can specify multiple server ports.
-host: nowhere
+host: b6geeakpwskovltbesvy3b6ah3ewxfmnhnshojndmpp7wcv2df7bnead.onion
 #port: 5223,443 ## we dont need 443!
 port: 5223
 log_tls_errors: off
@@ -436,7 +436,7 @@ log_tls_errors: off
 # `host_mode` can be 'public' (default) or 'onion'.
 # It defines prefferred hostname for destination servers with multiple hostnames.
 host_mode: onion
-required_host_mode: on
+required_host_mode: off
 
 # The domain suffixes of the relays you operate (space-separated) to count as separate proxy statistics.
 # own_server_domains:

opsec/darknetlantern/index.html

@@ -136,10 +136,10 @@
 → torsocks git clone http://git.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/nihilist/darknet-lantern /srv/darknet-lantern
 
 </pre></code>
-<p>Install nginx and php8.2-fpm:</p>
+<p>Install nginx and php8.2-fpm, and php-gd for the new captcha feature:</p>
 <pre><code class="nim">
 [ Wonderland ] [ /dev/pts/23 ] [/srv/darknet-lantern]
-→ apt install php8.2-fpm nginx -y
+→ apt install php-gd php8.2-fpm nginx -y
 
 </pre></code>
 <p>use the nginx.conf and drop it in /etc/nginx/sites-available/</p>
@@ -760,6 +760,140 @@ lantern.nowhevi57f4lxxd6db43miewcsgtovakbh6v5f52ci7csc2yjzy5rnid.onion
 			</div><!-- /row -->
 	    </div> <!-- /container -->
 	</div><!-- /white -->
+  <!-- +++++ Second Post +++++ -->
+	<div id="anon2">
+	    <div class="container">
+			<div class="row">
+				<div class="col-lg-8 col-lg-offset-2">
+          <h2><b> How to recieve link submissions ?</b></h2> </br> </br>
+<p>Starting with Lantern version v1.1.0, your lantern instance can now recieve submissions from the visitors directly, you can access the submission page on the <b>/submit.php</b> url:</p>
+<img src="19.png" class="imgRz">
+<p>If you wish to recieve links from your audience, you just need to copy the template submission.csv file and edit the file rights of the submissions folder accordingly (as otherwise there will be a blank page when trying to submit the a new link):</p>
+<pre><code class="nim">
+[ Mainpc-PrivateVM-Debian12 ] [ /dev/pts/14 ] [/srv/darknet-lantern]
+→ cp templates/submission.csv submissions/submission.csv
+
+[ Wonderland ] [ /dev/pts/14 ] [/srv/darknet-lantern]
+→ chmod 777 -R /srv/darknet-lantern/submissions/
+
+#optional, use that following command if you are updating from the previous lantern version
+[ Wonderland ] [ /dev/pts/14 ] [/srv/darknet-lantern]
+→ git rm --cached /srv/darknet-lantern/submissions/submission.csv
+
+</pre></code>
+<p>From here, anyone can mention the new link to submit, the name of that link, the description, the category name, and whether or not the link is sensitive (related to drugs) or not. And lastly, to prevent spam, we also implemented a Captcha mechanism.</p>
+<img src="18.png" class="imgRz">
+<p>Once the link is correctly submitted, as a lantern admin you have to manually verify it (obviously there's no way we'd let strangers submit links that would be directly displayed on your own lantern instance without any manual verification whatsoever, let's be real, that would be too risky).</p>
+<p>Back on your lantern instance server, you can run lantern.py's new option 11) to review submissions:</p>
+<pre><code class="nim">
+[ Mainpc-PrivateVM-Debian12 ] [ /dev/pts/7 ] [/srv/darknet-lantern]
+→ python3 scripts/lantern.py
+
+[+] Instance Name: dawdawddwawdadwadwadwawdaddawdov22nk2d3plyvwc7yd.onion. Valid:True
+[+] file exists, your Webring URL is dawdawddwawdadwadwadwawdaddawdov22nk2d3plyvwc7yd.onion
+
+[+] Welcome to your own Darknet Lantern Instance, where you can explore the Darknet and help others do the same.
+
+Managing Websites:
+ 1) Add a new Website entry (into unverified.csv)
+ 2) Trust/Untrust/ Blacklist a Website entry (move an entry from unverified to verified.csv)
+ 3) Edit link attributes
+
+Managing Webring Participants:
+ 4) Synchronize new links from existing webring participants, into your unverified.csv file
+ 5) Add a new webring participant (and download their files into their directory (without trusting them yet!))
+ 6) Trust/UnTrust/Blacklist a webring participant (Potentially dangerous)
+
+Managing Wordlists:
+ 7) Add/Remove Words/URLs in the sensitive list (ex: drug)
+ 8) Add/Remove Words/URLs or links in the blacklist (ex: porn)
+
+Maintenance:
+ 9) Remove the duplicate URLs for your own instance
+ 10) Perform sanity checks on all csv files for all instances (to mark them as sensitive / or remove the ones that are blacklisted)
+ <b>11) Review submissions (Add to verified.csv/ add to unverified.csv/ delete /blacklist)</b>
+
+ 0) Exit
+
+Select an option? (0-11): 11
+</pre></code>
+<p>That new option is going to simply iterate over every new submission you recieved, allowing you to move the entry to 1) verified.csv, 2) or to unverified.csv, 3) or to simply delete it, 4) or to blacklist it if it's a malicious link:</p>
+<pre><code class="nim">
+name         test
+desc         test
+category     test
+sensitive       y
+Name: 0, dtype: object
+
+Link to verify:  <b>http://coollinkdwadwdwawaadwdawdawdwawaddwawdaadw.onion/</b>
+
+1) Move entry to verified.csv
+2) Move entry from submission.csv to unverified.csv
+3) Delete from submission.csv file
+4) Add to blacklist.csv
+-1) exit
+Enter an option: 1
+
+</pre></code>
+<p>Here we need to copy the link into our tor browser to review it, and upon reviewing it, we see that it's a cool and valid link, so we pick option 1 to move it to verified.csv. </p>
+<pre><code class="nim">
+name         test
+desc         test
+category     test
+sensitive       y
+Name: 0, dtype: object
+
+Link to verify:  <b>http://weirdlinkdwadwdwawaadwdawdawdwawaddwawdaadw.onion/</b>
+
+1) Move entry to verified.csv
+2) Move entry from submission.csv to unverified.csv
+3) Delete from submission.csv file
+4) Add to blacklist.csv
+-1) exit
+Enter an option: 2
+
+</pre></code>
+<p>Then we have a second submitted link, which upon reviewing is weird and not what you expected, but upon reviewing it's not something you need to blacklist so we select option 2 to leave it in unverified.csv for the time being.</p>
+<pre><code class="nim">
+name         test
+desc         test
+category     test
+sensitive       y
+Name: 0, dtype: object
+
+Link to verify:  <b>http://cringelinkwadawdwdwawaadwdawdawdwawaddwawdaadw.onion/</b>
+
+1) Move entry to verified.csv
+2) Move entry from submission.csv to unverified.csv
+3) Delete from submission.csv file
+4) Add to blacklist.csv
+-1) exit
+Enter an option: 3
+
+</pre></code>
+<p>The next submission is a cringe link, so for this one instead we're going to just delete it with option 3.</p>
+<pre><code class="nim">
+name         test
+desc         test
+category     test
+sensitive       y
+Name: 0, dtype: object
+
+Link to verify:  <b>http://maliciouslinkwadwdwawaadwdawdawdwawaddwawdaadw.onion/</b>
+
+1) Move entry to verified.csv
+2) Move entry from submission.csv to unverified.csv
+3) Delete from submission.csv file
+4) Add to blacklist.csv
+-1) exit
+Enter an option: 4
+
+</pre></code>
+<p>And the last submitted link is actually a malicious link (for example a porn link) so we select option 4 to put it into our blacklist.csv.</p>
+				</div>
+			</div><!-- /row -->
+	    </div> <!-- /container -->
+	</div><!-- /white -->
 
 
 

opsec/stylometry/index.html

@@ -104,7 +104,6 @@ Anon: The Stylometry one please.
 </code></pre>
 
 <p>All goes well <b>until you write in such a way that people recognize who you are.</b></p>
-<img src="" class="imgRz">
 <pre><code class="nim">
 Nihilist: Ok, what if i paid you 5 euros for it ?
 

opsec/tailsqemuvm/index.html

@@ -101,8 +101,7 @@
 → truncate -s 8192M tails-amd64-6.3.img 	
 
 </code></pre>
-<p>Now here we can use <a href="https://etcher.balena.io/#download-etcher">balenaetcher</a> to flash the tails OS image onto a usb stick that we plug in on our computer:</p>
+<p>From here we install tails onto the usb stick (which is detected as /dev/sdc in our usecase) from the commandline using dd:</p>
-<img src="30.png" class="imgRz">
 <pre><code class="nim">
 nihilist@mainpc:~$ lsblk
 NAME        MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINTS
@@ -111,15 +110,10 @@ NAME        MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINTS
 <b>sdc           8:32   1  14.6G  0 disk  </b>
 [...]
 
-nihilist@mainpc:~$ cd .mullvad-browser/Downloads/
+user@mainpc:~$ cd .mullvad-browser/Downloads/
-nihilist@mainpc:~/.mullvad-browser/Downloads$ unzip balenaEtcher-linux-x64-1.19.25.zip 
+usert@mainpc:~$ <b>sudo dd if=/home/user/tails-amd64-6.3.img of=/dev/sdc bs=16M oflag=direct status=progress</b>
-nihilist@mainpc:~/.mullvad-browser/Downloads$ cd balenaEtcher-linux-x64/
-nihilist@mainpc:~/.mullvad-browser/Downloads/balenaEtcher-linux-x64$ ./balena-etcher
 
 </pre></code>
-<img src="31.png" class="imgRz">
-<img src="32.png" class="imgRz">
-<img src="33.png" class="imgRz">
 <p>Now that the Tails OS image has been flashed onto the usb stick, you can simply reboot your computer, and then enter the boot menu to choose to boot onto the USB rather than onto your host OS. In this example i need to press ESC, but depending on your motherboard you may need to press F2, or F11, or another key.</p>
 <img src="34.png" class="imgRz">
 <p>Then after entering the boot options by pressing ESC, we press 1 to choose to boot onto the USB key, rather than booting on the system drive.</p>