Signal Server code on GitHub is up to date again

Re:Signal Server code on GitHub is up to date again by danpalmer on Wednesday April 07, 2021 @11:14AM (#26726088)

I think the argument would be that with end-to-end encryption this is unnecessary, which is good because it's impossible.

There's a counter-argument that there is still useful metadata a server can glean from its users, but it's certainly minimised with a good protocol... like the Signal protocol.

[ Parent | on HN ]

Re:Signal Server code on GitHub is up to date again by cortesoft on Wednesday April 07, 2021 @01:22PM (#26727901)

Wait, how would end-to-end encryption help this problem at all? I agree that it is impossible (currently), but not sure how E2E helps anything?

E2E encryption only helps you verify WHO you are connecting to, not what they are doing with your connection once it is established.

[ Parent | on HN ]

Re:Signal Server code on GitHub is up to date again by iudqnolq on Wednesday April 07, 2021 @03:55PM (#26730285)

Because the other end in E2E is your friend's phone, not a server. We call end-to-server encryption "in-flight" encryption.

[ Parent | on HN ]

Re:Signal Server code on GitHub is up to date again by cortesoft on Wednesday April 07, 2021 @06:00PM (#26731962)

Ah, ok I misunderstood

[ Parent | on HN ]

Re:Signal Server code on GitHub is up to date again by gsich on Wednesday April 07, 2021 @01:39PM (#26728143)

Because it doesn't matter what the server does in terms of message content.

[ Parent | on HN ]