Skip to content
Snippets Groups Projects
Commit c2320a81 authored by Amna Snene's avatar Amna Snene Committed by Adrien Béraud
Browse files

doc: update README

Change-Id: I6db02e7fecc437711194899cd90288a229e6326f
parent bb300a13
No related branches found
No related tags found
No related merge requests found
......@@ -100,7 +100,7 @@ DHTNet depends on the following libraries:
### Dnc: Distributed nc
dnc is a program that provides network connectivity between peers in a Distributed Hash Table (DHT) network. It allows peers to establish connections with other peers and create a TCP socket on a remote devices, similar to the behavior of the traditional nc utility.
dnc is a command-line program that provides network connectivity between peers in a Distributed Hash Table (DHT) network. It allows peers to establish connections with other peers and create a TCP socket on a remote devices, similar to the behavior of the traditional nc utility.
#### SSH configuration
To simplify the usage of dnc with SSH, you can add the following lines to your SSH configuration file (`~/.ssh/config`):
```ssh
......@@ -127,7 +127,7 @@ ssh mypeer@dnc/2f4975e7b11a0908bd400b27130fe9a496d0f415
### Dsh: Distributed shell
dsh is a Distributed Shell program that enables peers to establish connections with other peers in a Distributed Hash Table (DHT) network and execute a binary on the remote target.
dsh is a Distributed Shell command-line program that enables peers to establish connections with other peers in a Distributed Hash Table (DHT) network and execute a binary on the remote target.
#### Setting up the Server (Listening) and Default Command
......@@ -143,4 +143,8 @@ dsh -I /home/<local_user>/.dhtnet/client <peer_id>
```
##### Using Different Certificates
If the client and server are on the same machine, they should use different certificates for authentication, so make sure to specify different identity file paths for the client and server. This ensures that they use separate certificates. In the example above, we specified the client's identity file path as /home/<local_user>/.dhtnet/client
\ No newline at end of file
If the client and server are on the same machine, they should use different certificates for authentication, so make sure to specify different identity file paths for the client and server. This ensures that they use separate certificates. In the example above, we specified the client's identity file path as /home/<local_user>/.dhtnet/client
## Report issues
Report issues on Gitlab: https://git.jami.net/savoirfairelinux/dhtnet/-/issues
\ No newline at end of file
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment