You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 26, 2022. It is now read-only.
Pitty you can't use passion to share password securely over any messenger that previews links.
When using Whatsapp you (should) get end-to-end encryption, so in transit it should be fine. And realistic attack vector is someone finding the link later after decrypting the communication. So having "disposable" link is a good way to secure it. But as whatsapp previews the link it withdraws the password.
If there was a rather simple password that could be shared along with the link, the password would not be withdrawn by simple preview. Or even a button press to withdraw the password would do. The password would still be safe because as soon as it's withdrawn by the other side it's gone - and that's realistically well before anyone can decrypt the conversation.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Pitty you can't use passion to share password securely over any messenger that previews links.
When using Whatsapp you (should) get end-to-end encryption, so in transit it should be fine. And realistic attack vector is someone finding the link later after decrypting the communication. So having "disposable" link is a good way to secure it. But as whatsapp previews the link it withdraws the password.
If there was a rather simple password that could be shared along with the link, the password would not be withdrawn by simple preview. Or even a button press to withdraw the password would do. The password would still be safe because as soon as it's withdrawn by the other side it's gone - and that's realistically well before anyone can decrypt the conversation.
The text was updated successfully, but these errors were encountered: