reachme
Differenze
Queste sono le differenze tra la revisione selezionata e la versione attuale della pagina.
Entrambe le parti precedenti la revisioneRevisione precedenteProssima revisione | Revisione precedenteUltima revisioneEntrambe le parti successive la revisione | ||
reachme [2021/12/11 19:59] – new repo pietro | reachme [2023/12/02 10:04] – tpos pietro | ||
---|---|---|---|
Linea 1: | Linea 1: | ||
- | {{: | + | {{: |
- | | + | |
- | + | ||
- | {{: | + | |
+ | {{: | ||
===== What is this? ===== | ===== What is this? ===== | ||
Linea 19: | Linea 18: | ||
And this is how you use it: | And this is how you use it: | ||
- | * **reachme** is ran on **A** | + | * **reachme** is run on **A** |
- | * **reachthem** is ran on **C**, sees there is a connection to **A** available, and allows the user of **C** to connect to **A**. | + | * **reachthem** is run on **C**, sees there is a connection to **A** available, and allows the user of **C** to connect to **A**. |
There is nothing very new or complicated in this: it just uses SSH port forwarding, a classic (and pretty safe) tool. **reachme** and **reachthem** make the process just a bit simpler, in particular if the user of **A** is technically not very sophisticated. | There is nothing very new or complicated in this: it just uses SSH port forwarding, a classic (and pretty safe) tool. **reachme** and **reachthem** make the process just a bit simpler, in particular if the user of **A** is technically not very sophisticated. | ||
+ | |||
===== Typical use cases ===== | ===== Typical use cases ===== | ||
reachme.txt · Ultima modifica: 2024/01/07 12:46 da pietro