http://sworddance.com/blog/2009/08/07/mac-osx-the-most-insecure-os-around/#utm_source=rss&utm_medium=rss&utm_campaign=mac-osx-the-most-insecure-os-around Tue, 17 Jan 2012 04:36:33 +0000 hourly 1 http://wordpress.org/?v=3.3.1 http://sworddance.com/blog/2009/08/07/mac-osx-the-most-insecure-os-around/comment-page-1/#comment-16813 Fred Brown Tue, 18 Jan 2011 23:24:37 +0000 http://www.sworddance.com/blog/?p=476#comment-16813 This is only 1/10 of the story. OSX was built from a perfectly good unix distro "BSD", but Apple ripped /all/ of the security controls and mechanisms out to make it "easy to use" ... yeah... you mean easy to hack ! The device drivers (network, video), boot, OS, memory sharing, are full of holes and there are no guards. It /is/ more insecure than WinBlows, and that's saying something. You can try to lock down, harden, AV, firewall these tinker toys all you want, but cracking them open is childsplay because of the fundamental lack of security throughout. Get RH Linux, enable SELinux, apply DoD stigs and then you have half a chance. With Windows and Mac, you have no chance. This is only 1/10 of the story. OSX was built from a perfectly good unix distro “BSD”, but Apple ripped /all/ of the security controls and mechanisms out to make it “easy to use” … yeah… you mean easy to hack ! The device drivers (network, video), boot, OS, memory sharing, are full of holes and there are no guards. It /is/ more insecure than WinBlows, and that’s saying something. You can try to lock down, harden, AV, firewall these tinker toys all you want, but cracking them open is childsplay because of the fundamental lack of security throughout. Get RH Linux, enable SELinux, apply DoD stigs and then you have half a chance. With Windows and Mac, you have no chance.

]]> http://sworddance.com/blog/2009/08/07/mac-osx-the-most-insecure-os-around/comment-page-1/#comment-16482 Renat Sat, 08 Aug 2009 17:52:10 +0000 http://www.sworddance.com/blog/?p=476#comment-16482 Hm.. my only suggestion would be - no byte sent outside VPN connection and you are safe. Hm.. my only suggestion would be – no byte sent outside VPN connection and you are safe.

]]>