Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Zoom zero-day discovery

blog.malwarebytes.com

Post reply on HN
Print view View original

241–246 of 246 posts

Re: Zoom zero-day discovery

#241

Post by anoncake »

twobitshifter wrote: post #97
_nickwhite wrote: post #50

Earlier quoted context omitted.

My biggest gripe about Teams is what a memory hog it is. Mine is currently sitting idle (been on vacation all week) at nearly 1GB. Compare this to Zoom, which is idling at just over 100MB. Teams is literally taking up 10 times more RAM than Zoom just running in the background.

In Microsoft’s defense Teams is an electron (or electronesque) app and offers quite a bit more than Zoom in terms of features. The fact that it uses so much RAM is expected when you consider it as another copy of chrome.

I don't see how that's a defense. MS choose to use Electron.

Re: Zoom zero-day discovery

#242

Post by rijoja »

aYsY4dDQ2NrcNzA wrote: post #229
interestica wrote: post #175

Earlier quoted context omitted.

I really wish there was a changelog for headlines. Too often I see a critique like this and I have to figure out if the comment is referring to the current headline or a previous version. And, if the headline has already unknowingly been 'corrected', it leaves me wasting time trying to figure it out within that framing. And it shouldn't be the responsibility of the poster necessarily to quote it -- because there's no…

> I really wish there was a changelog for headlines. While we’re talking feature requests, I think each submission should offer an optional second weblink, reserved specifically for the “original” or “source” URL. It bothers me when the link is changed after lots of comments reference the previous one.

good luck with that when was the last time something changed on HN? My belief which is nothing but an educated guess is that the latest addition was the anti-procrastinate switch.

Re: Zoom zero-day discovery

#243

Post by rijoja »

gowld wrote: post #86
rijoja wrote: post #77

Earlier quoted context omitted.

I don't really think a communication from Malwarebytes is the place for sarcastic comments. Lets say if you are working with a US government this could have enormous implications. I've talked to a lot of clients who ditched Zoom for Microsoft Teams due to their earlier mistakes. Also I find it funny that the heading "Not patched yet" is solved by the headline "Security done right". Lets say if you are working with a…

Teams is exploitable too.

Did I say that it wasn't?

Re: Zoom zero-day discovery

#244

Post by Rendello »

d110af5ccf wrote: post #222
Rendello wrote: post #91

Earlier quoted context omitted.

I wonder if the OS world will move towards lightweight but unforgiving sandboxing like OpenBSD's `pledge` and `unveil` system calls. It's crazy to me that most software is still completely fine to run around and set things as fire the instant it's compromised! This is about the implementation in the SerenityOS but it's my favourite explanation so far: https://awesomekling.github.io/pledge-and-unveil-in-Serenity...

Doesn't the equivalent already exist in Linux? BPF seccomp filters have been around since ~2012 ( https://lwn.net/Articles/656307 ). There's also SELinux and friends (ie Linux Security Modules).

Pledge was created as a response to low `seccomp` (Linux) and `capsicum` (FreeBSD) usage in the wild. Pledge trades off granularity for ease-of-use, and has seen quite a bit of adoption despite OpenBSD being a small ecosystem.

As a Linux-based programmer who hasn't quite delved into the UNIX internals world, knowing that I have to write my own BPF filter or do some crazy stuff with file descriptors (in the case of capsicum) is enough to scare me. But on OpenBSD, I added `pledge` and `unveil` calls to all my silly Python chat bots in 15 mintes

Re: Zoom zero-day discovery

#245

Post by d110af5ccf »

Rendello wrote: post #244
d110af5ccf wrote: post #222

Earlier quoted context omitted.

Doesn't the equivalent already exist in Linux? BPF seccomp filters have been around since ~2012 ( https://lwn.net/Articles/656307 ). There's also SELinux and friends (ie Linux Security Modules).

Pledge was created as a response to low `seccomp` (Linux) and `capsicum` (FreeBSD) usage in the wild. Pledge trades off granularity for ease-of-use, and has seen quite a bit of adoption despite OpenBSD being a small ecosystem. As a Linux-based programmer who hasn't quite delved into the UNIX internals world, knowing that I have to write my own BPF filter or do some crazy stuff with file descriptors (in the case of ca…

Yeah the idea of wrangling raw BPF is a bit daunting. Just FYI, libseccomp (https://github.com/seccomp/libseccomp) exists to abstract away all the BPF stuff. It even comes prepackaged by the major distros (ex https://packages.debian.org/sid/libseccomp2) so you don't even have to compile it yourself.

Re: Zoom zero-day discovery

#246

Post by samus »

chollida1 wrote: post #192
jacquesm wrote: post #44

Earlier quoted context omitted.

Same here, zoom is on our 'ban' list. And MS teams is getting there, what a load of crap that is, it is so buggy it is embarrassing.

I get that your just some random internet person but I'll bit and assume I'm not being trolled..... what's so bad about team's security that its almost on your ban list?

My company forbids using Teams for data that would be subject to GDPR. Guess they don't trust the Privacy Shield, but it still boggles the mind why we didn't go then for a solution that can be deployed on-premises.
Post reply on HN