Code-Signing Windows EXE with Sectigo Hardware Token (SafeNet . . . Code-Signing Windows EXE with Sectigo Hardware Token (SafeNet Authentication Client) on Ubuntu 22 04 Using PKCS11 Tools and osslsigncode Asked 2 years, 5 months ago Modified 1 year, 1 month ago Viewed 3k times
ssl - Adding CAA to pass sectigo CAA Check - Stack Overflow Here's Sectigo's official guide on how to add a CAA record I don't know what domain registrar you're using, but any decent provider should allow you to add a CAA record via the DNS setttings withing your account
Signing clickonce using Sectigo SHA384 EV certificate give unknown . . . It was something with sectigo timestamp url, digicert timestaping url has fixed the "unknown publisher" problem It is perfectly okay to use timestamp url across signing authorities I misunderstood it when I said I had an EV certificate It was actually an OV certificate and smart screen pop is well anticipated there until it start gaining on trust slowly
ACME certificates in Ansible using InCommon Sectigo CA I am really struggling with getting a working Ansible playbook that utilizes the ACME protocol and the InCommon Sectigo external account binding (EAB) and the quot;no challenge quot; option Lots
Sectigo timestamp server always using SHA384 instead of SHA1 The answer by @RickWeb specifies that one can use any timestamp server to produce a valid signature As for the Sectigo, I've been contacting their support and they don't provide much help, what I could discover is only that their timestamp server is always sending SHA384 and entirely disregards the parameters placed into the SignTool