When I plug in my iPhone, AMPDevicesAgent gets EXC_CRASH (SIGKILL (Code Signature Invalid)). It's not asking me for a password with Keychain. I'm reading this may have to do with an invalid digital signature. What's the problem and resolution? I was reading that the following may fix, but don't want to force any digital sig if I have a security problem: codesign --force --deep --sign - /Applications/App.app /System/Library/LaunchAgents/com.apple.AMPDevicesAgent.plist /System/Library/PrivateFrameworks/AMPDevices.framework/Versions/A/Support/AMPDevicesAgent /Users/$USER/Library/HTTPStorages/com.apple.AMPDevicesAgent

Let's say I received a PDF document that supposedly was signed with a digital certificate, instead of pasting a hand-drawn signature. Can I use Preview to see the signature's properties and check if it is valid? If so, how?

My isight doesn't works, i use another mac for create my digital signature. How can I import and set my signature on my mac ? where storage it?

I would like to output the result of

--assess --verbose path/to/app.app

in a notification dialog using Automator. However, it doesn't work. I assume it's because the command returns a multi-line output, such as

/Applications/Test.app: accepted

=Notarized Developer ID

I tried passing the output of the shell script to a Set Value of Variable action and then putting the variable in a Display Notification action. I tried using a Ask for Confirmation action instead. Since it didn't work, I tried passing the output of the command to a New TextEdit Document action, but the new document ended up blank. I tried appending

| tr '\n' ' '

to replace the new line character with a space but that didn't work. I would appreciate any help. Thanks.

On macOS Big Sur (11.0.1), running system_profiler SPExtensionsDataType in terminal includes a kext named AppleUSBEthernetHost from an unknown developer that has a signature validation error: It appears to maybe be an old version of a kext for which there is a newer version properly signed by Apple at a different path. This kext very possibly existed before I upgraded to Big Sur. I just looked at kexts now to ensure that I'm not running any unsupported legacy kexts. Is it advisable / safe to remove the kext with the signature validation error? What might have put it there? What might have caused its signature error if it was once there without an error? kext with signature validation error:

AppleUSBEthernetHost:

      Version: 7.0
      Last Modified: 2019-07-18, 11:56 PM
      Bundle ID: com.apple.macos.driver.AppleUSBEthernetHost
      Notarized: No
      Loaded: No
      Obtained from: Unknown
      Kind: Intel
      Architectures: x86_64
      64-Bit (Intel): Yes
      Location: /Library/Apple/System/Library/Extensions/AppleUSBEthernetHost.kext
      Kext Version: 7.0
      Loadable: No
      Signature Validation Errors: Kext signature validation error code -67050
      Dependencies: Satisfied
      Signed by: Unknown

Newer kext without errors, properly signed by Apple:

Version: 8.1.1
      Last Modified: 2020-01-01, 3:00 AM
      Bundle ID: com.apple.macos.driver.AppleUSBEthernetHost
      Notarized: Yes
      Loaded: No
      Obtained from: Apple
      Kind: Universal
      Architectures: arm64e, x86_64
      64-Bit (Intel): Yes
      Location: /System/Library/Extensions/AppleUSBEthernetHost.kext
      Kext Version: 8.1.1
      Loadable: Yes
      Dependencies: Satisfied
      Signed by: Software Signing, Apple Code Signing Certification Authority, Apple Root CA

I've been using the Preview App to generate my passwords and to be able to sign virtually. But now what I want to do **is to erase them completely, so that nobody can access them.** For example, if I sell my Mac in a hurry, or if someone accesses my Mac, I want to make it impossible to access those signatures. I don't mean to press the X (cross) that appears after generating the signature; because I think that by pressing that, that signature must be saved somewhere. I don't know. What I'm saying is to **eliminate it in a more strict way, forever.** Is it possible to do this? How?

A signature of someone, who I've never heard of, appeared in the signature list of my Preview app. I have noticed that the signature is stored in keychain and can be found in the KeyChain Access app. I don't think I have login my Apple ID on other machines, so it's unlikely that it's synced via the iCloud. I have also checked the devices under my iCloud account, nothing suspicious. Maybe someone has touched my Macbook? But it's not very sensible for someone I don't know to sneak into my home just to create a signature using my password protected Macbook but did not do any other harm, at least to my knowledge, to my other belongings. What could be the possible reasons?

I have received a signed and well encrypted E-Mail. I now want to reply to this particular sender using his public key in Apple Mail. But when I press the reply Button, the encrypt icon stays grey. Do I have to import his public key into my key chain first? And if yes, how does this work?

Apple has announced that all programs in the next release of its operating system must be notarized. > Beginning in macOS 10.14.5, all new or updated kernel extensions and > all software from developers new to distributing with Developer ID > must be notarized in order to run. In a future version of macOS, > notarization will be required by default for all software. How will this affect programs written in Python? Will they need to be notarized? Or will notarization be required for using certain APIs? How about browser plug-ins? Will they require notarization?

I click on the signature button in the Preview.app toolbar: The following box pops up: I click on the Click Here To Begin button. The box is now ready for input: However, I cannot get any markings at all to show up as my signature. My box always looks like the above image. I've tried doing the above in an image document and a PDF document. I've tried holding down the trackpad while writing and not holding the trackpad down while writing. I've tried using a mouse. Is there a fix for this bug, so that I can use my Macbook trackpad to write my signature? Note: the Camera-based signature method technically works on my machine. However, its rendition ability isn't great. ---------- OS X El Capitan, version 10.11.6. ----------

I'm looking for a tool to digitally sign PDFs with the private key of my X.509 certificate. macOS' Preview app only copy a scan of my handwritten signature into a pdf...

So, I've upgraded OSX to Sierra, but I need to downgrade (long story), and OSX won't let me because I didn't create a Time Machine backup before upgrading. So I have downloaded the Install OS X El Capitan.app image using BitTorrent. I assume Apple are wise enough to digitally sign their OS images, such that this is safe. But I would like to know for certain before proceeding.

I have the occasional need to scan and/or convert scanned images into PDF format. OS X Mountain Lion does this natively, but as far as I can tell it's just an image wrapped in a PDF, so text selection, search, and signing the document isn't possible. I've tried out the latest free trial of Adobe Acrobat Pro, which has scan to PDF functionality that does precisely what I want. Combined with its ClearScan option I've managed to get pretty decent looking PDFs at a reasonable size that I can search, select text from, and digitally sign. Awesome! Except it costs $199, which is a little steep for very occasional use. That being said, is there anything else out there that has similar functionality at a lower price point? I'm not expecting free. One app that keeps coming up in my search is PDFScanner , which makes the resulting PDF searchable by running it through OCR, but from what I can tell it's the equivalent of Adobe's searchable image format. One important requirement is being able to digitally sign the resulting PDF, but it's not clear if PDFScanner can do this. Text selection is nice but not absolutely necessary.

I have a .bundle that is digitally signed. I can verify this by opening the bundle by selecting "Show Package Contents" and indeed there is a _CodeSignature directory underneath the bundle. However, I am trying to figure out *who* is the signer of the bundle. Is there any way with Xcode, or any other tool, command line or otherwise, to view the certificate that was used to sign the bundle?