Open iShift opened 8 years ago
I dont really want to expose the private keys to webui.
If there was a vulnerability in webUI, then it would be to easy to grab the private keys, this isn't a really good idea...
but in the future we need that - for example - if you have zero on phone and you want your profile on it.
In that case it can be implemented in the mobile app.
Does it mean new key (and mail) for the phone?
but what about transfer? qrcode?
Exposing qrcode has just the same vulnerabilities.
Another option could be wrapping the keys in an downloadable-encrypted file with a temporary password the user would choose just in time. But that would bring unnecessary complexity.
The transference should never be trough web ui.
Perhaps this would be possible by standing up a server on another port number just for serving this data - wouldn't that fail same origin policy?
A bad browser plugin would able to stole it from the another port.
a malware can do the same under the windows
Sure, but we should minimize the attack vectors
Backing up your private keys to an off-line storage or to paper should be easy for site administrators. If it is not possible to do it using the WebUI, it should be easy to do using the ZeroNet client user interface. BIP39 makes paper storage easy. We would need password authentication for accessing the private key (#384) as a prerequisite for this issue.
+1 for BIP39 from cli for backup purpose.
+1 for cli, sending passwords across browser should be avoided IMO
Hi, thought it may be helpful if Zeronet has some built in automatic backuper of the important files (users.json) because identity is important and not everyone is technically skilled or aware of the importance to backup certain file and also somehow automate the job.
For example if ZeroNet inform user how important is to backup users.json, ask him to define backup location and do the automated backups periodically. (on each start, etc.) filename would be example: Zeronet_user_profilebackup(keep_private)_12.12.2018.backup
then when user reinstall PC, Zeronet upon first-time start (missing or raw users.json) will ask user if he want to import identity backup. Preferably if user can see details of each identity backup like number of follows/subscribbed topics,
In case of malwares, for extra security layer, ZeroNet could have a mode to not store user seed (but their data) and ask for login on every ZN startup
@HelloZeroNet @shortcutme
a malware could infect zeronet as it starts...
With key and sites: On ZeroHello we can have button import/export