I should do this when I get a chance. Good to know. Glad I have a external Hd to store it on
Previously Downloaded OS X Installers No Longer Work
71–80 of 102 posts
Re: Previously Downloaded OS X Installers No Longer Work
#72Earlier quoted context omitted.
Apple is just awful about providing meaningful, useful errors. The worst is AirPlay. When it fails to connect, which is about 33% of the time, there's nothing. It doesn't even pop up a generic alert, it just silently (or not so silently, if you're playing music) reverts to local playback. Many other examples abound. Most errors at least provide a message, but one so generic as to be useless.
or TimeMachine "sparsebundle already in use" is the FOAD of error messages. I do love how the (now stale) tools to fix this are maintained by a volunteer on an external site unrelated to apple. I try not to be too grumpy about it, but I paid $3k for a laptop not to have to fucking deal with windows-style normal operation of the OS and related tools is busted and you're gonna sink hours into debugging it. And least wh…
> And least when linux breaks it tends to leave error messages and details in syslog...
Tends to. Not directly a Linux issue, but i was trying to figure out why one specific program was giving me corrupted MAC errors when connecting via sftp.
All searches indicated it was a network config issue, but no changes seemed to matter.
Eventually i checked the libs the program was compiled with and found the sftp one was "jurassic". One update later and no more errors.
that said, more often than not, a quick dmesg or tail /var/log/messages is all that i need to get something purring again.
Re: Previously Downloaded OS X Installers No Longer Work
#73> There is one caveat to all this. Apple won’t allow a newer Mac to download versions of OS X that aren’t compatible with that Mac, so on a 27-inch iMac with Retina display, for instance, the App Store app refuses to let you download Mac OS X 10.7 Lion. It's an edge case, but it's still annoying that I can't do this. What if I'm trying to get a non-functional older Mac running again? Stopping all users from doing thi…
There's a reason: Lion didn't have drivers for the hardware in question. OS X has all drivers, like for graphics etc. built in. That's why you're limited to versions after you Mac was made.
Re: Previously Downloaded OS X Installers No Longer Work
#74Earlier quoted context omitted.
Expired and compromised are two different things. If compromised, it will be published in a CRL with a reason flag.
The reason why certificates expire is because they will become easy to crack as computers get faster. So this would effectively be removing the expiry date. Now you can crack any old certificate and sign things claiming that you did it before the certificate expired.
As someone above has already said.
To do this, you'd need to compromise or convince a trusted timestamping authority to sign your signing request with an old date.
Re: Previously Downloaded OS X Installers No Longer Work
#75Earlier quoted context omitted.
Let's not forget it's not exactly Apple's fault that some developers remove their apps from the App Store. While it's annoying, and we can wish all we want that Apple would make apps permanently available once downloaded, it's really the developer of the app that has failed you, not Apple.
No, I'm pretty sure it's Apple's DRM that got us into this mess.
As far as I understand (but I have only distributed an OS X app outside the App store), the DRM is opt-in.
App store guidelines require that packages are sandboxed and signed. If you have a signed application, you can circumvent the signature check by disabling gatekeeper, removing the quarantine attribute, or control-clicking and choosing 'Open'.
The DRM mechanism is called 'receipt validation' and has to be enabled by the app developer:
https://developer.apple.com/library/mac/releasenotes/General...
I can sort of see why Apple provides this (to entice companies to publish in the app store), but a developed can decide to be customer-friendly and not check the receipt. So, I think it's fair to blame the developer, not Apple.
(Please correct me if I am wrong, as said, I never distributed an App Store app.)
Re: Previously Downloaded OS X Installers No Longer Work
#76All of this is just more evidence driving me away from using any kind of app store. I download and install apks on my android phone, and executable/tar installers on my computers. It's also the reason why I'll never buy an iOS device, or even open the Windows 10 store.
The best app stores are the ones beginning with apt-get, yum, slapt-get etc. I'd very much like to see a real Linux/Unix phone with a battery that isn't a joke being played on consumers. I'm tired of looking after an smartphone that requires as much care and time as a small child.
Re: Previously Downloaded OS X Installers No Longer Work
#77I had a handful of apps I use all the time stop working entirely about a week ago. They were purchased from the App Store but are no longer in the App Store. I am furious. I am willing to bet the expired certificate is the culprit. I've had to carefully maintain the .app's myself across a couple Mac's as Apple stopped letting you download things that are no longer in the store. Now they just don't work at all. The ol…
> I've had to carefully maintain the .app's myself across a couple Mac's as Apple stopped letting you download things that are no longer in the store. Since when? I always download .dmg's and install them outside of the Apple Store. You have to do this roundabout security measure in Preferences to run them, but they're always runnable...
You have to do this roundabout security measure in Preferences to run them, but they're always runnable...
Note: you don't have to. You can Control-Click and then choose 'Open' to bypass the signature or unsigned app check. You can also remove the quarantaine attribute with:
xattr -d com.apple.quarantine Your.appRe: Previously Downloaded OS X Installers No Longer Work
#78The whole "old installer" and "bootable disk" has been a pain-point since 10.8 for me. I have done 4 or 5 clean installs for friends in the last 6 months, and I tried to make a 10.10 or 10.11 bootable USB... no go - each time, a new issue. I have ended up every time using my older 10.8 (ML) install USB every time, then just firing off the free App Store upgrade to 10.11.
In newer Mac's (2012 onward IIRC) you can just boot into a net installer, and it goes and fetches the installer from the internet before re-installing.
Even older Macs (2010 models):
http://www.macrumors.com/2012/02/07/apple-brings-lion-intern...
Re: Previously Downloaded OS X Installers No Longer Work
#79The whole "old installer" and "bootable disk" has been a pain-point since 10.8 for me. I have done 4 or 5 clean installs for friends in the last 6 months, and I tried to make a 10.10 or 10.11 bootable USB... no go - each time, a new issue. I have ended up every time using my older 10.8 (ML) install USB every time, then just firing off the free App Store upgrade to 10.11.
In newer Mac's (2012 onward IIRC) you can just boot into a net installer, and it goes and fetches the installer from the internet before re-installing.
What happens if no internet connection is available?
Re: Previously Downloaded OS X Installers No Longer Work
#80Earlier quoted context omitted.
It means that the certificate was valid at the time of signing. Trying to sign an executable after the certificate has expired will not produce a valid code-signed executable. It totally makes sense. That it is possible to make the certificate valid by simply setting the system clock (this works both on Windows and according to the article, OSX) shows that the whole certificate expiration thing is basically useless.
I'm not sure I understand. It doesn't matter if the consumer of the certificate is able to set their clock to make the certificate/signature valid because most people don't do that, but if the producer of the signature can simply set their clock to produce a signature/timestamp combination that's considered valid by a consumer regardless of their clock, then what's the point of expiring the certificate? But yeah, it…
Yes I should have been more clear. A user which wants to run a signed executable with expired certificate can trick the validation process on his machine by setting the system clock back into the valid period.
But for the code-signer this trick doesn't work, the sign-tool needs to talk to a time-stamp server, usually owned by a certificate authority. I know that the Microsoft signtool.exe and the Java jarsigner can use timestamps, apparently on OSX this works too (search for --timestamp cmdline arg: https://developer.apple.com/library/mac/documentation/Darwin...)