Live data from Hacker News

The facts around Zoom and encryption for meetings/webinars

blog.zoom.us

111–120 of 145 posts

Re: The facts around Zoom and encryption for meetings/webinars

#111

Earlier quoted context omitted.

> Oh, come on, that’s not the same thing at all. Here Zoom actively decrypts the stream so that it’s compatible with non-Zoom clients and then advertises it as end-to-end I took issue with a specific definition that precludes both products. I didn't say that both products use the same protocol. > you’re comparing it to (outdated, FYI) information Has the implementation changed in any way that makes it meet the defini…

> I took issue with a specific definition that precludes both products. This isn’t the first time you’ve tried to compare Zoom and iMessage; it’s just that I chose this one to respond to.

Have I made a false comparison anywhere else, or was the comparison valid as in this case?

Re: The facts around Zoom and encryption for meetings/webinars

#112
post #28

Earlier quoted context omitted.

The video must be decrypted to do the scaling, transcoding, and dynamic bitrate adjustment for different platforms and network speeds – there's no way around this. All of the group video providers will be decoding video on the server to achieve the reliability everyone wants.

The clients can dynamically adjust their sending rate and resolution. It is pretty easy to downgrade your video when not talking. Its also possible to number and label the encrypted frames (I frames or B frames), allowing decimation for low bandwidth clients without recoding, which is expensive and slow. There are also ways to send additive resolution streams -- a base stream and additional detail layers (multiresolu…

Clients already do this yes, but to achieve the reliability that zoom is renowned for you also need to dynamically adjust what is sent _TO_ individual clients

Re: The facts around Zoom and encryption for meetings/webinars

#113
post #28

Is there any evidence that other teleconferencing solutions meet or exceed what's described in this blog article? I just find the Zoom hate weird. We have no reason to think Teams, Hangouts, or anything else does anything close to or better than this. Lots of reason to suspect they probably don't. Don't get me wrong, I think the scrutiny is good, and will lead to positive outcomes. But we probably need to scrutinize…

The video must be decrypted to do the scaling, transcoding, and dynamic bitrate adjustment for different platforms and network speeds – there's no way around this. All of the group video providers will be decoding video on the server to achieve the reliability everyone wants.

The Zoom article we are discussing here claims they do not do that.

Re: The facts around Zoom and encryption for meetings/webinars

#114
post #17

If this pisses you off, it's worth noting that Telegram group chats have the same property, and that Telegram argues forcefully (and falsely) that what they're doing does meet the definition of "end-to-end encryption".

This statement is simply false, Telegram has never claimed group chats are "end-to-end encrypted". Only secret chats are claimed to be and proven to be.

https://telegram.org/faq#q-so-how-do-you-encrypt-data

As early as 2017, they broadly and publicly advertised that they are NOT end-to-end encrypted 'by default'.

https://telegra.ph/Why-Isnt-Telegram-End-to-End-Encrypted-by...

Re: The facts around Zoom and encryption for meetings/webinars

#115
post #15

wow!! zoom you were better off not having written that blog. you guys are some shady assholes. Everything from the text to the graphics are intended to mislead and obscure. I don’t think i’ve seen a company act in such bad faith since theranos was a thing.

In my opinion they seem better off from this blog post. For example yesterday I read this comment[1] and it seemed to say Zoom always decrypts the content on the servers, in which case it's very bad to say it's "end-to-end encrypted". But this blog post explains that if you don't have any external connector attached, it in fact is end-to-end encrypted, no false advertising. When you have an external connector attache…

> if you don't have any external connector attached, it in fact is end-to-end encrypted,

It doesn't say that all.

Re: The facts around Zoom and encryption for meetings/webinars

#116
post #66
post #63

Earlier quoted context omitted.

This. They really should look into what end-to-end encryption means. As the parent says, they can implement their app however they please, but they should get their feature list straight.

Zoom knows exactly what end-to-end encryption means, and always has. Most likely their marketing group didn't like their engineering group telling them this nice buzzword didn't apply and intentionally chose to misuse it.

You see the exact same thing with HIPAA.

"End-to-end" is often (incorrectly) used to simply describe SSL/TLS protection from web browser to server. Not technically wrong, but also not how most developers understand the term.

Re: The facts around Zoom and encryption for meetings/webinars

#117

Earlier quoted context omitted.

The clients can dynamically adjust their sending rate and resolution. It is pretty easy to downgrade your video when not talking. Its also possible to number and label the encrypted frames (I frames or B frames), allowing decimation for low bandwidth clients without recoding, which is expensive and slow. There are also ways to send additive resolution streams -- a base stream and additional detail layers (multiresolu…

Clients already do this yes, but to achieve the reliability that zoom is renowned for you also need to dynamically adjust what is sent _TO_ individual clients

Can the clients not advise the server what bandwidth and packet loss rate they are seeing, so the server can adjust their traffic rate? There is no reason not to allow a signalling channel separate to the E2E encrypted data channels.

Re: The facts around Zoom and encryption for meetings/webinars

#118
post #114
post #17

If this pisses you off, it's worth noting that Telegram group chats have the same property, and that Telegram argues forcefully (and falsely) that what they're doing does meet the definition of "end-to-end encryption".

This statement is simply false, Telegram has never claimed group chats are "end-to-end encrypted". Only secret chats are claimed to be and proven to be. https://telegram.org/faq#q-so-how-do-you-encrypt-data As early as 2017, they broadly and publicly advertised that they are NOT end-to-end encrypted 'by default'. https://telegra.ph/Why-Isnt-Telegram-End-to-End-Encrypted-by...

Your refutation of my claim is an article that claims Telegram's use of TLS encryption makes it more secure than its competitors, and links to another article going into even more detail about that ridiculous claim. I feel comfortable with where it leaves my argument standing.

Re: The facts around Zoom and encryption for meetings/webinars

#119
post #41

How could they guarantee end-to-end if not all gadgets support encryption?! Let's demand end-to-end encryption for people connecting via FAX machines to read only the comments. Of course connecting via unreliable machines / protocols means Zoom must have some bridge on their side somewhere. In light of this post it looks like for the majority of users it is end-to-end encrypted. I don't even use Zoom, but really, the…

So don't claim you do end-to-end encryption? And don't put a green lock signifying end-to-end encryption in the client when you aren't actually doing end-to-end encryption? You act as if they're the innocent victim here. They literally made indicators and showcase them in the client to signify encryption when they aren't doing it. If you send your kids to school and the teacher says they're being fed everyday, but th…

Not disputing your core point but I think its important not to confuse the green padlock with end-to-end encryption. It only tells you that the data is sent over a secure connection to the server. The transmitted data itself is not encrypted.

Re: The facts around Zoom and encryption for meetings/webinars

#120
post #41

Earlier quoted context omitted.

So don't claim you do end-to-end encryption? And don't put a green lock signifying end-to-end encryption in the client when you aren't actually doing end-to-end encryption? You act as if they're the innocent victim here. They literally made indicators and showcase them in the client to signify encryption when they aren't doing it. If you send your kids to school and the teacher says they're being fed everyday, but th…

Not disputing your core point but I think its important not to confuse the green padlock with end-to-end encryption. It only tells you that the data is sent over a secure connection to the server. The transmitted data itself is not encrypted.

I'm not sure what you mean by the "transmitted data itself is not encrypted". The payload (the packet above layer 5) is encrypted. The distinction people need to make is who the _confidentiality_ applies to. The communications are not confidential between the callers/callees. The communications are only confidential between Zoom servers and the users. The provider sees all.

I think you understand this but maybe you didn't word it quite correctly. Never confuse confidentiality with encryption is the take-away that we as an industry need to do a better job telling our users about.

Edit: Well the communication isn't ONLY confidential between users & zoom but I'm simplifying for point of brevity.

Post reply on HN