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
Currently, all data received by the brave integration (#64) is marked as "not secure". While this is currently true for IPNS, it's not true for IPFS-CIDs.
I created a ticket to have a look at the integration of DNSSec to make sure we have domain-to-content validation and don't rely on unencrypted unsigned DNS requests which can be altered by MITM or DNS-Spoofing.
URLs with the IPFS-scheme are also marked as insecure, which is not true - so there's also a ticket (brave/brave-browser#13727) for that.
Currently, all data received by the brave integration (#64) is marked as "not secure". While this is currently true for IPNS, it's not true for IPFS-CIDs.
I created a ticket to have a look at the integration of DNSSec to make sure we have domain-to-content validation and don't rely on unencrypted unsigned DNS requests which can be altered by MITM or DNS-Spoofing.
URLs with the IPFS-scheme are also marked as insecure, which is not true - so there's also a ticket (brave/brave-browser#13727) for that.
Originally I created a ticket here, but the content got moved to brave/brave-browser#13706.
The text was updated successfully, but these errors were encountered: