i started a (very niche) private messaging protocol & little CLI app demo. i’m no security expert, so any feedback or questions would be appreciated.
the gist is an ephemeral message exchange without identities. the goal is ultimate deniability.
the interesting (and weird) part is that messages are encrypted but not authenticated. this means an imposter could show up if they know the shared secret. otoh this means you can deny anything you say.
Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.
In this community everyone is welcome to post links and discuss topics related to privacy.
much thanks to @gary_host_laptop for the logo design :)
interesting point! i chose symmetric shared key because it means you can’t prove who sent what message.
the shared secret does add some authentication, which i think is necessary. the goal is it only creates enough to be practical (a random person can’t eavesdrop), but not enough to prove things. messages themselves still aren’t authenticated by any one person.
.
you’re not wrong, but that’s just the trade off that has to be made, i think. it’s the only way i can think to do it, at least. need -some- authentication for practical usability.
your gpg example removes the deniability since it proves who wrote the message.
.