cohost.blogg.se

1. #Hp scan to computer mac not working drivers#
2. #Hp scan to computer mac not working update#
3. #Hp scan to computer mac not working driver#
4. #Hp scan to computer mac not working software#
5. #Hp scan to computer mac not working code#

However, when there’s a certificate issue with a piece of Mac software, it affects everyone, everywhere, who is using that software. Mistakes happen, and Apple isn’t always to blame in cases like this. With any security software, false positives are always a potential problem. All his apps suffered the same issue as HP’s print drivers.

#Hp scan to computer mac not working code#

As an example, there was a case back in August where a developer named Charlie Monroe reported that his entire Apple developer account was deleted, and his code signing certificate was revoked. This isn’t the first time that certificates have been revoked in error. We’re still seeing new cases reported days later.

#Hp scan to computer mac not working driver#

In the meantime, we recommend users experiencing this problem to uninstall the HP driver and use the native AirPrint driver to print to their printer.Īpple was able to reinstate the revoked certificate, which fixed the problem for some people, but not everyone. This caused a temporary disruption for those customers and we are working with Apple to restore the drivers.

We unintentionally revoked credentials on some older versions of Mac drivers. However, it turned out, according to a statement from HP given to The Register, that HP itself had erroneously requested that the certificate be revoked. It was initially assumed that Apple had erroneously revoked the certificate. Revoking a certificate is usually done by Apple when a piece of malware is discovered to be signed using that certificate.

#Hp scan to computer mac not working drivers#

With some digging, we found that the source of the issue was that the developer certificate used to sign these HP drivers had been revoked.

#Hp scan to computer mac not working update#

However, the timing of the last XProtect update didn’t line up with the very sudden and widespread emergence of the issue.

#Hp scan to computer mac not working software#

(XProtect is a basic form of anti-malware protection built into macOS, which aims to prevent malicious software from running.) The thought was that this was a false positive in other words, XProtect was erroneously detecting legitimate files as malicious. Initially, there was a lot of finger pointing at a recent XProtect update. Samples of the software that we obtained appeared to be legitimate, with no signs of malicious behavior. The messages generally appeared when people were trying to print to their HP printers. However, we noticed that this “malware” was all (mostly*) related to HP printing drivers. The “malware” was being reported by the built-in anti-malware features in macOS, and there were a dozen or more different processes that macOS claimed “will damage your computer,” with a check box reading “Report malware to Apple to protect other users.” Sounds pretty scary, right? As we dug into the issue, however, we saw that there was a pattern in the screenshots we were seeing. Last Thursday evening (October 22), we started seeing an influx of support requests from people complaining about some new malware that we weren’t detecting. The certificates used by HP are no exception. The certificates used to sign software on macOS (and iOS, for that matter) are provided and managed by Apple. HP makes printers, and thus makes print drivers, and of course those drivers are signed, as they should be. This obviously applies to apps you download from the Internet or the App Store, but it also applies to more prosaic software, such as print drivers.

Your software will also probably just get deleted by many people. As a developer, if you don’t sign your Mac software, your users will have trouble running it, and you (or your support staff) will get countless help inquiries. In recent years, Apple has done more than just support code signing… it’s come as close as is reasonably possible to requiring code signing. This allows the system, and the user, to verify which developer created the software, and check that it hasn’t been modified since it was created. Code signing involves using a certificate to cryptographically sign a piece of software. For quite a few years now, Apple has supported what is called “code signing” on macOS. How does this relate to Apple and HP, you ask? Good question. Not many people actually look at these certificates, of course, but doing so is a sure-fire way to avoid a phishing site.

For example, when you try to connect to your bank site, the site’s certificate will verify that the site really does belong to your bank. With web traffic, these certificates are used to encrypt the data, but they support more than just encryption.Ĭertificates also allow for validation. Code signing and certificatesįirst, it’s important to understand that when I say “keys,” what I really mean is “certificates.” These certificates are similar to the ones that are the basis for secure communication between a web server and your browser. This is a story of those keys, and how a Hewlett Packard (HP) error caused problems for a lot of people. Apple holds the keys to nearly all recent Mac software.