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
This is a pie-in-the-sky feature, but I'm thinking it can be achieved.
The idea here is to be able to provide a file-sharing utility, where the file being shared never reaches the API, therefore it is never removed from the user ownership. When the other side downloads the file, the file will download encrypted from client to client.
Since clients aren't immediately available on the internet, I'm thinking to take this approach.
(User A sends, User B receives).
User A starts up the utility in share mode.
User A uploads their file to the system (into LocalStorage, client-side).
File is encrypted (CryptoJS is already a product dependency), key is shared to the user and user told to not leave the page.
User A shares the key to user B. User B loads the interface.
File from user A is downloaded onto user B's machine, in an encrypted state.
This might need to be proxied by the server, since we can't take A a host.
Encryption decoding key provided, the user receives the file in the intended state.
File has been successfully shared between hosts.
The text was updated successfully, but these errors were encountered:
This is a pie-in-the-sky feature, but I'm thinking it can be achieved.
The idea here is to be able to provide a file-sharing utility, where the file being shared never reaches the API, therefore it is never removed from the user ownership. When the other side downloads the file, the file will download encrypted from client to client.
Since clients aren't immediately available on the internet, I'm thinking to take this approach.
(User A sends, User B receives).
The text was updated successfully, but these errors were encountered: