Paaster – Secure by default end to end encrypted pastebin
1–10 of 18 posts
Re: Paaster – Secure by default end to end encrypted pastebin
#2> Can I trust a instance of paaster not hosted by me?
> No. Anyone could modify the functionality of paaster to expose your secret key to the server. We recommend using a instance you host or trust.
That's refreshingly honest, but I hope that some day a technology like WhatsApp / Cloudflare's recently released "Code Verify" extension helps to solve this.
https://inside.com/campaigns/inside-dev-2022-03-11-31674/sec...
Re: Paaster – Secure by default end to end encrypted pastebin
#3Text input seems to be broken on mobile? (iOS Chrome)
Re: Paaster – Secure by default end to end encrypted pastebin
#4Pinterest open sourced a similar tool a few years back - Snappass: https://github.com/pinterest/snappass
Re: Paaster – Secure by default end to end encrypted pastebin
#5I wish there was a way to create a link which doesn't contain the password so I can send the password separately.
Re: Paaster – Secure by default end to end encrypted pastebin
#6Might as well use WebRTC to establish realtime e2e p2p pasting.
Re: Paaster – Secure by default end to end encrypted pastebin
#7> Can I trust a instance of paaster not hosted by me? > No. Anyone could modify the functionality of paaster to expose your secret key to the server. We recommend using a instance you host or trust. That's refreshingly honest, but I hope that some day a technology like WhatsApp / Cloudflare's recently released "Code Verify" extension helps to solve this. https://inside.com/campaigns/inside-dev-2022-03-11-31674/sec...
I think that providing API to be used by standalone clients is far more better approach
Re: Paaster – Secure by default end to end encrypted pastebin
#8I 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
Re: Paaster – Secure by default end to end encrypted pastebin
#9> Can I trust a instance of paaster not hosted by me? > No. Anyone could modify the functionality of paaster to expose your secret key to the server. We recommend using a instance you host or trust. That's refreshingly honest, but I hope that some day a technology like WhatsApp / Cloudflare's recently released "Code Verify" extension helps to solve this. https://inside.com/campaigns/inside-dev-2022-03-11-31674/sec...
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.
Re: Paaster – Secure by default end to end encrypted pastebin
#10> Can I trust a instance of paaster not hosted by me? > No. Anyone could modify the functionality of paaster to expose your secret key to the server. We recommend using a instance you host or trust. That's refreshingly honest, but I hope that some day a technology like WhatsApp / Cloudflare's recently released "Code Verify" extension helps to solve this. https://inside.com/campaigns/inside-dev-2022-03-11-31674/sec...
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?