You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Everytime autoupdate pushes a backup, scp asks for a password. The router should have an ssh-key to actively push files on other systems. This key might be generated not only for autoupdate, but for the router itself.
The text was updated successfully, but these errors were encountered:
One problem with pushing via scp is that if the sender gets compromised, it'd be easy for an attacker to a) compromise upstream backups, and b) possibly compromise the entire upstream system. I'm not sure what scope the backup solution is intended for, but for general use I'd rather recommend using something else (e.g., POSTing possibly encrypted backup data along with a recovery email address to some HTTPS backup server that keeps incremental copies of backups).
Initially I thought of this backup function of a merely private function: The function should have only give the comfort of pushing the backups automatically into an archive-directory on the owners laptop.
We should defnitely discuss on a more secure solution, which could maybe incorporate pushing to (dezentralised) Servers.
Akira25
changed the title
[ssh] private key for routers
[backup] save backups remotely in a save manner
May 19, 2020
idea from firmware-meeting at 05.05.2020
Everytime autoupdate pushes a backup, scp asks for a password. The router should have an ssh-key to actively push files on other systems. This key might be generated not only for autoupdate, but for the router itself.
The text was updated successfully, but these errors were encountered: