also can confirm that I can take my bosses p12 files and set them up on my computer using this script
KEYCHAIN_PATH1="$HOME/Library/Keychains/tmpsed1.keychain-db"
KEYCHAIN_PASSWORD1="$(openssl rand -base64 12)"
security create-keychain -p "$KEYCHAIN_PASSWORD1" "$KEYCHAIN_PATH1"
security unlock-keychain -p "$KEYCHAIN_PASSWORD1" "$KEYCHAIN_PATH1"
echo "keychain-path=$KEYCHAIN_PATH1"
echo "keychain-password=$KEYCHAIN_PASSWORD1"
#DEV_ID_APPLICATION=$(mktemp)
#echo $DEV_ID_APPLICATION
#base64 -i app.p12 | base64 -d >"$DEV_ID_APPLICATION"
#cat "$DEV_ID_APPLICATION"
security import app.p12 -f pkcs12 -k $KEYCHAIN_PATH1 -P password -T /usr/bin/codesign -T /usr/bin/security
export DEV_ID_INSTALLER=$(mktemp)
base64 -i installer.p12 | base64 -d >"$DEV_ID_INSTALLER"
security import installer.p12 -f pkcs12 -k "$HOME/Library/Keychains/tmpsed1.keychain-db" -P “password” -T /usr/bin/pkgbuild -T /usr/bin/security -T /usr/bin/productbuild
rm "$DEV_ID_INSTALLER"
security set-key-partition-list -S apple-tool:,apple: -s -k "$KEYCHAIN_PATH1" "$KEYCHAIN_PASSWORD1"
security list-keychains -d user -s "$KEYCHAIN_PATH1" $(security list-keychains -d user | xargs)
although for whatever reason I have to run each line individually as oppose to running the whole script.
then I can run "productbuild" fine
these commands are exactly what I'm using from
this github action template
Topic:
Code Signing
SubTopic:
Certificates, Identifiers & Profiles
Tags: