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
IPFS uses transport encryption but not content encryption. This means your data is secure when sent from one IPFS node to another. However, anyone can download and view that data with the CID. The lack of content encryption is an intentional decision. Instead of forcing you to use a particular encryption protocol, you can choose the best method for your project. This modular design keeps IPFS lightweight and free of vendor lock-in.
However, to add encryption support, it might help to create a plugin for IPFS.
https://docs.ipfs.tech/concepts/privacy-and-encryption/#encryption
IPFS uses transport encryption but not content encryption. This means your data is secure when sent from one IPFS node to another. However, anyone can download and view that data with the CID. The lack of content encryption is an intentional decision. Instead of forcing you to use a particular encryption protocol, you can choose the best method for your project. This modular design keeps IPFS lightweight and free of vendor lock-in.
However, to add encryption support, it might help to create a plugin for IPFS.
Solutions using IPFS.
Structure notes
The text was updated successfully, but these errors were encountered: