Re:New Mac ransomware spreading through piracy
by sys_64738 on Tuesday June 30, 2020 @07:08PM
(#23695859)
Couldn't you run the Mac equivalent of a Windows Sandbox to restrict access if you had concerns about an app?
[ Parent
| on HN ]
Re:New Mac ransomware spreading through piracy
by Kejistan on Tuesday June 30, 2020 @07:26PM
(#23695997)
You can `sandbox-exec`. But that probably wouldn’t be useful for a program like little-snitch, which needs rather broad permissions normally.
Re:New Mac ransomware spreading through piracy
by jldugger on Tuesday June 30, 2020 @10:41PM
(#23697173)
The sandbox-exec command is DEPRECATED. Developers who wish to sandbox an app should instead adopt the App Sandbox feature described in the App Sandbox Design Guide. The sandbox-exec command enters a sandbox
Re:New Mac ransomware spreading through piracy
by saagarjha on Wednesday July 01, 2020 @04:45AM
(#23699311)
All of sandboxing (including sandbox-exec, which is like 10 lines of code to just call the sandboxing functions) is considered deprecated/Apple private. As it’s the way to do such things on macOS, however, some very popular software depends on it in addition to Apple’s: Chrome, Firefox, MacPorts, Homebrew, …
Re:New Mac ransomware spreading through piracy
by Wowfunhappy on Tuesday June 30, 2020 @11:55PM
(#23697603)
Does it work though?
Re:New Mac ransomware spreading through piracy
by comex on Wednesday July 01, 2020 @12:57AM
(#23697879)
It works, but you have to supply your own sandbox profile (list of allowed/denied operations) and it won’t create a virtual home directory for you like App Sandbox does. I’m not sure whether there’s an easy way to forcibly enable App Sandbox, but one possibility is to compile your own sandboxed app that simply execs the untrusted one. (Sandboxes are inherited by child processes, as they must be for security.)
Re:New Mac ransomware spreading through piracy
by oefrha on Wednesday July 01, 2020 @01:11AM
(#23697961)
It works, and Homebrew is a high profile example of software that uses sandbox-exec extensively (bottling CI and brew install from source build formulae in sandboxes so that build scripts can’t read/write whatever they feel like; so do tests).