Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Related Rants
ok guys, im having a little trouble diving into this, anyone wanna help?
ive got a server set up, and a client app. the client has a the server's public key built in, and encrypts the aes key/iv and sends it to the server, simple enough.
but now, after the first socket connection is over, what do i do? ive got both sides with the same aes key, but the server has multiple keys for other clients. so when the first client connects again, how do i know which key to use?
ive tried implementing a session class where there's a session id, but it doesnt work because the id must be encrypted, too. can someone help a fellow ranted out?
question
broken
bug
error
oof
mess up
problem