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 precedente | ||
| reachme [2022/11/06 14:26] – 0.7.4 pietro | reachme [2024/01/07 11:46] (versione attuale) – 0.7.5 pietro | ||
|---|---|---|---|
| Linea 1: | Linea 1: | ||
| - | {{: | + | {{: |
| - | | + | |
| + | |||
| + | {{: | ||
| ===== What is this? ===== | ===== What is this? ===== | ||
| Linea 16: | Linea 19: | ||
| 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.1667744777.txt.gz · Ultima modifica: da pietro
