3 ms·

What kind of client side encryption does this use?

• stabbles 7y ago
  It's just some symmetric encryption with a randomly generated key (in the hash of the generated url). Meaning you now have to find a way to safely send this URL ... and you are right where you started. It's no safety at all.
  • johnmarcus 7y ago
    not really true. You can send the link via slack. the person would then need to actually be listening to your slack messages in real time, which is a threat but a very minor one. What this protects against is the real password being visible in Slack logs and archive history for all to see. so, it doesn't solve every problem, but it does solve most real problems.
  • ben509 7y ago
    It's adding self-destructing messages, so there's that. But, yeah, the lack of protection from eavesdropping is a show stopper.
• GlitchMr 7y ago
  AES-128-CCM