Skip to main content

OS X Security Lapses

Who says that Microsoft has all the hackers and crackers problem? In recent years , this has been the selling point of most non Microsoft OS. Partially , they are right. LINUX and UNIX has been consistent in this field but what about Apple? I could not blame the designers of Microsoft , the patches are always there, but its the price to pay for being so famous to end users ..making it more interesting to hackers. This is not in defense of the Bill Gates company , just a reflection on how much other OS firms have considered their security features.

Here is a nice article in a blog i read named Digital Binary ( a good blog ) about security issues regarding the new OS X from Aple. Read on....
Booming of Apple’s Mac OS X signals all the hacker to shift their eyes on them. Less security compared to current UNIX and the current transition plan into Intel architecture will just make it worse.

OS X platform are based on UNIX that are less vulnerable compared to windows platform. Yet OS X seems forgetting to put security measure that UNIX has done in twenty-years past and make it more vulnerable than UNIX these days.

"This is almost certainly the year of the OS X exploit," said Jay Beale, a senior security consultant for Intelguardians and an expert in hardening Linux and Mac OS X systems. "The OS X platform may be based on a Unix platform, but Apple seems to be making mistakes that Unix made, and corrected, long ago."

Apple also has been widely criticized for not talking about the details of its vulnerability-response process or how it manages security incidents. While Microsoft has the lion's share of security problems--and the Mac OS X hardly any--the Redmond, Wash., based software giant has received high marks from security researchers for its responsiveness, while Apple has often been the focus of complaints.

"On a good day, Apple doesn't even make it to Microsoft's level of security awareness," Beale said.


"No matter how good your security platform is, negligence and misjudgement can bring it down."


Comments

Popular posts from this blog

Getting Started with Stateless : A Lightweight Workflow Library Alternative for .NET

Image Credit: https://www.pioneerrx.com A year ago, I was looking for a simple workflow manager for a project I was working. Its a medium sized application that involves tracking the state of assets in the system. Back in 2008, Microsoft (MS) introduced new technologies along with the release of Visual Studio 2008: Windows Presentation Foundation (WPF), Windows Communication Foundation (WCF), and  Windows Workflow Foundation (WF). Having worked in a company utilizing mostly MS products for development, my first option was to go with WF. After doing some time reading and studying the library, I paused and decided it was too complex for my requirement. Using WF would be an overkill and the fact that it has, a rather, steep learning curve, there has to be another option. My mind toyed with the idea of developing a simple workflow library myself. It would be a learning experience but it might end up consuming a lot of time. Why reinvent the wheel? So I started querying the ...

Hiding Unwanted Python Folders and Files in Visual Studio Code

Visual Studio Code is a universal editor and pretty good at it. However, the explorer view maybe cluttered with the automatically generated folders and files confusing developers. Python is no different. Below are example files and folders generated by Python. The __pycache__ folder and *.pyc files  are totally unnecessary to the developer. To hide these files from the explorer view, we need to edit the settings.json for VSCode. Add the folder and the files as shown below: Copy and paste the lines below : "**/*.pyc" : { "when" : "$(basename).py" }, "**/__pycache__" : true

How to Kill a Slow Process using DOS Batch File Script with TaskKill and TaskList

If you are still trapped in the era of batch files and command lines in Windows environment, here is something you can add to your DOS cheat codes.  Lucky for us here, we are still using DOS batch file to implement installation of some updates to our system. Here is a simple batch file script that is designed for slow systems that requires a significant amount of time to kill a particular process. The requirement is simple,  do not start any copying or moving of files until  the process ( i.e. MyProcess.exe) is totally killed by DOS. The simplest solution would be to use TASKKILL to kill the process, wait for a few seconds  then start copying/ moving of files there after. Unfortunately, while we were testing this simple step on a slow machine, DOS would take an awful lot of minutes to kill the process in question. Thus, when our delay is reached, we would encounter error on copying/moving files that is currently used by the unkilled process causing a failure on ...