Skip to main content
Solved

Installomator = no usable signature

  • Apr 20, 2023 9:09 AM UTC
  • 3 replies
  • 93 views

Forum|alt.badge.img+5

Hi, I know some of you are using Installomator to update third party software and since I need to clear some time I decided to give it a go on a small part of our Macs. They are more or less all the same under ventura.

 

Works great on most of our macs, but for some reason, it does not work on several of them, the logs is giving the same error :

 

firefoxesrpkg : ERROR : Error veryfying Firefox.pkg error : Firefox.pkg: rejected
source =no usable signature.

 

 

Any recommendations ?

Best answer by joshuasee

If its working for most clients, work on potential client side issues first. Check that the failing machines are updated and have the correct time set on their clocks. SSH into or start Terminal on an affected machine and manually run through the steps Installomator would with curl, codesign, etc, to see what errors you get.

View original

3 replies

Forum|alt.badge.img+18
  • Valued Contributor
  • Answer
  • Apr 21, 2023 2:24 PM UTC

If its working for most clients, work on potential client side issues first. Check that the failing machines are updated and have the correct time set on their clocks. SSH into or start Terminal on an affected machine and manually run through the steps Installomator would with curl, codesign, etc, to see what errors you get.


Forum|alt.badge.img+5
  • Author
  • Contributor
  • Apr 23, 2023 2:06 PM UTC

If its working for most clients, work on potential client side issues first. Check that the failing machines are updated and have the correct time set on their clocks. SSH into or start Terminal on an affected machine and manually run through the steps Installomator would with curl, codesign, etc, to see what errors you get.


Clever idea, I'll try that thanks !


Forum|alt.badge.img+5
  • Author
  • Contributor
  • Apr 24, 2023 12:42 PM UTC

If its working for most clients, work on potential client side issues first. Check that the failing machines are updated and have the correct time set on their clocks. SSH into or start Terminal on an affected machine and manually run through the steps Installomator would with curl, codesign, etc, to see what errors you get.


Thanks again, finally managed to pinpoint the issue. The script was looking for a PKG while I was getting a DMG…