Poa.st / Chudbuds.lol General Discussion Thread - !! Poa.st and Bae.st have been compromised, all direct messages have been leaked. !!

  • 🐕 I am attempting to get the site runnning as fast as possible. If you are experiencing slow page load times, please report it.
josiah.png
AHAHAHAHAHAHAHAHAHA
RIP Jersh.
 
  • Like
  • Informative
  • Lunacy
Reactions: Iwasamwillbe, Big Miss Steak, Marchesa of the Vast and 23 others
I'm not enough of an autist to know about the inner workings of Fediverse services like Poast but I do very explicitly remember Null stating on MATI that you should never, ever, EVER treat Fediverse/KF messages as private in any way because they aren't encrypted. Glad to see he was right to hammer that point home.

Also, another reminder to do your weird deviant shit in real life behind closed doors and not on the Internet using venues like the Poast DM system because it will almost always come back to bite you. Though, admittedly I hope people never learn to follow that advice because this site and the spectacles on it probably wouldn't exist if they did.

ETA: i opened the /cow/ thread briefly and was immediately greeted by a plethora of very humiliating dick pics. my sides have breached the stratosphere. i cannot wait to see how much good shit comes out of this
 
Last edited:
  • Like
  • Agree
  • DRINK!
Reactions: WebLurker, Wright, Pee Cola and 20 others
kainvnod said:
> Have messages encrypted on the server
> In order to make them readable to the user, server needs to decrypt them
> Key for decrypton is stored on the server
> Server gets compromised
Click to expand...
So you encrypt the DM key with another key, call the key for that the KEK (key encryption key). The KEK is derived from the user's password and never touches the server. The user downloads the encrypted blob containing the key for their DMs, they decrypt it to get the DM key, they request the encrypted blob from the server, and then they decrypt their DMs. That way plaintext DMs aren't stored on the server.

When they need to reset their password, they download the encrypted DM key, decrypt it with the key derived from their old password, encrypt it with the key derived from their new password, and upload that along with the password change request.

Ideally DMs would be E2EE, not just encrypted at rest, but that would require getting all the different fediverse server implementations to play nicely.
 
  • Like
  • Informative
Reactions: Carpenter Trout, The Ghost of Kviv, Procrastinhater and 7 others
So graf is ok with people signing their "little brother", a literal CHILD, up to poast. Blah blah we can't verify it's a kid but you wouldn't really use "little brother" for anybody that's over 18. He's perfectly ok with fucking CHILDREN being exposed to what gets put on poast publicly, what a faggot. Hope both graf and that poor kids brother who decided to help get him on poast meet the rope soon, you're both a waste of oxygen.

1.png
 
  • Informative
  • Like
  • Horrifying
Reactions: UnsufficentBoobage, Pee Cola, Flanker and 15 others
  • Informative
  • Thunk-Provoking
  • Like
Reactions: WebLurker, Marchesa of the Vast, Procrastinhater and 14 others
inception_state said:
So you encrypt the DM key with another key, call the key for that the KEK (key encryption key). The KEK is derived from the user's password and never touches the server. The user downloads the encrypted blob containing the key for their DMs, they decrypt it to get the DM key, they request the encrypted blob from the server, and then they decrypt their DMs. That way plaintext DMs aren't stored on the server.

When they need to reset their password, they download the encrypted DM key, decrypt it with the key derived from their old password, encrypt it with the key derived from their new password, and upload that along with the password change request.

Ideally DMs would be E2EE, not just encrypted at rest, but that would require getting all the different fediverse server implementations to play nicely.
Click to expand...
or just go outside and talk in real life
 
  • Like
  • Winner
  • Optimistic
Reactions: Pee Cola, Carpenter Trout, Owlbear and 24 others
inception_state said:
So you encrypt the DM key with another key, call the key for that the KEK (key encryption key). The KEK is derived from the user's password and never touches the server. The user downloads the encrypted blob containing the key for their DMs, they decrypt it to get the DM key, they request the encrypted blob from the server, and then they decrypt their DMs. That way plaintext DMs aren't stored on the server.

When they need to reset their password, they download the encrypted DM key, decrypt it with the key derived from their old password, encrypt it with the key derived from their new password, and upload that along with the password change request.

Ideally DMs would be E2EE, not just encrypted at rest, but that would require getting all the different fediverse server implementations to play nicely.
Click to expand...
Good idea.
Do you even need a 2nd key with this approach? Just generate the private key on the fly whenever needed from the password, but put the public one out there for everyone to encrypt messages sent to you.
 
  • Like
Reactions: Procrastinhater
2 Faces 2 Colours said:
Literally fuck this piece of shit website I could barely tolerate the content in there and now they let everyone's information get leaked?!
Click to expand...
No, they only let DMs get leaked. Which, if you weren't being a degenerate Discord fag weirdo on the platform actually seems to mean that you've been unaffected by the hack, at least for now.
 
  • Like
  • Agree
  • Informative
Reactions: Mourning_Cloak, Procrastinhater, AmateurComedicTaxidermist and 7 others
Cats said:
That's why I'm Cats, that's why I only ever post cats and send people photographs of cats. you can't get mad at a cat. you can't be embarrassed by sending a cat.
Click to expand...
I get mad at my cat when he insists on invading my personal workspace and lying on my keyboard. Just sayin'; even you cats are not immune. Take note.
 
  • Feels
  • Like
  • Agree
Reactions: duckbutter&toejamsandwich, Pee Cola, Iwasamwillbe and 12 others
kainvnod said:
Good idea.
Do you even need a 2nd key with this approach? Just generate the private key on the fly whenever needed from the password, but put the public one out there for everyone to encrypt messages sent to you.
Click to expand...
That's basically how PGP works. You have a public/private key pair. To send data, you generate a random symmetric key, encrypt it with the receiver's public key, send the encrypted data and encrypted key over the wire. Then they decrypt the symmetric key using their private key and use that to decrypt the message. It's a bit more complicated than what you described but orders of magnitude more efficient. Public key cryptography is really slow compared to symmetric algorithms like AES.

The nice part about the KEK structure I described above is that do don't have to read/write a ton of data to change passwords. All you have to do is encrypt and decrypt a tiny amount of data (keys). With something like what you outlined, if you wanted to change your password you would need to download all the encrypted data from the server, decrypt it with the old key and then re-encrypt it with the new key. That adds up to a lot of work and bandwidth if you have say 1 gb of DMs, or even 10,000 users with 10 mb of DMs each.

The gold standard is really something like the Signal protocol though: https://www.signal.org/docs/specifications/doubleratchet/. E2EE, post-compromise security, lots of other really nice features.
 
  • Like
  • Informative
Reactions: WebLurker, Iwasamwillbe, Procrastinhater and 7 others
You must log in or register to reply here.
Back