3 ms·
>I'd likely still be hosting the files right? Yes but the entire web points to the wrong files since you no longer own the IPNS location. It's similar to loos
by tscs37 10y ago
>I'd likely still be hosting the files right?
Yes but the entire web points to the wrong files since you no longer own the IPNS location.
It's similar to loosing access to your DNS configuration or loosing your GPG keys to an attacker.
- IanCal 10y ago> Yes but the entire web points to the wrong files since you no longer own the IPNS location. Along with a link to all previous versions if there's a chain. And anyone pointing to a specific version will still see that rather than the new one. > It's similar to loosing access to your DNS configuration Yes. > or loosing your GPG keys to an attacker. I think that's a bit strong. > >I think there was some discussion about having there be a chain > Still same problem, if the private key gets leaked, a malicious attacker can manipulate the entries on the chain. I'm really not sure that's right, IPNS doesn't give you the ability to edit content.
- tscs37 10y ago>And anyone pointing to a specific version will still see that rather than the new one. That's an IPFS Hash tho, not IPNS. Differences matter. >I think that's a bit strong. Over time your IPNS could very well become your identity, linked everywhere in the net. >IPNS doesn't give you the ability to edit content. That is correct, but you can point at arbitrary content. It's basically the equivalent to controlling the DNS A entry to a website, they can't modify the content and it's available under the same IP but they can still do a shitload of bad stuff because few people bother to actually link IP addresses.