![]() ![]() Turning off SIP is a stop gap, and even though I may turn off SIP personally because I’m technically savvy and no how to protect myself, I will NOT do that or recommend it for my non technical friends and family and co workers. I love TF, but the writing is on the wall. Once you open a ‘back door’ then you open a back door to potentially anybody.Īs a developer myself, I understand Darwin’s position. EVERY developer in the world is going to request an exception be made for it. ![]() Who decides what is ‘trusted’? How will you enforce? Hackers can already spoof app signatures and security signatures, so having an app signed is still no guarantee. The SECOND you go down that road, you have totally defeated the purpose and security of SIP. Some people have said why can’t Apple keep SIP, but just allow certain ‘trusted’ programs to make changes. Binary age totalfinder code#It’s not just changing a few lines of code here and there, it is a completely different approach and design, and Darwin understands that it isn’t worth his effort, but the y’all won’t listen. This would not be trivial, but a huge undertaking. Binary age totalfinder password#Without SIP in place, ANY DEVELOPER could write a program that can change pretty much anything in OS X, once the user puts in their password during install.įor TF to work without disabling SIP, would require a COMPLETE and FUNDAMENTAL rewrite and design of how TF works, basically TF would have to be rewritten as an app, like PathFinder or ForkLift. but OS X can no longer fly under the radar and hope malware developers don’t target Macs. ![]() I do not blame Apple, the reality is allowing code injection is an open invitation to malware, and frankly, it is AMAZING it has gone on this long without major infections on the Mac platform. Apple CAN NOT judge intent, it can only prevent outside programs from trying to circumvent the operating system, not the reason why. And this behavior is exactly what SIP is meant to prevent, because of TF can do it, so can any other program/developer. The technical process of replacing the program code is identical. The only difference is intent, malware does it to accomplish undesirable behavior TF does it to accomplish desired behavior. This is no different that what a Trojan or malware program does, Trojans and malware insert themselves into running code to change behavior. TF is not independent of Finder, it uses code injection, it LITERALLY seeks out and INSERTS its own code into Finder IN MEMORY at runtime. Those apps are separate apps, they launch and run independent of Finder. Comparing to programs like PathFinder, and saying why can’t TF do that, etc is irrelevant. Most of the misunderstanding is because of a lack of misunderstanding how TF works. Really? Calling the developer a liar is not the best way to convince him to help you. even went as far as to say, quote “I simply do not believe you…”. I am amazed, or maybe not, and the level of denial coming from all of you. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |