Live data from Hacker News

Paaster – Secure by default end to end encrypted pastebin

github.com

11–18 of 18 posts

Re: Paaster – Secure by default end to end encrypted pastebin

#11

I wish there was a way to create a link which doesn't contain the password so I can send the password separately.

Looking at https://github.com/WardPearce/paaster/blob/Development/paast... the link is just concatenated with # - navigate(`/${pasteId}#${paste.clientSecret}`)} So you could just copy the link as everything before the # and send the rest as the password separately

Yep, that's exactly how it works.

It's the same concept as how mega.nz do their E2EE.

Re: Paaster – Secure by default end to end encrypted pastebin

#12
post #9

Earlier quoted context omitted.

AFAICT you could permanently trust a webapp loaded from an IPFS-scheme URI (as e.g. Brave can do), after it’s been audited once.

But then if you're using an IPFS gateway instead of hosting your own instance then the gateway could serve you different content, no?

Since you request data by a hash, and your software should verify the downloaded data has the same hash, no.

Re: Paaster – Secure by default end to end encrypted pastebin

#13
post #12

Earlier quoted context omitted.

But then if you're using an IPFS gateway instead of hosting your own instance then the gateway could serve you different content, no?

Since you request data by a hash, and your software should verify the downloaded data has the same hash, no.

If you're using a gateway, you have to trust the gateway.

Re: Paaster – Secure by default end to end encrypted pastebin

#14
post #13
post #12

Earlier quoted context omitted.

Since you request data by a hash, and your software should verify the downloaded data has the same hash, no.

If you're using a gateway, you have to trust the gateway.

You could probably have a pretty light wrapper around the gateway which verifies the hash.

It wouldn't be as easy as simply using a gateway but still much easier than hosting/implementing an IPFS node locally

Re: Paaster – Secure by default end to end encrypted pastebin

#15
post #14
post #13

Earlier quoted context omitted.

If you're using a gateway, you have to trust the gateway.

You could probably have a pretty light wrapper around the gateway which verifies the hash. It wouldn't be as easy as simply using a gateway but still much easier than hosting/implementing an IPFS node locally

Well, to use the node locally you just run a binary, it's not like there's much to it.

Re: Paaster – Secure by default end to end encrypted pastebin

#16
post #15
post #14

Earlier quoted context omitted.

You could probably have a pretty light wrapper around the gateway which verifies the hash. It wouldn't be as easy as simply using a gateway but still much easier than hosting/implementing an IPFS node locally

Well, to use the node locally you just run a binary, it's not like there's much to it.

No, but getting at content can sometimes take a while if it's not very actively seeded, e.g. I've had to wait hours for images to load on IPFS.

Re: Paaster – Secure by default end to end encrypted pastebin

#17
post #15

Earlier quoted context omitted.

Well, to use the node locally you just run a binary, it's not like there's much to it.

No, but getting at content can sometimes take a while if it's not very actively seeded, e.g. I've had to wait hours for images to load on IPFS.

Yes, definitely. Discovery with IPFS is abysmal.
Post reply on HN