It’s not accurate because it will be an optional feature.
QuarterSwede@lemmy.world
on 11 May 14:50
nextcollapse
Yeah, not seeing this as the big bad everyone thinks it is. We regularly have Teams meetings with other companies when they’re sharing their proprietary info. I’m okay with a screen capture disabling function just like we’d want to use from time to time.
patatahooligan@lemmy.world
on 11 May 17:12
collapse
From the article:
Those joining from unsupported platforms will be automatically placed in audio-only mode to protect shared content.
and
“This feature will be available on Teams desktop applications (both Windows and Mac) and Teams mobile applications (both iOS and Android).”
So this is actually worse than just blocking screen capturing. This will break video calls for some setups for no reason at all since all it takes to break this is a phone camera - one of the most common things in the world.
Considering most of the organizations using Teams bear the “enterprise” warning label I wouldn’t count on whoever you are talking to having the ability (as in permissions, not stupidity) to turn it off.
partial_accumen@lemmy.world
on 11 May 14:52
nextcollapse
What part of the headline suggests the feature is mandatory? Assuming its mandatory doesn’t pass the critical thinking “sniff test” because what is sensitive is purely subjective. Microsoft has no way of knowing what data you consider sensitive. As in, there’s no way Microsoft could make it mandatory on only “sensitive” data.
That’s a charitable reading, and likely justified by the article, but based only on the phrasing, it’s just as likely to read that as assuming Microsoft will block all content in order to ensure the safety of sensitive data. Sniff tests have to be adapted when things tend to stink in general, or companies regularly try to cover up their smell.
partial_accumen@lemmy.world
on 11 May 20:56
collapse
it’s just as likely to read that as assuming Microsoft will block all content in order to ensure the safety of sensitive data.
Hang on. If you’re rejecting rational use cases that companies use Teams for, then your assumption must be that Microsoft will block ALL screen capture when a teams meeting is occurring whether its of the Teams meeting content being shared or not. As in, even the presenter would be blocked from doing screen captures of their own system. Why isn’t that your conclusion?
Why are you, again, from the headline only, assuming that screen capture would mandatory for just content shared to you by a Teams presenter? You chose a middle ground, but why didn’t you choose full blocking?
Sniff tests have to be adapted when things tend to stink in general, or companies regularly try to cover up their smell.
So are you adapting yours back now because yours was proven wrong?
Well, ‘proven wrong’ is a bit of a stretch. ‘will soon block screen capture’ doesn’t leave a lot of wiggle room, but also isn’t that crazy to read into it that maybe it would block screen capture on the presenters screen… especially if you grant that it might only have control over the teams portion of the screen. I’ve had it black out windows on my own machine even when not presenting.
But further than that, it’s not fair to say everything has to be read only from the most or the least charitable viewpoints. Context is a thing and if you’re even a little bit familiar with the history of software enshittification, it’s reasonable to assume that an uncharitable reading is fair without assuming the app will now melt your computer for spare parts if you try something that is disallowed. ‘As shitty as we can get away with’ might be a good rule of thumb.
thisbenzingring@lemmy.sdf.org
on 11 May 16:14
collapse
this is true, if you have privacy categories setup and you use something that isn’t rated for someone, they won’t be able to see it. Kinda like permissions. Government and Medical environments is where I’ve seen it applied. It’s a beast to implement.
This feature will be available on Teams desktop applications (both Windows and Mac) and Teams mobile applications (both iOS and Android).
cupcakezealot@lemmy.blahaj.zone
on 11 May 22:40
nextcollapse
i trust signing in through the browser on linux will be supported since that’s the official way to use teams on linux
WhyJiffie@sh.itjust.works
on 12 May 00:40
collapse
except on firefox of course, because fuck you for even trying to protect a little bit of your privacy
iknowitwheniseeit@lemmynsfw.com
on 12 May 07:04
collapse
I use Edge on Linux for working with Microsoft stuff on my corporate laptop. For everything else I use Firefox there. Privacy preserved, basically.
WhyJiffie@sh.itjust.works
on 12 May 10:39
collapse
Privacy preserved, basically.
only if the browser cannot run in the background, and it cannot access any of your fikes, the DBus of your regular user’s session, and other facilities
You lock it with flatpak as much as you can. Also, don’t keep it running if not needed.
WhyJiffie@sh.itjust.works
on 12 May 12:53
collapse
Also, don’t keep it running if not needed.
can you enforce that with flatpak? I often see the notification that “X program is still running in the background” or something similar, but the flatpak permission settings did not seem to have such a setting
bane_killgrind@slrpnk.net
on 12 May 13:02
collapse
My workplace barely groks opportunity cost on their main product, and I’m not responsible for the IT. When it breaks constantly, I say “yeah we know it breaks like this, get them to fix it.”
jamescrakemerani@feddit.uk
on 11 May 20:12
nextcollapse
I have a Linux work laptop which they let us have but we still have to use the MS crap. Fortunately most of it is accessible through the browser but a lot of the Office apps are broken, or missing features on web.
Don’t worry, teams is always somewhere between 10%-30% broken, always something n doesn’t work, there are always a bunch of people that can’t get in the meeting, that can’t share screens all of the sudden because fuck you, that’s why
Teams is the absolute worst and not a day goes by without people shitting on it, and we’re only using it because most of our customers do but internally we will switch to something open source soon, because I get to make that decision 😎
taladar@sh.itjust.works
on 11 May 20:30
nextcollapse
I have looked but I just couldn’t find an open source alternative that supported Teams core features like showing an error every time I login.
WhyJiffie@sh.itjust.works
on 12 May 00:38
collapse
you know, sometimes I wonder if Matrix could be used in a business setting, and worry about its rough edges and buggy features of Element. but you know what! it would probably be fine! not worse than teams, and at least they don’t want to fuck you over!
OK, I’m really curious on what programs your engineers use then. Engineering has been one of the use-cases for me, that made it basically impossible to switch to Linux full-time. If you know, please tell me.
BlackPenguins@lemmy.world
on 12 May 13:25
nextcollapse
We have Linux. We just use the in browser app. Works fine.
I see. Using the browser app certainly doesn’t sound like the optimal solution, but if it works fine, then that’s great. Unfortunately that’s not feasible for my case.
Thx for the answer, that makes sense. I’m more in the mechanical sector now and don’t have much to do with silicon design.
toastmeister@lemmy.ca
on 11 May 17:07
nextcollapse
This is why they require a TPM, your motherboard will be DRM against you owning the operating system.
Lyra_Lycan@lemmy.blahaj.zone
on 11 May 17:46
collapse
I installed Windows 11 with an unsupported CPU, kinda funny how it just worked despite all their screeching that it wouldn’t work and updating not working, but installing with installation media was flawless.
It’s a real bitch, automatically logging me into my partner’s account for the whole system and overriding my local user settings when I open MS Office apps Excel or Word (but that’s just Windows), and it cries about my lack of TPM on those apps and the Start menu when it does log in and cries about me not being logged into a MS account otherwise, but you know what? Everything still actually operates.
original_reader@lemm.ee
on 11 May 19:12
nextcollapse
…for now.
lazynooblet@lazysoci.al
on 11 May 19:35
nextcollapse
What CPU?
The list of unsupported CPUs is for OEMs licensing new computers as Windows 11 certified.
Nothing stopping you installing Windows 11 or upgrading to Windows 11 with an incompatible CPU.
The only item that requires a hack is the lack of TPM. Now that I still don’t understand.
Also, Office by default installs with licensing configured per machine but can be installed so it is licensed per user.
An OS is a tool.
And you are a tool if you use the wrong tool for a purpose.
E.g. an essential program that only runs on windows and is either impossible or troublesome to run elsewhere.
I agree. That’s why I wouldn’t install Windows 11 on an unsupported CPU in the first place, let alone keep it installed after having one issue after another like the comment I replied to had mentioned.
So does running teams in a windows vm prevent me to take a screenshot on the Linux host? I can’t imagine it would.
clay_pidgin@sh.itjust.works
on 11 May 20:44
collapse
I can’t see how it would. Can a VM tell it’s a VM?
vfsh@lemmy.blahaj.zone
on 11 May 20:54
nextcollapse
There are plenty of ways for a VM to tell that it’s a VM and not on baremetal, but there’s not really a way for a program running on an OS in the VM to block the Host OS or hypervisor software from capturing an image of the screen of the VM.
clay_pidgin@sh.itjust.works
on 11 May 21:07
collapse
Got it, thanks. I could imagine that certain software could just exit if it detects it’s not on the host OS.
sugar_in_your_tea@sh.itjust.works
on 12 May 01:48
collapse
Anticheat games are notorious for handing out bans if they detect they’re running in a VM.
So many commenters here and at the article get a hard on to bash MS for anything.
MS won’t make this a requirement, nor will they make using the Teams app a requirement. This isnt some backhanded way to get people to switch from Linux to windows.
This is MS responding to an enterprise feature request.
The reflexive hate for M$ is not irrational fan-boys bashing a rival, but bitterness over prolonged and profound annoyance, suffering, and downright abuse experienced through using the products produced by that dogshit company.
I switched because I wanted software that didn’t hate me and my values.
What’s irrational is the Stockholm-syndrome Windows user who thinks it’s normal and right to run software that spies, advertises, and generally treats users like a resource to be exploited.
sugar_in_your_tea@sh.itjust.works
on 12 May 01:43
collapse
Both are irrational IMO. Don’t make up reasons to hate a feature, but do attack the features that spy on you.
embed_me@programming.dev
on 12 May 05:31
nextcollapse
fatalicus@lemmy.world
on 12 May 05:28
nextcollapse
Yeah, commented on the sister thread of this over on the technology subreddit that this wouldnt be a default on feature, and probably be either something the meeting owner has to enable (or tenant admins set to enabled in a policy) or it will be part of sensitivity labels or DLP policies.
I think it’s more that average users aren’t accustomed to seeing Linux be a larger part of discussions here than on corporate platforms.
mostlikelyaperson@lemmy.world
on 12 May 08:25
nextcollapse
The moment a certain company is mentioned in an article, lemmy will go rabid, it doesn’t really matter what the article is about. I am a Linux nerd and if MS crashed and burned tomorrow I wouldn’t exactly shed a tear but the knee jerk reactions are pretty weird to observe.
cupcakezealot@lemmy.blahaj.zone
on 11 May 22:37
nextcollapse
i mean if someone really wanted to commit espionage they’d just take a photo of the screen with their camera.
humorlessrepost@lemmy.world
on 11 May 23:56
collapse
I suspect running teams on Windows in Parallels on a Mac would still let me use the Mac’s screen record feature.
FreedomAdvocate@lemmy.net.au
on 11 May 23:11
nextcollapse
“To address the issue of unauthorized screen captures during meetings, the Prevent Screen Capture feature ensures that if a user attempts to take a screen capture, the meeting window will turn black, thereby protecting sensitive information,” Microsoft shared in a new Microsoft 365 roadmap entry.
“This feature will be available on Teams desktop applications (both Windows and Mac) and Teams mobile applications (both iOS and Android).”
Yeah, seems like a perfectly reasonable feature to add. It will also likely be a toggle-able feature switch.
Surely there’s no way Lemmy gets angry at this, right?
I really want to dump on them but I can’t find anything wrong with the feature… That’s depressing, I’ll have to look elsewhere for my dose of “MS can’t do anything right lol”
sugar_in_your_tea@sh.itjust.works
on 12 May 01:39
collapse
You can just take a picture with a camera, which is included with a device pretty much everyone carries with them every day.
FreedomAdvocate@lemmy.net.au
on 12 May 05:06
nextcollapse
Bit more effort and harder to do when something only briefly flashes on screen than it is to hit the screenshot button on almost every keyboard.
sugar_in_your_tea@sh.itjust.works
on 12 May 05:25
collapse
If you know it’s blocked, you can have the camera ready. This is only going to keep honest people honest.
FreedomAdvocate@lemmy.net.au
on 12 May 05:28
collapse
As I said in another comment:
Also most people don’t sit there in meetings with their finger on the screenshot key ready to go - but it is simple to just press a screenshot key on your keyboard. It’s a little bit harder to have your phone up and with the camera open the entire time ready to take photos, especially if cameras are on - especially if something just pops up briefly on screen and you realise you want to capture it.
This is only going to keep honest people honest.
It’s going to keep the overwhelming amount of people “honest”, and it’s going to give companies an extra tick box on any security audits that are integral to the company doing business.
Sure, but it takes extra steps and the results won’t be as good as direct screen capture. It won’t stop someone determined, but it’s annoying enough that most people won’t bother.
sugar_in_your_tea@sh.itjust.works
on 12 May 13:14
collapse
Sure, it keeps honest people honest, but does little if anything to stop the actual problem.
surewhynotlem@lemmy.world
on 12 May 00:44
nextcollapse
My problem with it is that it gives a sense of security that does not exist.
Non-Technical folk will click the button and think they’re safe
FreedomAdvocate@lemmy.net.au
on 12 May 05:04
collapse
My problem with it is that it gives a sense of security that does not exist.
It gives security for 99% of people that will ever be on the calls, and most importantly it gives the company something to point to whenever they get security audits.
Non-Technical folk will click the button and think they’re safe
Non-technical folk aren’t usually responsible for setting policies in enterprise software lol.
Especially in the companies with the enterprise warning label non-technical idiots are in charge of setting technical policies because it is all about office politics there.
FreedomAdvocate@lemmy.net.au
on 12 May 06:02
collapse
If a company on enterprise plans has non-IT technical people doing their technical policies then nothing will save them.
FreedomAdvocate@lemmy.net.au
on 12 May 05:02
collapse
The feature is fine in theory. In practice, especially with work from home, it’s useless to achieve the goal it set out to. The article even points it out.
While true, that doesn’t really matter when it comes to enterprise. For security compliance you have to be shown to be doing everything that you can to prevent security breaches etc. This feature is another tick box that you can show to whoever is doing your audits to show that you are doing it.
Also most people don’t sit there in meetings with their finger on the screenshot key ready to go - but it is simple to just press a screenshot key on your keyboard. It’s a little bit harder to have your phone up and with the camera open the entire time ready to take photos, especially if cameras are on - especially if something just pops up briefly on screen and you realise you want to capture it.
I don’t know your experience in enterprise, but I can tell you that a feature like this will be much applauded by those running companies for the reasons above.
Yeah, this is a “feature” for the companies with the “enterprise” warning label who would rather waste a lot of effort on ineffective compliance checklists than actually make sure their software is up-to-date with security fixes.
FreedomAdvocate@lemmy.net.au
on 12 May 06:03
collapse
Nope. Compliance check lists matter when you are audited by external companies for things like PCI. It’s also not a lot of effort, nor is it ineffective, nor is making sure software is up to date ignored.
Are you stupid? Next week they will sell an add on that let’s you recall the whole meeting. You need to start thinking outside the box if you’re gonna make it in scummy corporate sales.
Or just use the smartphone camera that almost everyone is going to have anyhow…
embed_me@programming.dev
on 12 May 05:30
nextcollapse
Like record it using a camera? That’s a substantial downgrade
taladar@sh.itjust.works
on 12 May 05:44
nextcollapse
Doesn’t matter for the “problem” they are trying to solve. Nobody interested in the “sensitive” information of another company will complain about picture quality if the information is readable enough.
pastermil@sh.itjust.works
on 12 May 05:44
collapse
now that all the performance, reliability, and usability issues are solved in Teams, it’s great to see all that energy going into this useful feature that is surely not possible to circumvent in any way.
There are going to be fifty different bypasses up on github by the end of the week. This makes me want to join a corpo and record their precious meetings
SubUrbanIT@lemmy.world
on 12 May 10:53
nextcollapse
Gonna be difficult to block screen capture when I have a phone in my hand with a camera that can be record what I see.
Don’t be so bold. Microsoft is investing in military AI applications. So don’t be surprised when your computer slaps that camera right out of your hands and punches you in the face. /j (or not, idk, things are looking bad)
NotMyOldRedditName@lemmy.world
on 12 May 17:23
collapse
There are some autonomous cars with lidar out there where the lidar is so powerful it can wreck a camera close up, but is still safe for eyes.
Switch up FaceID to use a more powerful laser which will wreck the phones camera, and start making webcams for non macs that are required to have this in them for Teams to work.
BradleyUffner@lemmy.world
on 12 May 11:18
nextcollapse
So you’re saying that I can just start an infinite empty meeting in order to block the AI Recall thing from recording my screen?
Laughs at all the cell phone camera captures that will start showing up…
gradual@lemmings.world
on 12 May 12:53
nextcollapse
More and more, I notice that Microsoft’s ubiquity in our society is to reinforce the idea that we need to take abuse and reward our abusers in order to be successful.
rottingleaf@lemmy.world
on 12 May 13:16
nextcollapse
We dont make the decision as to what suite to use?
Literally no one but our CFO ad shareholders like microsoft.
OccasionallyFeralya@lemmy.ml
on 12 May 13:51
nextcollapse
To be clear this is an option enabled by the host. It most likely won’t be used for normal meetings.
FermionWrangler@lemm.ee
on 12 May 15:29
nextcollapse
There will be ways to capture it anyway. Probably specific software designed for GPU capture, since that’s how these apps “prevent” capturing, using GPU trickery.
The announcement from MS and the linked article both also mention this, though they recommend the real analogue hole: a separate camera pointed at the screen.
Simplest way is a Windows VM and screen capture in the OS running the VM. Obviously next step for Microsoft is to detect and block Windows VMs, good luck to them with that.
threaded - newest
Clickbait title
No, the title is quite accurate. There is no magic to discern “sensitive” data from that which is not.
It’s not accurate because it will be an optional feature.
Yeah, not seeing this as the big bad everyone thinks it is. We regularly have Teams meetings with other companies when they’re sharing their proprietary info. I’m okay with a screen capture disabling function just like we’d want to use from time to time.
From the article:
and
So this is actually worse than just blocking screen capturing. This will break video calls for some setups for no reason at all since all it takes to break this is a phone camera - one of the most common things in the world.
This has always been the case for anything that restricts screen capture. The tech makes getting detailed information more difficult, that’s all.
Adobe does this with PDFs by restricting printing. You can still record the screen and flip through each page.
Also, you’ll look odd holding your phone up to the screen.
just connect another display, set it to mirroring, and point a camera at that. or just use a video capture card.
Like I said, there’s always been a way to defeat this type of protection. This feature makes doing so more difficult.
That’s pure speculation. Did you even read the article?
Edit: here, let me help you:
Considering most of the organizations using Teams bear the “enterprise” warning label I wouldn’t count on whoever you are talking to having the ability (as in permissions, not stupidity) to turn it off.
What part of the headline suggests the feature is mandatory? Assuming its mandatory doesn’t pass the critical thinking “sniff test” because what is sensitive is purely subjective. Microsoft has no way of knowing what data you consider sensitive. As in, there’s no way Microsoft could make it mandatory on only “sensitive” data.
“Microsoft” “will” “block”
Those parts of the title.
The source though indicates that it will be a Feature and it even has its own name. Sadly it doesn’t point out that it will be optional.
Additionally you can see in the comments of the article that people think this will be mandatory.
That’s a charitable reading, and likely justified by the article, but based only on the phrasing, it’s just as likely to read that as assuming Microsoft will block all content in order to ensure the safety of sensitive data. Sniff tests have to be adapted when things tend to stink in general, or companies regularly try to cover up their smell.
Hang on. If you’re rejecting rational use cases that companies use Teams for, then your assumption must be that Microsoft will block ALL screen capture when a teams meeting is occurring whether its of the Teams meeting content being shared or not. As in, even the presenter would be blocked from doing screen captures of their own system. Why isn’t that your conclusion?
Why are you, again, from the headline only, assuming that screen capture would mandatory for just content shared to you by a Teams presenter? You chose a middle ground, but why didn’t you choose full blocking?
So are you adapting yours back now because yours was proven wrong?
Well, ‘proven wrong’ is a bit of a stretch. ‘will soon block screen capture’ doesn’t leave a lot of wiggle room, but also isn’t that crazy to read into it that maybe it would block screen capture on the presenters screen… especially if you grant that it might only have control over the teams portion of the screen. I’ve had it black out windows on my own machine even when not presenting.
But further than that, it’s not fair to say everything has to be read only from the most or the least charitable viewpoints. Context is a thing and if you’re even a little bit familiar with the history of software enshittification, it’s reasonable to assume that an uncharitable reading is fair without assuming the app will now melt your computer for spare parts if you try something that is disallowed. ‘As shitty as we can get away with’ might be a good rule of thumb.
this is true, if you have privacy categories setup and you use something that isn’t rated for someone, they won’t be able to see it. Kinda like permissions. Government and Medical environments is where I’ve seen it applied. It’s a beast to implement.
Doubt it will prevent flameshot from working if I use teams in firefox
Knowing ms they’ll just make browsers audio only going forward
Pointless.
Rules for thee not mee
Yeah seriously; this won’t even stop normies. Everybody knows how to take a picture with their phone. Why bother?
Hell a lot of people would probably default to using a phone because they don’t know how print screen works.
I’ll have to use the camera phone again then.
Don’t worry, Recall will record everything done on the Windows machine.
The important bit:
And I presume everything except Windows 11 Teams will be considered “unsupported”.
I used to be able to join teams meetings in the browser version of teams from my Linux machine. I did my last job interview this way
There’s also the unofficial flatpak, which works rather well.
No, it sucks. The Linux app does not support screen sharing on Wayland, but it works fine in the browser
Ah. I haven’t switched to Wayland yet so I wasn’t aware of that issue.
I use Wayland at work, and haven’t had any issues sharing my screen on Teams.
This still works, it is my only method of interaction with Teams
Aahhwww, that is so sad, I run Linux and soon our entire office will.
Guess we won’t be using teams then, ooaaahhhwww, so sad
What do you use for video calls with screen share?
My coop uses teams and I want to move them off it.
Did you even read the article.
Read the article man
i trust signing in through the browser on linux will be supported since that’s the official way to use teams on linux
except on firefox of course, because fuck you for even trying to protect a little bit of your privacy
I use Edge on Linux for working with Microsoft stuff on my corporate laptop. For everything else I use Firefox there. Privacy preserved, basically.
only if the browser cannot run in the background, and it cannot access any of your fikes, the DBus of your regular user’s session, and other facilities
You lock it with flatpak as much as you can. Also, don’t keep it running if not needed.
can you enforce that with flatpak? I often see the notification that “X program is still running in the background” or something similar, but the flatpak permission settings did not seem to have such a setting
No but, you can just close it.
Good. Do me a favour and block the audio as well.
So now my clients will have a harder time engaging with my product. Great.
Stop using microsoft teams, ya dolt.
My workplace barely groks opportunity cost on their main product, and I’m not responsible for the IT. When it breaks constantly, I say “yeah we know it breaks like this, get them to fix it.”
Not my circus, I just stamp the tickets.
I don’t know to what extent they’ll go, but yes, this and the Advanced Chat Privacy in WhatsApp are just user locking moves.
Welp, there goes any accountability.
So take a fucking picture with your phone
No you.
My company is transitioning to teams. Most of our engineering is on Linux.
Can Microsoft please hurry up and break teams so we can’t transition?
If Co is willing to use it in current state, all the breaking in the world is not going to change their mind.
God I wish my company allowed that
I have a Linux work laptop which they let us have but we still have to use the MS crap. Fortunately most of it is accessible through the browser but a lot of the Office apps are broken, or missing features on web.
This is fairly common in software development.
I’m still at my first job in Software Development.
I think this has gone and done it for you
Don’t worry, teams is always somewhere between 10%-30% broken, always something n doesn’t work, there are always a bunch of people that can’t get in the meeting, that can’t share screens all of the sudden because fuck you, that’s why
Teams is the absolute worst and not a day goes by without people shitting on it, and we’re only using it because most of our customers do but internally we will switch to something open source soon, because I get to make that decision 😎
I have looked but I just couldn’t find an open source alternative that supported Teams core features like showing an error every time I login.
you know, sometimes I wonder if Matrix could be used in a business setting, and worry about its rough edges and buggy features of Element. but you know what! it would probably be fine! not worse than teams, and at least they don’t want to fuck you over!
OK, I’m really curious on what programs your engineers use then. Engineering has been one of the use-cases for me, that made it basically impossible to switch to Linux full-time. If you know, please tell me.
We have Linux. We just use the in browser app. Works fine.
I see. Using the browser app certainly doesn’t sound like the optimal solution, but if it works fine, then that’s great. Unfortunately that’s not feasible for my case.
All the EDA tools for silicon design are Linux based.
Thx for the answer, that makes sense. I’m more in the mechanical sector now and don’t have much to do with silicon design.
This is why they require a TPM, your motherboard will be DRM against you owning the operating system.
I installed Windows 11 with an unsupported CPU, kinda funny how it just worked despite all their screeching that it wouldn’t work and updating not working, but installing with installation media was flawless.
It’s a real bitch, automatically logging me into my partner’s account for the whole system and overriding my local user settings when I open MS Office apps Excel or Word (but that’s just Windows), and it cries about my lack of TPM on those apps and the Start menu when it does log in and cries about me not being logged into a MS account otherwise, but you know what? Everything still actually operates.
…for now.
What CPU?
The list of unsupported CPUs is for OEMs licensing new computers as Windows 11 certified.
Nothing stopping you installing Windows 11 or upgrading to Windows 11 with an incompatible CPU.
The only item that requires a hack is the lack of TPM. Now that I still don’t understand.
Also, Office by default installs with licensing configured per machine but can be installed so it is licensed per user.
I don’t want to be that guy, but why use Windows at that point?
An OS is a tool.
And you are a tool if you use the wrong tool for a purpose.
E.g. an essential program that only runs on windows and is either impossible or troublesome to run elsewhere.
I agree. That’s why I wouldn’t install Windows 11 on an unsupported CPU in the first place, let alone keep it installed after having one issue after another like the comment I replied to had mentioned.
Seems like the wrong tool to me.
What about Teams browser?
OBS Studio has been able to record Teams meetings so far, on Linux.
regarding the quote, will they just not let linux users connect to the call when that restriction is turned on?
edit: nvm, the article talks about that too
So does running teams in a windows vm prevent me to take a screenshot on the Linux host? I can’t imagine it would.
I can’t see how it would. Can a VM tell it’s a VM?
There are plenty of ways for a VM to tell that it’s a VM and not on baremetal, but there’s not really a way for a program running on an OS in the VM to block the Host OS or hypervisor software from capturing an image of the screen of the VM.
Got it, thanks. I could imagine that certain software could just exit if it detects it’s not on the host OS.
Anticheat games are notorious for handing out bans if they detect they’re running in a VM.
It’s too late for this philosophical questions
So many commenters here and at the article get a hard on to bash MS for anything.
MS won’t make this a requirement, nor will they make using the Teams app a requirement. This isnt some backhanded way to get people to switch from Linux to windows.
This is MS responding to an enterprise feature request.
The reflexive hate for M$ is not irrational fan-boys bashing a rival, but bitterness over prolonged and profound annoyance, suffering, and downright abuse experienced through using the products produced by that dogshit company.
I switched because I wanted software that didn’t hate me and my values.
What’s irrational is the Stockholm-syndrome Windows user who thinks it’s normal and right to run software that spies, advertises, and generally treats users like a resource to be exploited.
Both are irrational IMO. Don’t make up reasons to hate a feature, but do attack the features that spy on you.
One man’s dogma is another man’s irrationality
One man’s feature is another man’s anti-feature.
Yeah, commented on the sister thread of this over on the technology subreddit that this wouldnt be a default on feature, and probably be either something the meeting owner has to enable (or tenant admins set to enabled in a policy) or it will be part of sensitivity labels or DLP policies.
Instant downvote.
Because Lemmy Linux bros like to get their titty in a twist.
I think it’s more that average users aren’t accustomed to seeing Linux be a larger part of discussions here than on corporate platforms.
The moment a certain company is mentioned in an article, lemmy will go rabid, it doesn’t really matter what the article is about. I am a Linux nerd and if MS crashed and burned tomorrow I wouldn’t exactly shed a tear but the knee jerk reactions are pretty weird to observe.
I bet they will still make it default.
i mean if someone really wanted to commit espionage they’d just take a photo of the screen with their camera.
I suspect running teams on Windows in Parallels on a Mac would still let me use the Mac’s screen record feature.
Yeah, seems like a perfectly reasonable feature to add. It will also likely be a toggle-able feature switch.
Surely there’s no way Lemmy gets angry at this, right?
Reads comments
<img alt="" src="https://lemmy.net.au/pictrs/image/d9190e66-00cf-490b-8683-807fdf00e93d.jpeg">
I really want to dump on them but I can’t find anything wrong with the feature… That’s depressing, I’ll have to look elsewhere for my dose of “MS can’t do anything right lol”
You can just take a picture with a camera, which is included with a device pretty much everyone carries with them every day.
Bit more effort and harder to do when something only briefly flashes on screen than it is to hit the screenshot button on almost every keyboard.
If you know it’s blocked, you can have the camera ready. This is only going to keep honest people honest.
As I said in another comment:
It’s going to keep the overwhelming amount of people “honest”, and it’s going to give companies an extra tick box on any security audits that are integral to the company doing business.
Sure, but it takes extra steps and the results won’t be as good as direct screen capture. It won’t stop someone determined, but it’s annoying enough that most people won’t bother.
Sure, it keeps honest people honest, but does little if anything to stop the actual problem.
My problem with it is that it gives a sense of security that does not exist.
Non-Technical folk will click the button and think they’re safe
It gives security for 99% of people that will ever be on the calls, and most importantly it gives the company something to point to whenever they get security audits.
Non-technical folk aren’t usually responsible for setting policies in enterprise software lol.
Especially in the companies with the enterprise warning label non-technical idiots are in charge of setting technical policies because it is all about office politics there.
If a company on enterprise plans has non-IT technical people doing their technical policies then nothing will save them.
.
While true, that doesn’t really matter when it comes to enterprise. For security compliance you have to be shown to be doing everything that you can to prevent security breaches etc. This feature is another tick box that you can show to whoever is doing your audits to show that you are doing it.
Also most people don’t sit there in meetings with their finger on the screenshot key ready to go - but it is simple to just press a screenshot key on your keyboard. It’s a little bit harder to have your phone up and with the camera open the entire time ready to take photos, especially if cameras are on - especially if something just pops up briefly on screen and you realise you want to capture it.
I don’t know your experience in enterprise, but I can tell you that a feature like this will be much applauded by those running companies for the reasons above.
Yeah, this is a “feature” for the companies with the “enterprise” warning label who would rather waste a lot of effort on ineffective compliance checklists than actually make sure their software is up-to-date with security fixes.
Nope. Compliance check lists matter when you are audited by external companies for things like PCI. It’s also not a lot of effort, nor is it ineffective, nor is making sure software is up to date ignored.
I mean… Would it do the same with a 3rd party screenshot app? Or even something like obs? So many ways around it, no reason to get too upset.
Probably, but won’t really know until it comes out.
I hate stuff like this because screen grabs during meetings or lectures is my favorite way to take notes.
Nooooo. If you do that, you won’t be paying for Teams Premium which has built in support for screen recording. Think of the revenue lost 😭😭
Edit: I should add /s incase people think I’m a Microsoft shill
Now I know why they’re trying to push corporate users off of Linux, again.
It’s okay people, even if the feature in itself is not awful, MS Teams still is awful. We can still bash on MS to relieve past Windows trauma.
they should also blank the screen if the user has recall enabled
Are you stupid? Next week they will sell an add on that let’s you recall the whole meeting. You need to start thinking outside the box if you’re gonna make it in scummy corporate sales.
Run teams in a VM and take a screen shot from the host OS.
Or just use the smartphone camera that almost everyone is going to have anyhow…
Like record it using a camera? That’s a substantial downgrade
Doesn’t matter for the “problem” they are trying to solve. Nobody interested in the “sensitive” information of another company will complain about picture quality if the information is readable enough.
A lot of people havw been doing it anyway.
Recording a 1h meeting with a smartphone sounds like a nightmare.
1hr? Maybe just wear an action camera, if you can sit well in front of the screen during whole meeting. (j/k)
EDIT: For smartphone, get a selfie stand if you have place to set it up, do not try to hold the phone with your hand for 1 hour.
This is the right way, but holding it in their hands will be the way so many clever rebels do it at first.
Thanks Microsoft, I’m investing in cell-phone tripods today.
on a work laptop?
Some of us have remote desktop capabilities on our wfh machines
So it would block screen/video capture, but will it block sound-only capture, too?
It will be funny if they try, because plenty of presentation setups will break
Jerb security.
now that all the performance, reliability, and usability issues are solved in Teams, it’s great to see all that energy going into this useful feature that is surely not possible to circumvent in any way.
Now we get to break it.
There are going to be fifty different bypasses up on github by the end of the week. This makes me want to join a corpo and record their precious meetings
Gonna be difficult to block screen capture when I have a phone in my hand with a camera that can be record what I see.
Don’t be so bold. Microsoft is investing in military AI applications. So don’t be surprised when your computer slaps that camera right out of your hands and punches you in the face. /j (or not, idk, things are looking bad)
There are some autonomous cars with lidar out there where the lidar is so powerful it can wreck a camera close up, but is still safe for eyes.
Switch up FaceID to use a more powerful laser which will wreck the phones camera, and start making webcams for non macs that are required to have this in them for Teams to work.
So you’re saying that I can just start an infinite empty meeting in order to block the AI Recall thing from recording my screen?
Oh, no, AI Recall has “special privileges” - just you lusers don’t.
This is so you can then use their super cool and completely accurate AI summary tool that will be coming soon.
“The meeting was about polishing yaks. The conclusion was green is important fudge.”
[laughs in rdp from another machine]
Laughs at all the cell phone camera captures that will start showing up…
More and more, I notice that Microsoft’s ubiquity in our society is to reinforce the idea that we need to take abuse and reward our abusers in order to be successful.
Why would one use an intentionally impaired tool?
Because the company one works at is entangled in Microsoft products and totally dependend on it.
We dont make the decision as to what suite to use?
Literally no one but our CFO ad shareholders like microsoft.
To be clear this is an option enabled by the host. It most likely won’t be used for normal meetings.
There will be ways to capture it anyway. Probably specific software designed for GPU capture, since that’s how these apps “prevent” capturing, using GPU trickery.
The announcement from MS and the linked article both also mention this, though they recommend the real analogue hole: a separate camera pointed at the screen.
Simplest way is a Windows VM and screen capture in the OS running the VM. Obviously next step for Microsoft is to detect and block Windows VMs, good luck to them with that.
Yes.
It’s inevitable they’ll do everything they can to degrade the usability of their shitty products.