summaryrefslogtreecommitdiff
path: root/content
diff options
context:
space:
mode:
authorDavid Uhden Collado <149145202+daviduhden@users.noreply.github.com>2024-07-04 05:50:43 +0200
committerGitHub <noreply@github.com>2024-07-04 05:50:43 +0200
commita526f83994b3ac11acc064ed2f6d82b9df430dcf (patch)
treea64ae8b354caa92d4ada1b4b39be32ed0ec27f8c /content
parent6a514eef9eb008d1b8ab6fae3423c4aa6afa21e2 (diff)
Update i2p.md
Add formatting.
Diffstat (limited to 'content')
-rw-r--r--content/i2p.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/content/i2p.md b/content/i2p.md
index 40ac79d..19923cc 100644
--- a/content/i2p.md
+++ b/content/i2p.md
@@ -58,7 +58,7 @@ If you run `i2pd` with the configuration above, it will generate a random privat
If you instead pre-generate a private key for your website, you can use brute-force computation to make a "vanity" address, such as the following:
```
-chadaor3jc08ht340c30mg5cf340j395gj095kuazj5tokipr34f.32.i2p
+{{<hl>}}chad{{</hl>}}aor3jc08ht340c30mg5cf340j395gj095kuazj5tokipr34f.32.i2p
```
To accomplish this, a set of tools named `i2pd-tools` can be installed.
@@ -81,7 +81,7 @@ make -j$(nproc)
This will build a variety of useful tools for i2p, with `vain` being the command of interest to generate an address:
```sh
-./vain chad
+./vain {{<hl>}}chad{{</hl>}}
```
This command will begin running and output a new set of private keys named `private.dat` to the same directory it's ran from. Copy this file to your i2p configuration and you'll have your vanity address:
@@ -94,7 +94,7 @@ cp private.dat /var/lib/i2pd/example.dat
I2P has various **registrars** that let users link their long I2P addresses to shorter, more memorable ones, like `example.i2p`. To actually register your site on one of these registrars, you will need an **authentication string.** Luckily, `i2pd-tools` includes such a tool in their repository:
```sh
-./regaddr private.dat example.2ip > auth_string.txt
+./regaddr private.dat {{<hl>}}example.2ip{{</hl>}} > {{<hl>}}auth_string.txt{{</hl>}}
```
The command above will save the string to a file named `auth_string.txt`. You will have to place the text contained in that file on a registration page like [http://reg.i2p/add](http://reg.i2p/add) or [http://stats.i2p/i2p/addkey.html](http://stats.i2p/i2p/addkey.html).
@@ -121,7 +121,7 @@ From here, the steps are almost identical to setting up a normal website configu
```nginx
server {
listen 127.0.0.1:8080 ;
- root /var/www/example ;
+ root /var/www/{{<hl>}}example{{</hl>}} ;
index index.html ;
}
```