Live data from Hacker News

Show HN: Encrypt and upload files to IPFS from browser

thirdcloud.org

21–30 of 43 posts

Re: Show HN: Encrypt and upload files to IPFS from browser

#21

Encryption gets broken eventually as we get more compute power, and the current algorithms could have problems we're not yet aware of. IPFS requires every node to agree to your delete request (if I'm understanding it correctly). What's stopping someone from just vacuuming all the data they can until codebreaking catches up with encryption? Is there a way to remove malicious content? For example, if someone uses this…

You can make blocks private in ipfs so only authorised people can download them. Here's how we do this in peergos https://peergos.org/posts/bats

Re: Show HN: Encrypt and upload files to IPFS from browser

#22
post #12
post #11

Earlier quoted context omitted.

It's encrypted directly on your browser, you can download the encryption key after file is uploaded. Not content-based (because the header is randomly generated & you keep the encryption key) but you can share to secret file to others and they will be able to download the file. Files are pinned mainly by NFTStorage. Currently it's free because NFTStorage is free. If things change I would allow buying storage using Fi…

According to NFTStorage's Terms and Conditions: > The Service is offered for the creation and storage of NFTs. Use of the Service to store other types of data is not permitted. Do you have a special agreement with NFTStorage which overrules the general Terms and Conditions?

https://web3.storage/ most likely

Re: Show HN: Encrypt and upload files to IPFS from browser

#23
post #12
post #11

Earlier quoted context omitted.

It's encrypted directly on your browser, you can download the encryption key after file is uploaded. Not content-based (because the header is randomly generated & you keep the encryption key) but you can share to secret file to others and they will be able to download the file. Files are pinned mainly by NFTStorage. Currently it's free because NFTStorage is free. If things change I would allow buying storage using Fi…

According to NFTStorage's Terms and Conditions: > The Service is offered for the creation and storage of NFTs. Use of the Service to store other types of data is not permitted. Do you have a special agreement with NFTStorage which overrules the general Terms and Conditions?

Isn't any file stored on IPFS by definition a NFT, since the address identifies a unique file?

Re: Show HN: Encrypt and upload files to IPFS from browser

#25
post #12

Earlier quoted context omitted.

According to NFTStorage's Terms and Conditions: > The Service is offered for the creation and storage of NFTs. Use of the Service to store other types of data is not permitted. Do you have a special agreement with NFTStorage which overrules the general Terms and Conditions?

Isn't any file stored on IPFS by definition a NFT, since the address identifies a unique file?

Technically no, you'd need to also deploy a NFT smart contract that creates a new token for each file. But theoretically any media type could be represented by an NFT so it's sort of an arbitrary restriction by NFT.storage. Probably not super enforceable on their part. I imagine the promo will end at some point though. Filecoin just happens to have an excess of available storage right now, which is why they can afford to offer it for free.

Re: Show HN: Encrypt and upload files to IPFS from browser

#26
post #4

Allow the user to decide if encryption should be applied to files or not. I have files that are already encrypted.

I’m not arguing that you don’t have a valid point nor that the feature request should be beneficial for the project to add to gain wider adoption. I know why this feature isn’t there though, because doubly encrypting something doesn’t do anything but add another layer of protection they guarantee by default, but that the computational cost of this possibly not needed protection is assumed by the provider and not the…

A simple checkbox is all that is needed.

Re: Show HN: Encrypt and upload files to IPFS from browser

#27

Encryption gets broken eventually as we get more compute power, and the current algorithms could have problems we're not yet aware of. IPFS requires every node to agree to your delete request (if I'm understanding it correctly). What's stopping someone from just vacuuming all the data they can until codebreaking catches up with encryption? Is there a way to remove malicious content? For example, if someone uses this…

>Is there a way to remove malicious content? For example, if someone uses this to store some malware's payload and you don't want your project being used for that, what happens?

My job involves fighting malicious content on the internet. No, there's no way to remove malicious content from ipfs. It's especially annoying when the ipfs2http gateway takes path using a GET parameter (instead of it being a part of a domain name) because it makes it unblockable on the DNS level.

Re: Show HN: Encrypt and upload files to IPFS from browser

#30

Encryption gets broken eventually as we get more compute power, and the current algorithms could have problems we're not yet aware of. IPFS requires every node to agree to your delete request (if I'm understanding it correctly). What's stopping someone from just vacuuming all the data they can until codebreaking catches up with encryption? Is there a way to remove malicious content? For example, if someone uses this…

> What's stopping someone from just vacuuming all the data they can until codebreaking catches up with encryption?

The people who have the time and resources to do this are nation states. And if they're going to spend their resources on IPFS, they're also already doing this for intercepted HTTPS traffic because it would be wild not to. Imagine having the confidence to crack strong encryption and ignoring 99.9999% of web traffic so you could potentially spy on the handful of gigabytes of whatever is ending up on IPFS.

Even if codebreaking catches up to the point where it's tractable to start cracking the encryption on these files, the ability to tractably crack _all_ the files is probably many decades away. You can probably be confident that you'll be long dead. And you can almost certainly be confident that by the time any of the files (or HTTPS traffic, or whatever) get cracked, the statute of limitations has long passed on whatever nefarious thing you are worried might get seen.

Of course privacy from the prying eyes of the NSA (or your favorite codebreaking entity of choice) is obviously important, but it really begs the question: what is their incentive to do this? To get in on the furry porn you're uploading? To see your baby pictures? The kinds of secrets the NSA is looking for need to be worthwhile enough for the NSA to justify spend millions (billions? tens of billions?) of dollars building zettabyte-scale data centers and cracking them years and years after the fact instead of spending that money on something more immediately impactful. Quite frankly, those secrets aren't "someone from HN sharing their files over ipfs"-shaped.

Post reply on HN