What’s important is the process, rather than the particular tools mentioned to implement it. Of course, at least in part, it uses my own s/w (if I can’t trust my own software, who can? And besides, my s/w is free!), but there are other ways to achieve the same thing. In this post I’m going to share with you (part of) my security set up. Rather than relying on others for your protection, the solution is to have a system in place that will protect you and allow you to recover completely and quickly regardless of the source of the infection. With several hundred malware infected apps discovered in the App Store last month alone, what’s clear is that leaving your security up to someone else (even if its Apple) is short-sighted at best, and disastrous at worse, particularly if your reliable source just happens to be of great interest to hackers (especially if its Apple!). purge the RAM then toggle the setting again in whatever app you’re using to toggle invisible files.īack in the days of Mountain Lion when Apple introduced GateKeeper, a lot of talk was heard about the best way to protect your mac being to only download apps from the App Store. issue a ‘killall Finder’ on the command line In both cases, there’s a couple of ways to deal with it (albeit temporary until Apple applies a proper cure): We believe a related bug is that Finder sometimes fails to show the new version of an app in the Finder preview after the app has been updated. The bug basically ends up with Finder showing the opposite of both what the app shows and what ‘defaults read’ shows (see image above the value should be ‘1’ when invisible files are visible). In 10.11 I see a reproducible though not always consistent bug when using any GUI-wrapped app to toggle this Finder setting. In every version of OS X from 10.6 thru to 10.10 this works as expected. The standard method for doing this, either in Terminal or in code (via NSTask) has always beenĭefaults write AppleShowAllFiles -bool true killall Finder. So, here we are at version 2.18 … we’re a bit breathless, so it’s time for a sit-down and a nice cup of tea!Ī number of 3rd party apps, including my own DetectX and FastTasks 2, offer a GUI way to hide/reveal invisible files in the Finder. Luckily that report came in pretty quick (many thanks to Al), and we were able to address the bug with a simple code tweak (if you got bit by that bug, please open and then close the Licensing window before attempting to update to v2.18). In 2.17 we also fixed a false positive in the Keylogger detector and updated some search definitions.Īlas, we’d inadvertantly let a bug slip in with v2.16 that prevented DetectX from quitting in certain situations. If you have a version of MS Silverlight that is not the currently patched version, you’ll see a warning in the log drawer when you run a search. That resulted in 2.17, which added a Silverlight check to the detector Search function. All well and good, until we noticed a serious security issue with Microsoft Silverlight had recently surfaced, and we didn’t want to wait to address it. It all started with 2.16, which introduced some changes to the licensing and user interface. We’ve had a bit of a mad day here at Sqwarq and Applehelpwriter, releasing three updates within a few hours of each other for DetectX. The beta is still in an early stage and more features are slated as it develops, but feel free to tell us about anything that you feel could be done better or things that you’d like to see added. The beta version is free to use for both Home and Commercial users, so just head off over to its home page and grab yourself a copy!ĭon’t forget to keep us informed of how it goes. There’s tons more to DetectX Swift, but the best way to find out about it is just to try it. One of the coolest things I like about the new History function is that you can run a diff on any previous run against the latest run, immediately seeing how they differ. There’s changes in the History view, too, both in the display and functions. The new Profile view employs some super cool dynamic highlighting and lets you inspect the contents not only of directories but also of scripts, plists and other files that could execute troublesome code on your mac. The Search uses some fancy heuristics as well as hard-coded and live update search definitions to ensure it provides the very best in security threat scanning. The new version is called DetectX Swift because (yeah, you guessed it) I wrote it in Swift and because it’s considerably faster than its older sibling.ĭetectX Swift’s got a new interface, but there’s far more going on under the hood. It’s been unusually quiet on Applehelpwriter these past few months, and the reason is that I’ve been devoting all my time and efforts to the new version of DetectX.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |