This is from Macworld's May 2012 edition.

I hate to be a stick in the mud, but the issue with the "Trusted Security Certificate" model is that if the issuing authority, in this case Apple, is breached the damage can be potentially huge because people believe that software signed by the issuing authority is safe they tend to allow it to anything they want. Microsoft went through this a while back.

The biggest incident of this type (in my mind) was the hacking of Verisign back in 2011.

http://www.huffingtonpost.com/2012/02/02/verisign-hack_n_1249275.html

There have been a few others as well...and in one case false certificate claiming that malware was authentic MS software were distributed. Will look for the link on that later.

---

"Come out from man foul spirit. What is thy name?" And he said unto him, "Our name is legion, for we are many." Gospel of Mark, 5 - 8

Patriotism is your conviction that your country is superior to all others because you were born in it. George Bernard Shaw

Let's take the advice and unplug the cable

"Let's take the advice and unplug the cable"

...mmmm, unfortunately we have WiFi these days.

---

"Come out from man foul spirit. What is thy name?" And he said unto him, "Our name is legion, for we are many." Gospel of Mark, 5 - 8

Patriotism is your conviction that your country is superior to all others because you were born in it. George Bernard Shaw

Good news for all of those using Firefox for Mac.

Mozilla preparing Mac code signing for Mountain Lion’s Gatekeeper

By Ryan Paul - May 17 2012, 6:30pm EDT

Signing will be enabled for the nightly build channel next week.

Mozilla developer Ben Hearsum wrote a blog post today, describing the status of the effort to integrate code signing into the automated build process for Firefox on Mac OS X. Mozilla aims to turn on code signing for the browser’s nightly builds by next week.

The application needs to be signed so that it will continue to work on Mac OS X 10.8, codenamed "Mountain Lion," which is expected to launch later this year. Mountain Lion introduces a new security feature called Gatekeeper that will prevent the platform from executing applications that come from untrusted sources.

Gatekeeper supports several different configurations, but the default setting will only allow users to run software that has been signed with an Apple-supplied developer key or that comes from the Mac App Store. Third-party developers who do not distribute their applications through the Mac App Store will need to register with Apple, obtain a developer ID and start signing their applications.

Complying with the signing requirement won’t pose any major difficulties for the vast majority of Mac developers who already use Apple’s development tools. It might not be quite as simple, however, for applications with specialized build processes, many different builds, and extremely frequent releases. One such application is Mozilla’s Firefox Web browser.

As Hearsum previously described in a February blog post about Firefox build automation, Mozilla already performs code signing with GPG and Authenticode signatures during the build process. Some early work on integrating native Mac OS X signing into the build process began in 2010, but it was never completed. Hearsum resurrected the project this year and has been moving it forward towards production readiness.

One challenge for Mozilla was determining the best version of OS X to use for signing. Mozilla’s Erick Dransch reported in a blog post earlier this year that Firefox builds signed on 10.7 didn’t verify on 10.5, which is why Mozilla decided to use 10.6 on their signing servers. Dransch also described how Mozilla uses the command-line security utility on Mac OS X to unlock the keychain where the signing key is stored without having to deal with an interactive prompt that would interfere with automation.

Mozilla also had to make some decisions about what kind of Apple-approved certificate to use and what level of permission to assign to various kinds of Firefox builds. The “dep” and “try” builds, which are only used internally by Firefox developers, will be signed with a self-signed certificate, which means that they won’t be compatible with the default settings on 10.8.

All of the user-facing builds will be signed with official Developer ID certificates, but Mozilla plans to use two separate IDs. One ID will be used for the Nightly and Aurora builds. A second ID will be used for the beta and release builds. Hearsum wrote in his blog post that the purpose of using two separate IDs "gives us some degree of isolation in terms of certificate revocation."

Some recent rumors suggest that Mountain Lion could arrive within the next month, possibly even during WWDC in the first half of June. Mozilla is working to ensure that they have a stable version of the browser that has been signed ready for the launch.

http://arstechnica.com/apple/2012/05/mozilla-preparing-mac-code-signing-for-mountain-lions-gatekeeper/

---