Microsoft Teams: 1 feature, 4 vulnerabilities • Hacker News Board

Re: Microsoft Teams: 1 feature, 4 vulnerabilities

#111

Post by cloudengineer94 » Wed, Dec 22, 2021, 12:21 PM UTC

vladvasiliu wrote: post #88

deng wrote: post #70

Earlier quoted context omitted.

The version numbers are lying. The Linux version is missing important features, like seeing more than 4 participants at the same time, or blurring the background. Also, for some reason it is often not possible to see the camera picture of participants when they start screen sharing (if they are using the Linux version, that is).

I don't know about the number of participants, luckily I've never been in a mammoth call. As for the background blur, it may be related to a missing feature in Electron. I seem to remember that another conferencing app (might have been zoom, not sure) didn't support this while running on Chrome/Linux, so I figure it's related. To me, the main missing feature on Linux is the "native notifications" feature (as opposed…

There's a lot of missing features like those mentioned above, is the reply option with a quote already working in Linux? Been using MacOS since the MBP14" came out and haven't booted by PopOS desktop since I'm not at home

Re: Microsoft Teams: 1 feature, 4 vulnerabilities

#112

Post by cloudengineer94 » Wed, Dec 22, 2021, 12:22 PM UTC

azalemeth wrote: post #63

cloudengineer94 wrote: post #22

Earlier quoted context omitted.

When I used to have my i9 16" MBP, the thing would go crazy and hit 90% CPU usage during web calls on Teams. I had to force myself to have it in clamshell mode to avoid crazy stuff going on.

Use it in a browser. At least you can close the browser, and to be honest desktop Chrome seems to have better power management. Of course, sometimes you then get the "Your browser is unsupported -- please use Microsoft Edge or Google Chrome" message, whilst using Chrome ...

Sadly misses important features like background blur and more on the MacOS browser..

Re: Microsoft Teams: 1 feature, 4 vulnerabilities

#113

Post by atraac » Wed, Dec 22, 2021, 12:22 PM UTC

IiydAbITMvJkqKf wrote: post #34

MS Teams is the worst software I've ever used. This is not hyperbole. A room full of monkeys on a typewriter would never create something as bad as teams.

I fully agree. I literally never felt this much hate and contempt for software as I do when I'm forced to use Teams every day. It's an absolute shitshow of a chat. And when I thought it couldn't get worse, they f*ked up ctrl+a selecting all text on Windows... I work in MS ecosystem, some MS products are great, some are really bad, most are ok-ish, but Teams is on a whole another level of bad.

Re: Microsoft Teams: 1 feature, 4 vulnerabilities

#114

Post by rapsey » Wed, Dec 22, 2021, 12:25 PM UTC

AshamedCaptain wrote: post #83

pydry wrote: post #17

In 2020 a rash of anti-zoom propaganda that I'm almost certain was driven by Microsoft led to a company-wide prohibition on using anything other than Teams "for security reasons" where i worked. This was, I am almost certain, inspired by Microsoft corporate sales getting their hooks into management. This was largely because of news stories like "end to end encryption doesnt really work as advertised" and "if you leav…

As an anecdote I know of a certain top-100 company that ditched their in-house competitor to Teams because MS made them a sweeter O365 deal. For a time management forced them to use Teams even though they were still developing AND licensing the in-house competitor to other companies. MS is really aggressive with Teams marketing (specially for large bureaucratic enterprise) and I could totally see them doing what you…

And this is why MS is the king of enterprise.

Re: Microsoft Teams: 1 feature, 4 vulnerabilities

#115

Post by deadbunny » Wed, Dec 22, 2021, 12:26 PM UTC

vladvasiliu wrote: post #88

deng wrote: post #70

Earlier quoted context omitted.

The version numbers are lying. The Linux version is missing important features, like seeing more than 4 participants at the same time, or blurring the background. Also, for some reason it is often not possible to see the camera picture of participants when they start screen sharing (if they are using the Linux version, that is).

I don't know about the number of participants, luckily I've never been in a mammoth call. As for the background blur, it may be related to a missing feature in Electron. I seem to remember that another conferencing app (might have been zoom, not sure) didn't support this while running on Chrome/Linux, so I figure it's related. To me, the main missing feature on Linux is the "native notifications" feature (as opposed…

As a long time Linux user and one that has suffered through multiple versions of teams/slack/zoom/Google Meet I was pleasantly surprised with Google Meet (in chromium) for video calls. It worked flawlessly, adapted really well to a super wide monitor (actually used the space well), and had the background blurring/replacement features that get stripped from most linux clients, the only downside was that it didn't like screensharing in Firefox.

Re: Microsoft Teams: 1 feature, 4 vulnerabilities

#116

Post by isodev » Wed, Dec 22, 2021, 12:27 PM UTC

I work with several large organisations, all using Teams.

In every instance, the previous solution (Slack/Zoom/Discord) was replaced by Teams following higher management making the switch for reasons like "it's included in Office 365" or a new hire influencing the migration to Microsoft solutions.

In every instance, the application was/is not well received by the employees - it's slow, buggy, crazy complicated and generally doesn't feel "right".

Microsoft is good at channeling security topics for their PR, but at the end of the day they make software, just like everybody else (and this software is subject to bugs, just like everybody else).

It's really disappointing that the vulnerabilities have not yet been addressed...

Re: Microsoft Teams: 1 feature, 4 vulnerabilities

#117

Post by rleigh » Wed, Dec 22, 2021, 12:27 PM UTC

aspaviento wrote: post #100

IiydAbITMvJkqKf wrote: post #34

MS Teams is the worst software I've ever used. This is not hyperbole. A room full of monkeys on a typewriter would never create something as bad as teams.

Linux version: - some times the left arrow to move the cursor doesn't work - some times images are displayed and others not - can't have more than 4 people on screen in a video call - the scroll is completely broken - can't get out of the immersive mode without closing the process (the back arrow doesn't work) And the list goes on and on...

Not Linux-specific! The Windows version suffers from at least 1, 2 and 4 in my experience.

Re: Microsoft Teams: 1 feature, 4 vulnerabilities

#118

Post by markus_zhang » Wed, Dec 22, 2021, 12:28 PM UTC

Teams has a bunch of anti-features that I have to click off, including this one.

The micro update also tend to break something. For example a November patch broke list in chat, a futher one broke list in general. I have to enter the edit mode every time I want to enter a list.

I think the ability to use ''' to enter code snippets was also broken a while ago, and in another patch the indentation of such code block was gone as well.

I think they are trying to force us to use the editor mode.

Re: Microsoft Teams: 1 feature, 4 vulnerabilities

#119

Post by vegai_ » Wed, Dec 22, 2021, 12:29 PM UTC

IiydAbITMvJkqKf wrote: post #40

iso1631 wrote: post #3

Earlier quoted context omitted.

Make all software which isn't released as open source liable for the cost of security breaches?

Why should open source software be exempt? If your data gets leaked/abused the license of the software used does not matter in the slightest. If anything, freeware (whether open source or proprietary) should be exempt from costs. You get what you pay for, after all.

Make everyone culpable but make the maximum amount of damages never be higher than what income the software generated.

Re: Microsoft Teams: 1 feature, 4 vulnerabilities

#120

Post by _kbh_ » Wed, Dec 22, 2021, 12:30 PM UTC

llarsson wrote: post #55

_kbh_ wrote: post #27

Earlier quoted context omitted.

I'm still reeling from the fact that the macOS teams app have a local privilege escalation to root vulnerability for a while. Why does ANY part of teams run as root?.

Probably to auto-update? I can't think of any other even remotely valid reason.

Yeah it was the update, but even thats a bad reason to be honest, the only thing that changes without the privilege helper is the user gets a prompt for an update.