6 ms·
Buggy system implementations, unfinished API flows, apps constantly needing to ask for permission, a big break in compatibility and little to no time to properl
by jeroenhd 7y ago
Buggy system implementations, unfinished API flows, apps constantly needing to ask for permission, a big break in compatibility and little to no time to properly test before the official release: it took some time, but Apple has finally reached their Vista point.
Not that this is necessarily bad (although the bugs are super annoying). Vista had to happen, and I can see why many casual users in the Apple ecosystem would prefer a simple, sandbox system for their operating system. Time will tell if this is indeed a step ahead or a problem that will be made undone in the future. It just sucks that Apple customers are dealing with their own Vista now though.
- TazeTSchnitzel 7y agoI'm a “power user” and I think sandboxing is a good thing. I often run code written by others that I haven't read. I would like it if it does not have the ability to erase all my files.
- stefan_ 7y agoThe problem is that sandboxing has been consistently proven to impede legitimate use cases, but not so much the illegitimate.
- blub 7y agoSandboxing on iOS and Android is working great to prevent the spyware developers from achieving their goals. And now macOS is adding more of the same protections...
- jschwartzi 7y agoNo, it just means you need to create a social network to install spyware.
- deleted 7y ago[deleted]
- BeetleB 7y ago> Sandboxing on iOS and Android is working great to prevent the spyware developers from achieving their goals. For power users who use Tasker, Android's restrictions are a nightmare. I cannot, for example, kill an app using Tasker, and I really really need to do this. Plenty of other restrictions that made Tasker users' life difficult. To be clear, this is on a rooted phone. Am I not allowed to algorithmically decide to kill an app on my own phone?
- acdha 7y agoDo even 0.1% of Android users use Tasker? 100% of them are at risk from malware and spyware which would directly access your data and other apps if not sandboxed. This could be somewhat addressed with different sandbox policies for well-audited applications but we've seen a long history of those lines being pushed as far as possible (e.g. Uber trying to use geo-fencing to evade reviewers). As an aside, I'm curious what makes killing an app so critical vs. only shutting down background processes. That seems like an edge case on an edge case?
- BeetleB 7y ago> Do even 0.1% of Android users use Tasker? This thread is about power users, not average users. If I sold you a Linux PC, and gave you root access, but it was sandboxed and you couldn't kill apps from the command line, would you say the PC I gave you is fine for "power users"?
- acdha 7y agoYou have to think about how these capabilities are abused for something with as much personal data as a phone: if that capability is there it will be abused by malware, abusive partners, unscrupulous app vendors, snooping governments, etc. to impact orders of magnitude more people than believe they need these features. People will be trained to click approve the next time they install spyware or bogus optimization / cleanup utilities and many of the people most likely to be exploited will be the loudest about saying they're power users who need this access and won't make mistakes (see past decades of Windows usage).
- favorited 7y agoHuh? Sandboxing absolutely impedes illegitimate use cases. I love that I can run apps knowing that they can't scan the contents of my documents directory, or my photos app. Without sandboxing, apps can rampage through my user contents unrestricted.
- jeroenhd 7y agoI agree re: sandboxing. The security gained by a sandbox is immense and dumb programs and games I use should be restricted to their own little space. This does require some well-thought-out system level abstractions for users and developers to accept the new sandbox, but that's not impossible to do. Especially for stuff that should Just Work (R), sandboxes are a great tool. This isn't just a casual user thing, system developers also use Spotify and don't want to mess with arcane program settings and directories. I do believe that casual users will be using more apps that "just work" than power users though, which is why I mentioned them. On the other hand, I do like to have access to each and every file on my system if I so please and I do want to be able to use my toolset anywhere on the system. For my classes I need to run what we call "PhD-ware" every now and then (technically advanced software that is great at doing one specific job but is mostly unmaintained and requires a specific setup to work) and that's never going to be compatible with any security restriction. I want to be able to override the system when needed.
- blablabla123 7y agoI upgraded to Catalina and barely noticed the restrictions since I mostly use Browser, Terminal and Editor - along with some off-the-shelve proprietary software. For me it's a good development since I rarely download .DMGs from the web browser, and if I do, I get a strong reminder that this might contain adware, spyware or just make my system a little more buggy. Most software I actually install through homebrew and it's nice that the software has been checked more than once by other people. To me it's the whole point of using Mac(OS), things just work (TM) and if not there's a way to make them work. One positive thing actually: I think Apple tidied up the DTrace configuration, so it's much easier to start without doing any crazy configuration stunts.
- msla 7y ago> For my classes I need to run what we call "PhD-ware" every now and then (technically advanced software that is great at doing one specific job but is mostly unmaintained and requires a specific setup to work) and that's never going to be compatible with any security restriction. Sounds like a job for Docker, or possibly a hypervisor: Put the app in a container, put the specific files it needs to work on in the container, and the app lives entirely inside that container, whether it's a Docker image or a filesystem image with an OS or something in-between; there's no security implications because it can only touch what's already in the container with it. As a plus, the whole system (OS, configuration, application, and all) is now reified into a single container artifact you can ship around and just run. It won't rot, or at least it'll keep a lot longer (as long as the container technology keeps).
- acomjean 7y agois it sandboxing shell/python scripts downloaded? Or programs installed by brew.? While I'd love to check all the code I've downloaded for sneaky problems, I'll agree that in this day and age that isn't entirely feasible. At some point, you have to hope your backup regimen is working.
- msla 7y agoI like sandboxing too, but what you just said gives a window into the problem: You don't want a program to be able to erase all your files, but you might want it to be able to create and edit files. So how do you express that clearly enough to become an automatically-enforcable security policy? Can a program only create files? Can a program create files, and only edit files it created? Can a program create files, and then edit and delete only the files it created? Ignoring the technical details of implementing this, you still have a semantic gap between "I don't want my document editor running wild on my files" and something you can express unambiguously. The only way anyone seems to have come up with to close that gap is Popup Whack-A-Mole, which everyone seems to agree is a massive usability failure except everyone who's reinvented it.
- concordDance 7y agoI expect this is a problem that's been thouroughly thought about. Permissions are probably something like"you can do what you like over HERE but can't touch anything else".
- blub 7y agoVista had excellent security compared to its predecessor, but it never had this kind of sophisticated access control. In any case, within one year they fixed the annoying pop-ups and it was a solid OS, I was using it as my main OS for several years. Apple's permissions are smarter and the constantly asking for permission does not happen in my experience on macOS. Apparently they've integrated the open file dialog with their access control, so any such dialog will automatically permit the app to access the target file/folder. The pop-ups only appear when an app wants to access specific folders in the background. This is brilliant and would stop e.g. malware which encrypts documents or nosy apps in their tracks!
- jeroenhd 7y agoOf course, I don't intend to say that vista had anything that comes close to the modern day sandbox. However, it did enforce strict security policies that its predecessors didn't have. UAC and up to some point smart screen is comparable to the sandbox permissions and the notarising thing. It's an inconvenient break in compatibility, dialog flow and program design that has a lot of benefits and some downsides. Until programs adapt to the new paradigm, old programs will likely be slightly annoying to use, just like what happened in the Vista days. I hope Apple doesn't solve the dialog problem the way Microsoft did though (by sacrificing security for usability), now we have the situation that being logged in as a local admin with UAC set to default means that any malware can gain admin privileges through UAC bypasses. You can prevent this by setting the UAC settings to max or logging in as a standard user, but then you get Vista-style annoyances again...
- temac 7y ago> You can prevent this by setting the UAC settings to max or logging in as a standard user, but then you get Vista-style annoyances again... And I'm not even sure UAC at max level is officially a security boundary. As for the second solution, yep, and you actually could also log in as a standard user in XP (and 2000, and NT) Now there is a fun thing about security, is that it can be sometimes counter-intuitive. A yes-no popup on a secure desktop can be way more secure than asking for a password in some cases, because the popup screen could be spoofed, and while obtaining an admin pwd is obviously valuable, obtaining a yes-no answer from the user at the console is not... (Some mitigations exists like SAK but they are not perfect, because the users can make mistakes, especially if asked for their password all the time)
- kitsunesoba 7y agoThe problems with permissions dialogs are overblown in my experience. You get hit with a flurry at least initial boot up after upgrading because desktop applications don’t know how to behave themselves in a sandboxed environment and just reach for whatever they please, but after that initial burst they’re quite rare. With how Apple has been gradually weaning third party devs from having extensive/root access it’s nowhere near as annoying as UAC was.
- jeroenhd 7y agoI don't think UAC was tbat annoying to be honest. Where it asked for confirmation and admin privileges, it made sense. Most UAC buttons were labeled and from a security standpoint, it was quite a solid experience. Last time I used Apple, it felt like a flashback to Vista to me. Prompts for every program I downloaded, leaving me to keep the system security settings open for the first hour or so to download appropriate installers and password prompts every time I went to change a setting. Like in vista, the places it asks for admin permissions usually make sense, but the contrast was quite stark compared to the Windows and Ubuntu dialog flow I was used to. I found the "the system prevented you from opening this program" dialogs reminiscent of the super-criticised SmartScreen dialogs that block(ed?) Windows 8+ programs from unknown sources.
- zozbot234 7y ago> Apple has finally reached their Vista point Well, on a different note, even Linux desktop/workstation distributions have reached their Vista point... in the somewhat trivial sense that they now need Vista-capable hardware in order to be reasonably usable! (We do know how it happened, it's all about the usual CADT syndrome. At least they are still usable, unlike Vista or Catalina. But one can still be disappointed by such developments.)
- dtech 7y agoWhy should precious developer time and resources be devoted to supporting pre-2006 hardware?
- jeroenhd 7y agoA system that runs smoothly on 2006 hardware runs blazingly fast on modern hardware. It's also likely to consume less resources and power. There's also the fact that many developers live in rich countries where good hardware is relatively cheap and easy to come by. Developing countries usually don't have access to reasonably priced hardware at all. There's billions of people whose hardware is barely capable of running a Vista equivalent. That alone should be reason to consider developing with older systems in mind. Developing to keep an old system somewhat smooth can lead to improvements across the board. There's pros and cons to every decision and I certainly don't think every piece of software should be designed to run on a Core2Duo. In many cases some considerations for those who can't bug fancy hardware would be nice though.
- zozbot234 7y ago> A system that runs smoothly on 2006 hardware runs blazingly fast on modern hardware. This is especially true wrt. memory use, BTW. Memory bandwidth is, as a rule of thumb, the main bottleneck affecting performance in present-day systems, so most savings in RAM use yield very real increases in performance for real-world scenarios. Also, less RAM use makes it easier to run a useful number of virtual machines or containers, even on non-high class hardware.
- Bud 7y agoThis is a one-time access control check for security. The article is overblown, the headline is sensationalized, and so is your comment.
- jquery 7y agoThe "one-time access control check" doesn't fire properly if you merely upgrade from Mojave. Dropbox completely stopped working for me until I did a clean reinstall of Catalina and then the permissions window finally appeared and I was able to say "yeah, let Dropbox do its thing." Really bad user experience, if I knew I'd have to do a clean reinstall, I would've waited to upgrade.
- musicale 7y agoI tend to agree - Vista's security improvements were its best feature, and they also broke a lot of stuff and resulted in a bunch of annoying UAC pop-ups that confused users and probably encouraged them to get in the bad habit of saying "yes" to everything.