Fix <pre> areas in markdown
This commit is contained in:
parent
4627410580
commit
f82cb5dbf7
@ -77,7 +77,8 @@ can do:
|
|||||||
1. Build >=OpenSSL-1.1.0 (e.g., using the provided ./build_openssl command)
|
1. Build >=OpenSSL-1.1.0 (e.g., using the provided ./build_openssl command)
|
||||||
2. Build and install luksrku: make && sudo make install
|
2. Build and install luksrku: make && sudo make install
|
||||||
3. Generate the keyfiles. For this we use the provided gen_config script:
|
3. Generate the keyfiles. For this we use the provided gen_config script:
|
||||||
```
|
|
||||||
|
```bash
|
||||||
Disk UUID : 952ebed9-5256-4b4c-9de5-7f8829b4a74a
|
Disk UUID : 952ebed9-5256-4b4c-9de5-7f8829b4a74a
|
||||||
Disk name : crypt-root
|
Disk name : crypt-root
|
||||||
Suggestion: TDFV6Z6XyDQ52ASswVFSEl8mrVfnH9F5b
|
Suggestion: TDFV6Z6XyDQ52ASswVFSEl8mrVfnH9F5b
|
||||||
@ -92,19 +93,22 @@ can do:
|
|||||||
# Host UUID Host PSK Disk UUIDs
|
# Host UUID Host PSK Disk UUIDs
|
||||||
d66f96fc-7056-46e1-aea6-0f3d705cd3bc d94f3fc6c3507123bda4034dd8c865a1b4cf9870bda50e9ed9f861621d581017 952ebed9-5256-4b4c-9de5-7f8829b4a74a=54444656365a3658794451353241537377564653456c386d7256666e4839463562
|
d66f96fc-7056-46e1-aea6-0f3d705cd3bc d94f3fc6c3507123bda4034dd8c865a1b4cf9870bda50e9ed9f861621d581017 952ebed9-5256-4b4c-9de5-7f8829b4a74a=54444656365a3658794451353241537377564653456c386d7256666e4839463562
|
||||||
```
|
```
|
||||||
|
|
||||||
We follow the suggested passphrase, which should contain 192 bits of entropy.
|
We follow the suggested passphrase, which should contain 192 bits of entropy.
|
||||||
4. We use cryptsetup luksAddKey to add the suggested passphrase to the LUKS
|
4. We use cryptsetup luksAddKey to add the suggested passphrase to the LUKS
|
||||||
keyring of the server.
|
keyring of the server.
|
||||||
5. The config script has given suggestions for server.txt and client.txt. We
|
5. The config script has given suggestions for server.txt and client.txt. We
|
||||||
copy the respective contents into the files.
|
copy the respective contents into the files.
|
||||||
6. Then we create the server binary config:
|
6. Then we create the server binary config:
|
||||||
```
|
|
||||||
|
```bash
|
||||||
$ luksrku-config server server.txt server.bin
|
$ luksrku-config server server.txt server.bin
|
||||||
Successfully read key file with 1 entries.
|
Successfully read key file with 1 entries.
|
||||||
$ luksrku-config client client.txt client.bin
|
$ luksrku-config client client.txt client.bin
|
||||||
Successfully read key file with 1 entries.
|
Successfully read key file with 1 entries.
|
||||||
Passphrase to encrypt keyfile:
|
Passphrase to encrypt keyfile:
|
||||||
```
|
```
|
||||||
|
|
||||||
Now we'll have a server.bin and password-protected client.bin.
|
Now we'll have a server.bin and password-protected client.bin.
|
||||||
7. On the server machine (i.e., the one with the LUKS disk) we copy
|
7. On the server machine (i.e., the one with the LUKS disk) we copy
|
||||||
server.bin to /etc/luksrku-server.bin.
|
server.bin to /etc/luksrku-server.bin.
|
||||||
@ -120,6 +124,7 @@ can do:
|
|||||||
will now broadcast UDP packets onto the network indicating its presence.
|
will now broadcast UDP packets onto the network indicating its presence.
|
||||||
These packets will be sent to UDP port 23170.
|
These packets will be sent to UDP port 23170.
|
||||||
12. On the client, start the client to unlock the server's key:
|
12. On the client, start the client to unlock the server's key:
|
||||||
|
|
||||||
```
|
```
|
||||||
$ luksrku --client-mode -k client.bin
|
$ luksrku --client-mode -k client.bin
|
||||||
Keyfile password:
|
Keyfile password:
|
||||||
|
Loading…
Reference in New Issue
Block a user