Live data from Hacker News

Zoom will enable waiting rooms by default to stop Zoombombing

techcrunch.com

31–40 of 51 posts

Re: Zoom will enable waiting rooms by default to stop Zoombombing

#31
"Building development teams that include skeptics and realists, rather than just visionary idealists, could keep ensure products get safeguarded from abuse before rather than after a scandal occurs."

On the face of it this sounds fair, but the problem is that being "sceptical" and "realistic" is far easier and requires much less effort than being "visionary"[1]. Too much of the former early on can really suck the life out of a team, increasing the risk that the product fails, or is simply never built.

Safeguarding from abuse is much better achieved by systematic thinking and discipline (which are learned skills) rather than hiring "realists" who might simply turn out to be whiners and energy vampires.

As much as Zoom is currently in the spotlight, and I can't say I'm overjoyed by a number of the issues I've read about (e.g., encryption keys being passed through Chinese servers?!??), many of them are the problems of success, and every successful company has or will experience their fair share of those.

[1] I might also add that it's far easier to commentate and to critique than to do, eh, TechCrunch?

Re: Zoom will enable waiting rooms by default to stop Zoombombing

#32

Waiting rooms don't help because you don't see any identifying information. My sister's call got zoombombed even with a moderated waiting room. They were trying to keep within their university's students, but they couldn't see the email addresses associated with the zoom user name in the waiting room, so a griefer got through.

Zoom meetings created on my company's account can only be joined by people logged in through my company's SSO (unless the meeting is explicitly set to open).

Universities typically have SSO, so this don't seem like a hard thing for them to implement.

Re: Zoom will enable waiting rooms by default to stop Zoombombing

#33
I’ve used a lot of these tools, and I have to admit, Zoom is the best.

As for the Zoombombing, I can’t say that I am surprised. All you really need is the URL.

And all the other tools are like that too. Sure, you can require a separate passcode, but damn it, it’s like trying to figure out rocket science to enter the passcode.

1) you have to dial the number

2) you have to punch in the meeting ID

3) you have to punch in the passcode.

4) ERROR. You flipped it, and used the passcode for the meeting ID instead. Aargh.. frustration.

5) Forget about the passcode. Just let everyone in that has the meeting ID. And monitor if there’s someone unknown on the line.

Re: Zoom will enable waiting rooms by default to stop Zoombombing

#34
My understanding was that chats simply had too easy to guess names.

Would this be solved by generating chat names through a cryptographic hash algorithm?

I have google docs that are edible by anyone with the link and I’m kinda assuming that the link is as hard to guess as logging in with a password.

Am I completely off and in dire need of reevaluating my personal web security?

Re: Zoom will enable waiting rooms by default to stop Zoombombing

#35

Earlier quoted context omitted.

Except the search space is much, much, larger.

Don't we want the search space larger? That way it is harder to wardial? YouTube has 11 characters composed of [a-Z] and [0-9]. (26*2+10)^11 is a pretty big number. There's no reason it couldn't be longer.

It would also make it harder to dial by phone, if you need to do so.

Re: Zoom will enable waiting rooms by default to stop Zoombombing

#36
post #2

> Starting April 5th, it will require passwords to enter calls via Meeting ID A meeting id with a password is semantically the same as a longer meeting id (or a meeting id with a character space larger than just digits). I wish they'd do that instead (make meeting ids longer) so I could continue to enter my company meetings with only a link but not have to worry about getting wardialed.

You will be able to enter with only a link, the url looks like:

https://tenant.zoom.us/j/123123123?pwd=QlR0cXZkYXBDS0txYzJRR...

The password is an encoded version of the password set by the host.

Re: Zoom will enable waiting rooms by default to stop Zoombombing

#37

Earlier quoted context omitted.

Except the search space is much, much, larger.

What is larger than what? With the most straightforward way for "meeting id with a password" and "longer meeting id" to be the same, both methods provide the exact same expansion in search space compared to the previous implementation, and they have the exact same search space as each other. (That method being: concatenate shortid and password to get longid)

Here’s an ignorant question. I see this comment all the time, that an ID and PIN is exactly the same as a longer ID, but is it actually true?

I get the logic of it, but in a practical sense doesn’t it have the potential to be different? For example, if you have to enter a correct ID, wait, and then get prompted for a password, couldn’t that potentially slow down an attacker?

Alternately, couldn’t a bunch of correct meeting ID’s followed by incorrect PINs present an opportunity to flag the ID as under attack, or give a prompt to a host that would spur inquiry, or something?

Perhaps I’m wrong about this but it seems like there are some non trivial differences between the two.

Re: Zoom will enable waiting rooms by default to stop Zoombombing

#39

"Building development teams that include skeptics and realists, rather than just visionary idealists, could keep ensure products get safeguarded from abuse before rather than after a scandal occurs." On the face of it this sounds fair, but the problem is that being "sceptical" and "realistic" is far easier and requires much less effort than being "visionary"[1]. Too much of the former early on can really suck the lif…

I'm so tired of these types of comments. "The reason you have this issue is you're missing X", "Yeah but if we only had X we wouldn't have been able to do this at all!", "Yes, which is why I said you should have more X, not completely abandon everything but X".

Let's be clear: The issues that Zoom is having were seen by other businesses in the same industry decades ago. At a time where every other messaging system in the world has been moving to end to end encryption - even facebook, Zoom is still lying about it to customers. It doesn't require a room full of sceptics to figure that out, it requires some sort of development process that involves a the tiniest bit of thought before rushing out a feature - a culture that is apparently consistently lacking in large parts of silicon valley.

Btw, If you think that what we've seen over the last few years is that commentating on tech is an easy career to make a living at, you haven't been paying attention to the state of journalism.

Re: Zoom will enable waiting rooms by default to stop Zoombombing

#40

"Building development teams that include skeptics and realists, rather than just visionary idealists, could keep ensure products get safeguarded from abuse before rather than after a scandal occurs." On the face of it this sounds fair, but the problem is that being "sceptical" and "realistic" is far easier and requires much less effort than being "visionary"[1]. Too much of the former early on can really suck the lif…

I don't know why skepticism and realism are viewed as "easy" when both are skills that require practice and education to apply accurately and consistency. What is so much harder about being "visionary" if all that means is coming up with ideas? Obviously what's valuable is coming up with ideas that can be executed on safely and easily, and Zoom completely shit the bed on safety here.

A team full of visionaries will never get anything shipped at release quality. I've worked with plenty of them. You don't need to hire a bunch of depressing pessimists but if you don't have skeptics and realists to keep your team's velocity under control you're never going to hit quality targets.

Imagine there being multiple valuable skills in an industry, like critique, commentary, planning, debugging, testing, engineering, design, and ideation!

Post reply on HN