Timeline for How to force low ssh-encryption
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 16 at 1:41 | answer | added | forest | timeline score: 2 | |
| Apr 16, 2016 at 9:46 | comment | added | meuh |
You could use rsync in its daemon mode where it can use a direct tcp connection with optional compression.
|
|
| Apr 16, 2016 at 8:55 | comment | added | Jakuje | You should rather consider setting up some FTP server. If you are running over trusted LAN, I don't think encryption is needed. | |
| S Apr 16, 2016 at 8:18 | history | suggested | Lucas | CC BY-SA 3.0 |
remove greetings
|
| Apr 16, 2016 at 8:18 | answer | added | Benjamin | timeline score: 0 | |
| Apr 16, 2016 at 7:51 | review | Suggested edits | |||
| S Apr 16, 2016 at 8:18 | |||||
| Apr 16, 2016 at 7:42 | comment | added | Eddynand Fuchs | it's definitely not disk I/O since pv /dev/zero > x.bin gives me arount 39 MB/s while over ssh I only get 15 | |
| Apr 16, 2016 at 7:40 | comment | added | Archemar | It is unclear that lowering encryptin will accelerate backup. bottleneck more likely located with disk I/O. However, you can try to reactivate remsh (remote shell, aka rsh, port 23) of old, for testing purpose. | |
| Apr 16, 2016 at 7:29 | review | First posts | |||
| Apr 16, 2016 at 7:51 | |||||
| Apr 16, 2016 at 7:29 | history | asked | Eddynand Fuchs | CC BY-SA 3.0 |