5 ms·
Never having used or looked into Beaker, dat, ipfs, etc, some immediate questions about security implications come to mind: 1) Someone accesses your "site" dir
by indigodaddy 9y ago
Never having used or looked into Beaker, dat, ipfs, etc, some immediate questions about security implications come to mind:
1) Someone accesses your "site" directly on your computer via ipfs/dat whatever it is. This is static content I guess? And it's like your computer is just running a static webserver (kinda/sorta? if not, or something more dynamic please advise). So, are there security implications here? Is there an attack surface that a client/viewer of your content could leverage?
2) Sort of opposite question as in 1. You are the client/viewer of the "site," directly connected to some dude's computer via ipfs/dat or whatever. Obviously I should use standard security measures and not just go clickity on anything/everything I see, but beyond that, are there any other security implications for the client? I could download a virus I'm sure by clicking or downloading a malicious file, but beyond that, could I get hacked by the target in a more dynamic way than that?
3) How do I "navigate" in ipfs/dat-land? How do I know what URL to go to, and if this "URL" might be a safe site, or like what the hell is this URL if it's just some kind of hash? Is there a "google" of ipfs/dat sites/content?
Stuff like this. :) Any feedback would be muchly appreciated!
- StavrosK 9y ago1) Yep, exactly. There shouldn't be security implications, as long as the IPFS daemon is secure. 2) Again, as long as the IPFS daemon is secure, standard security practices apply. It's just static files. 3) It's all just static files. You get linked to from other files. Same as you navigate the rest of the web. It's not hard to wrap your head around it, really, just imagine that the web was all static files. That's it.
- patmorgan23 9y agoFor number 3 literally the web 20( 30?) years ago
- StavrosK 9y agoWe definitely had dynamic websites in 1998, guestbooks, forums, etc. Mostly via CGI. But yes, it's very close to that.
- notheguyouthink 9y agoI mean, sort of. We had some files that weren't expected to change, but nearly nothing was truly static. Content Addressable .. content is truly unchanging. Which, imo, is something the modern web is lacking.
- sova 9y agoIpfs is awesome. It's more like bit torrent. You have hashes generated based on files. Same hash always points to same file, provided at least one ipfs node is mirroring it. You don't automatically mirror content with ipfs unless you elect to. When you update your site, the hash must change, and thus the link changes as well. Security stuff... Yeah it can be used maliciously just like bit torrent can, but ipfs hashes can be accessed also by ipfs.io/hash and I haven't heard of any problems with malware or anything of the sort, things get filtered out pretty quickly it seems. Ipfs is awesome. Read the white paper ... It's such a nice middle layer for projects wanting to use a distributed file network without building out their own torrent network.
- zapita 9y ago> 1) Someone accesses your "site" directly on your computer via ipfs/dat whatever it is. This is static content I guess? And it's like your computer is just running a static webserver (kinda/sorta? It's like static content served by bittorrent. The content might be served directly by your computer, or by other nodes in the ipfs/dat network which are caching your content. > So, are there security implications here? Is there an attack surface that a client/viewer of your content could leverage? An attacker could try to exploit vulnerabilities in the IPFS/DAT network. This would be similar to exploiting vulnerabilities in bittorrent. Or they could try to steal the private key used to publish your content, and publish malicious updates. If access to your content is restricted (ie with a secret hash or url), an attacker might try to get access to it. Overall the security model is quite straightforward, with a smaller attack surface than typical dynamic web stacks. > 2) Sort of opposite question as in 1. You are the client/viewer of the "site," directly connected to some dude's computer via ipfs/dat or whatever. Obviously I should use standard security measures and not just go clickity on anything/everything I see, but beyond that, are there any other security implications for the client? I could download a virus I'm sure by clicking or downloading a malicious file, but beyond that, could I get hacked by the target in a more dynamic way than that? It's pretty much the same security model as regular web content, as you mention. The only exception might be a vulnerability in the ipfs/dat code, since your computer might be running a local node. > 3) How do I "navigate" in ipfs/dat-land? How do I know what URL to go to, and if this "URL" might be a safe site, or like what the hell is this URL if it's just some kind of hash? Is there a "google" of ipfs/dat sites/content? IPFS has a naming system called IPNS, where addresses are based on a unique crypto keypair. Addresses look like `/ipns/<hash>`. You can use specialized ipfs software, like the `ipfs` cli, or navigate your regular browser to an http gateway. For example, with the official gateway you can navigate to `https://ipfs.io/ipns/<hash>` https://ipfs.io/ipns/<hash>`. Ipfs also has a facility to easily alias a DNS domain to an ipns key, so you can navigate to `/ipns/<mydomain.com>` Dat I believe has a similar system. The main difference is that, thanks to Beaker, you can bypass the gateway system - just navigate to `mydomain.com` and, if it's dat-enabled, the browser will lookup the corresponding key and fetch the content via dat instead of http. There's no reason IPFS couldn't work the same way - you just need a browser to implement iofs support directly in the same way. Personally I hope Beaker will find the time to support both! > Is there a "google" of ipfs/dat sites/content? Not that I know of. But I think it's inevitable!