mirror of
http://git.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/nihilist/darknet-lantern.git
synced 2025-05-16 20:26:58 +00:00
updated readme : v1.0.1 released
This commit is contained in:
parent
a73825a91b
commit
ab25258245
1 changed files with 30 additions and 7 deletions
37
README.md
37
README.md
|
@ -1,6 +1,25 @@
|
|||
# [Darknet Lantern Project v1.0.0](http://lantern.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/)
|
||||
# [Darknet Lantern Project v1.0.1](http://lantern.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/)
|
||||

|
||||
|
||||
```sh
|
||||
/!\ WARNING, BREAKING CHANGES FROM V1.0.0 TO V1.0.1 /!\
|
||||
|
||||
cd /srv/darknet-lantern
|
||||
|
||||
#backup your participants directory:
|
||||
cp -r www/partcipants /tmp/participants
|
||||
|
||||
#abandon changes in the git directory in /srv/
|
||||
git stash
|
||||
|
||||
#update the git repo by doing a git pull
|
||||
torsocks git pull
|
||||
|
||||
#reimport your csv files:
|
||||
cp -r /tmp/participants www/participants
|
||||
|
||||
```
|
||||
|
||||
To explain the full context on why this project is relevant in the Darknet Ecosystem compared to the clearnet, check out [this blogpost](http://blog.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/opsec/darknetexploration/index.html)
|
||||
|
||||
For a full step-by-step tutorial on how to setup your own Darknet lantern, check out [this tutorial](http://blog.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/opsec/darknetlantern/index.html)
|
||||
|
@ -76,21 +95,25 @@ V0.8:
|
|||
v0.9
|
||||
- harden the python code to make sure that the user filters out malicious inputs from other webring participants
|
||||
- harden the PHP code to prevent any malicious php code from being ran from csv files even if that shouldnt be possible
|
||||
```
|
||||
|
||||
Current Version:
|
||||
```
|
||||
V1.0.0: (01/02/2025)
|
||||
- doc: finish the blogposts on why it is important, and how to setup your own instance
|
||||
- release it officially to try and onboard the first webring participants
|
||||
- php: find a way to display the description for each link
|
||||
|
||||
```
|
||||
|
||||
Current Version:
|
||||
```
|
||||
V1.0.1:
|
||||
- py: refactor/simplify the lantern.py script wherever possible (assigned to Sovereignty)
|
||||
- git: implement .gitignore to ignore www/participants, otherwise you can't do torsocks git pull without having to do a git stash
|
||||
- py: since .gitignore makes it so that www/participants doesnt exist, automatically create the directory structure from www/.official_participants
|
||||
|
||||
```
|
||||
|
||||
Future Versions:
|
||||
```
|
||||
V1.0.1:
|
||||
- py: refactor/simplify the lantern.py script wherever possible (assigned to Sovereignty)
|
||||
|
||||
V1.0.2:
|
||||
- py: in option 4, make sure that new webring participants (that are listed from other webrings) are automatically added on your own instance aswell
|
||||
- py: merge the option 2 and 3 together, and repurpose option 3 to become "edit links attributes"
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue