'Hey Apple! You’re going to let some little independent developer selling a $15 utility to bypass SIP or be signed to modify the OS? What about me? My software is responsible for thousands of Macs being bought and used. Who is going to decide who gets keys to the kingdom? You will literally see THOUSANDS of developers submitting claims to be allowed access to bypass SIP. There are literally thousands of apps, many of which, development and functionality would be greatly enhanced and improved 'if only silly Apple would let us “trusted” developers run amok in the guts of macOS and change whatever we want, when we want". The old saying, What’s good for the goose is good for the gander? Can the same be said for other developers and other apps? If Apple makes an exception for TF, and sets the precedence that exceptions are given or even possible, how quickly do you think before other developers are going to literally threaten to TEAR down the walls in Cupertino to also be given an ‘exception’. In this case, we as users trust TF and the developer that no harm is done as part of this direct manipulation of Apple code and the operating system. At the time modifying Finder was allowed and it worked. That’s it, that’s all TF was intended to be, everything else is bells and whistles. Back in the day, it was the easiest and most efficient way for TF to be written based on the intent, a simple dual pane window enhancement to Finder. This is not a criticism of TF, I love it and use it. TF as currently written, works because it directly modifies Apple code this is precisely what malware does and what SIP was created to prevent. I see comments like “Can’t you petition Apple to have TF signed, or why can’t Apple set up a system for ‘legitimate’ programs that modify the operating system to be reviewed and ‘allowed’ through.” You have people bemoaning that SIP must be disabled, and claiming they can’t / won’t disable SIP because they don’t want the ‘risk’ or their employer doesn’t want the ‘risk’ in short without saying so, they concede the security benefit of why SIP is there in the first place, even if publicly dissing it because of the personal inconvenience it creates.Īt the same time, you have folks, including some of the very same people who can’t or refuse to disable SIP, criticizing Apple for having SIP in the first place, or suggesting that Apple allow TF an exception (and by conceit therefore open the door for other developers to want ‘exceptions’), or suggest that Apple permit it to be signed etc, so that TF will run. I found it VERY ironic, even comical, some of the comments posted here. No one take this personally, just my observations, not directed at anyone specifically. Thanks again to TotalFinder team for its work over the years Maybe it could convince some of you to switch to Mojave Please mind giving me some feedback if you try it. As I’ve stated in the README, there’s a lot of limitations due to SIP restrictions, so it’s not perfect, but in my case it does the job.Īny contribution would be greatly appreciated, as the project is fully open-source I’ve just released it on my GitHub here where you can download the. I’ve encapsulate the behavior in a small Objective-C app that allows to set a few settings (including custom shortcut). I’ve used Apple Script (ScriptingBridge to be exact), to deal with Finder window position. It has been a long/difficult/discovering-undocumented-APIs travel, but I’ve kind of succeeding replicate the basic behavior. Knowing that it will stop working with SIP enabled, prevent me from updating to Mojave.Īs Visor was the main feature I miss, I’ve tried to replicate the functionality, only using allowed API to be SIP-compliant. System is a late 2015 iMac 27" Did Apple Change the OS install? I've never been asked about keyboard / mouse prior to the 10.14.1 installer, nor has the USB installer ever had issues with the magic mouse.Like most of you, TotalFinder was super important in my productivity workflow. I haven't tried making a disk from version 8.0.1. I used a clean 8GB SanDisk USB stick, and a fresh download of the Mojave install app. Also the restore partition seems to remember the setup, so I haven't been asked again if I have to use it again. Oddly enough the Restore partition on the hard drive brought up the same assistant, but was able to link with the mouse just fine. On the USB stick, the system was never able to link with the magic mouse, even though it was on, and pressing the button / holding the button didn't seem to work. I have the Magic Mouse 2, and Apple Aluminum USB keyboard with the hub. While the process completed correctly, the issues came up after booting from the USB drive.Īpparently as of 10.14.1, the wireless Mouse / Keyboard assistant pops up. I had an unusual issue when using DiskMakerX version 8 to create a Mojave install disk.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |