6 Comments
- newbill123, on 11/15/2007, -0/+2It's probably a good thing that user interface strings and localizations are included in the signing. It's not code, but someone could easily change a destructive choice (e.g. "Delete File") into an innocuous sounding one (e.g. "Save") even worse would be just swapping the keyboard shortcuts which are even less likely to be noticed.
- roustk, on 11/15/2007, -0/+1Well, try to run Xslimmer or Monolingual on any code signed app and then verify the signature -- codesign will return an error.
- colincornaby, on 11/15/2007, -0/+1This isn't true. Code slimming will not affect code signed apps. From the Apple docs on code signing ( http://developer.apple.com/documentation/Security/ ... ): "Because each architecture component is signed independently, it is all right to perform universal-binary operations (such as running the lipo command) on signed programs. The result will still be validly signed as long as you make no other changes." Obviously something else is at work here.
- roustk, on 11/15/2007, -0/+1I have to say that I used Monolingual on Tiger and I love the idea of saving gigabytes of space on my hard drive. However, on Leopard it is a completely different story.
- SwitchedtoMac, on 11/15/2007, -0/+0Collin,
Have you tried it? - SwitchedtoMac, on 11/15/2007, -0/+0collin, Have you tried it?


What is Digg?
Digg is coming to a city (and computer) near you! Check out all the details on our