bloubz

joined 2 years ago
[โ€“] [email protected] -5 points 1 year ago (2 children)

On the day of the attack it was 200, what happened since? Not following exactly

[โ€“] [email protected] 2 points 1 year ago

You're drunk. Nobody said HTTPS

But we said IRC

[โ€“] [email protected] 1 points 1 year ago* (last edited 1 year ago) (1 children)

Ok thank you so much. What I would like to point at in the difference between having an end-to-end encryption between two recipients and at-rest encryption for information owned by Signal (in this example), is the purpose of those two different things. E2E encryption means only the two agents at each end have the mathematical possibility to decrypt the info: this is privacy by design. At-rest encryption on Signal servers of different things is a security layer meant to protect users' privacy against attackers, but Signal have the means to decrypt it, and they would do it in the normal usage of the service. This would also mean they can (and have to) transmit decrypted information to whatever agency demand them to

[โ€“] [email protected] 1 points 1 year ago (1 children)

What you call transit is a bus?

[โ€“] [email protected] 2 points 1 year ago (3 children)

Thank you for that info and the link I'll go into that. Just to summarize, if you have the knowledge and time: this is at-rest encryption? I'm not sure how it could be end-to-end encryption and at the same time enable to start new conversations with other Signal users / discovery based on name / phone number

[โ€“] [email protected] 0 points 1 year ago

I would say it is in most situations. Then they could have a reason on top of that for not actually going forward with the release after validation, no idea. I'm not from the team, just to clarify

view more: next โ€บ