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
ipwb currently encrypts content prior to pushing to IPFS with a key in anticipation that the same key will be used for decryption on replay, possibly by another user/party. As of version 0.4.7 (ipfs/kubo#3397 (comment)), IPFS has the ability to limit the swam to only users with a generated and shared key. Using this key in lieu of entering a string might be a good way to facilitate collaboration of archives. An idea is to use the generated key as the basis of encryption/decryption.
The text was updated successfully, but these errors were encountered:
ipwb currently encrypts content prior to pushing to IPFS with a key in anticipation that the same key will be used for decryption on replay, possibly by another user/party. As of version 0.4.7 (ipfs/kubo#3397 (comment)), IPFS has the ability to limit the swam to only users with a generated and shared key. Using this key in lieu of entering a string might be a good way to facilitate collaboration of archives. An idea is to use the generated key as the basis of encryption/decryption.
The text was updated successfully, but these errors were encountered: