<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div><br><blockquote type="cite"><div><div style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><blockquote type="cite"><div><div style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div><br></div><div>I assume done with jpackage by indicating something like —mac-sign only? If wrong feel free to correct.</div></div></div></blockquote><div><br></div><div>No, it is always done if —mac-sign is NOT specified and we doing ad-hoc signing on app bundle only. PKG will not be ad-hoc signed.</div><div>If —mac-sign is provided we will use certificate provided with —mac-sign to sign app image and PKG as before.</div><div><br></div><div>Thanks,</div><div>Alexander</div></div></div></blockquote><br></div><div>I always do dmg or app-image for quick testing. I haven’t done any pkg yet. </div><div><br></div><div>So if I understand correctly now for app bundle types - dmg or app-image, some signing is always done. Certificate if signing is indicated and it is provided or adhoc if it isn’t indicated as a default. I didn’t know this.</div><div><br></div><div>Thanks</div><div><br></div><div>Mike </div><br></body></html>