3 ms·

> Apple gets certificate revocation requests all the time, to disable test builds, disabled badly bugged software versions, to disable software for licensing re

by _qulr 6y ago

> Apple gets certificate revocation requests all the time, to disable test builds, disabled badly bugged software versions, to disable software for licensing reasons. How do you know this? What is the evidence for this claim? The strange thing about this claim is that certificate revocation does not disable specific builds, it disabled every piece of software ever signed with the cert, so this wouldn't even accomplish what you claim it accomplishes.

deleted 6y ago
[deleted]
simonh 6y ago
You just sign different builds with different certs. That’s how come this revocation only disabled particular HP drivers, not ever piece of software for the Mac released by HP.
- _qulr 6y ago
  > You just The reason we're even discussing this issue is that there was a huge public fallout. You don't "just" do anything. This was a nightmare for many HP users, who just couldn't print at all. How do you "just" deliver new builds to users when the old builds won't even open?
  - simonh 6y ago
    I was simply responding to the claim that the only reason to revoke a cert is to disable malware, and that such requests were very rare, and gave a counter example showing this is not true. One of the uses of certs is to sign test builds with a different cert from the production release, so that you can ask Apple to disable them after release. So Apple gets requests to revoke certs for this, and other reasons all the time. In this case HP had used a different cert for these drivers as against other drivers, showing that they used different certs for different purposes, that's all.
    - _qulr 6y ago
      > One of the uses of certs is to sign test builds with a different cert from the production release, so that you can ask Apple to disable them after release. So Apple gets requests to revoke certs for this, and other reasons all the time. In this case HP had used a different cert for these drivers as against other drivers, showing that they used different certs for different purposes, that's all. Where in the world are you getting this information? Citation please. Apple Product Security does not talk. About anything. So any claims about what Apple receives are dubious at best. > you can ask Apple to disable them after release There are very strict limits on how many Developer ID certs you can generate. You can't generate them willy-nilly. So this claim is also dubious at best. I have a developer friend who ran into this limit, and it took him months to resolve this issue with Apple Product Security. He was stuck. Again, you just seem to be inventing things in your own mind with no first hand knowledge. Are you even a Mac developer? Can I download one of your Developer ID signed apps?

by _qulr 6y ago

deleted 6y ago

[deleted]

simonh 6y ago

You just sign different builds with different certs. That’s how come this revocation only disabled particular HP drivers, not ever piece of software for the Mac released by HP.

_qulr 6y ago
> You just The reason we're even discussing this issue is that there was a huge public fallout. You don't "just" do anything. This was a nightmare for many HP users, who just couldn't print at all. How do you "just" deliver new builds to users when the old builds won't even open?
- simonh 6y ago
  I was simply responding to the claim that the only reason to revoke a cert is to disable malware, and that such requests were very rare, and gave a counter example showing this is not true. One of the uses of certs is to sign test builds with a different cert from the production release, so that you can ask Apple to disable them after release. So Apple gets requests to revoke certs for this, and other reasons all the time. In this case HP had used a different cert for these drivers as against other drivers, showing that they used different certs for different purposes, that's all.
  - _qulr 6y ago
    > One of the uses of certs is to sign test builds with a different cert from the production release, so that you can ask Apple to disable them after release. So Apple gets requests to revoke certs for this, and other reasons all the time. In this case HP had used a different cert for these drivers as against other drivers, showing that they used different certs for different purposes, that's all. Where in the world are you getting this information? Citation please. Apple Product Security does not talk. About anything. So any claims about what Apple receives are dubious at best. > you can ask Apple to disable them after release There are very strict limits on how many Developer ID certs you can generate. You can't generate them willy-nilly. So this claim is also dubious at best. I have a developer friend who ran into this limit, and it took him months to resolve this issue with Apple Product Security. He was stuck. Again, you just seem to be inventing things in your own mind with no first hand knowledge. Are you even a Mac developer? Can I download one of your Developer ID signed apps?