For general public I can see how that is helpful if they can't decide if a foreign executable is trust worthy or if they execute everything with admin/root privilege.
As for me, I really hate this "feature". I work with IHVs and often have to share private binaries and it's a chore using xcopy/sfpcopy to their bespoke network path, from where I guess then someone manually copies over to their local subnet.
We should have a more robust mechanism in place than to outright ban sharing of executable files. Windows Smartscreen and Mac's Gatekeeper method of online checksum/signature verification is sort of interesting.
Re:Hackers used Slack to break into EA Games
by 650REDHAIR on Saturday June 12, 2021 @02:40PM
(#27486561)
1000 times no.
You need to build security for the lowest common denominator.
Re:Hackers used Slack to break into EA Games
by zeusk on Saturday June 12, 2021 @06:10PM
(#27487823)
Which is what Defender smartscreen and Gatekeeper are. With their full on setting, they give you a big fat warning on running files from internet.
This is like banning guns and cars because they can kill people.
Also, you do 24 hours of lemons?
Re:Hackers used Slack to break into EA Games
by recursive on Friday June 11, 2021 @05:05PM
(#27478484)
I don't know if it's true, but a co-worker of mine said that, "in the wild" signed binaries are positively correlated with being malware.
I don't think the signing itself does much.
Re:Hackers used Slack to break into EA Games
by manquer on Friday June 11, 2021 @06:16PM
(#27479163)
Perhaps not in itself. The lack of scans is concerning though
But the problem goes beyond that. Many organizations have disabled sharing executable file formats in attachments over e-mail. GMail flat-out prevents you from sharing executables, and macro enabled word documents as attachments, even when put into a zip file.
But on Microsoft teams? I sent a zip file with 8 unsigned executables to a colleague a few days ago. No warnings, no messages, no nothing :)