Conversation:
Notices
-
Thought: You could have the migration generate a key used to encrypt the backup, which is then transmitted only to the target server and then stored, and then email the user the migration data when the backup task is complete. They would then upload that zip file to the target server and the key would be needed to decrypt the archive and thus import the account.
-
What do you think of this implementation idea for your suggestion, @bob?
-
@bob Well I figure if the archive is encrypted and the end-user doesn't have the key then that mitigates most attacks regarding injection of bad data sufficiently.
-
@bob It is my understanding that this is the reason the functionality of restoring remote backups was curtailed in StatusNet originally, from the comments, but I may be wrong.
-
@bob Definitely. We could write an internal header with checksum, expected length, and a few other things that represent easy checks.
-
@bob Yes we'd definitely want to scrub anything that can't normally be in notices out of there though you could still run into problems regardless.
maiyannah
All Hacker Poesy content and data are available under the