# DigiCert KeyLocker and SetupBuilder

**URL:** <https://clarionhub.com/t/digicert-keylocker-and-setupbuilder/6898>\
**Category:** uncategorized\
**Created:** [January 5, 2024, 9:40am UTC](https://clarionhub.com/t/digicert-keylocker-and-setupbuilder/6898 "2024-01-05T09:40:10Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bjarne\_Havnen](https://clarionhub.com/user_avatar/clarionhub.com/bjarne_havnen/32/1350_2.png) [@Bjarne\_Havnen](https://clarionhub.com/u/Bjarne_Havnen)\
**Post date:** [January 5, 2024, 9:40am UTC](https://clarionhub.com/t/digicert-keylocker-and-setupbuilder/6898/1 "2024-01-05T09:40:11Z")

</div>

Also posted on Lindersoft forum, but perhaps relevant here since many Clarion developers use Setupbuilder?  
I am about to renew my certificate now. A year ago I gave up on Sectigo and bought an expensive DigiCert certificate, time is money, after all.  
DigiCert has introduced a “DigiCert KeyLocker” that is a some cloud key storage.  
I have skimmed through the docs and so far I do not understand how this works, particularily with SetupBuilder, which manages all my signings today.  
Futhermore, there is a limitation of 1000 signs per key. Probably enough, but when I have signed 20 files in a setup, I can’t batch build and prepare installs for every version anymore.

Is it possible to use DigiCert code signing with Digicert KeyLocker, or should I go for the hardware token? I don’t understand how hardware token works either, please excuse my ignorance.

(Man, how I miss the days where I could concentrate my efforts on developing applications)

---

<div class="post-metadata">

**Author:** ![Julian](https://clarionhub.com/letter_avatar_proxy/v4/letter/j/74df32/32.png) [@Julian](https://clarionhub.com/u/Julian)\
**Post date:** [January 6, 2024, 9:11am UTC](https://clarionhub.com/t/digicert-keylocker-and-setupbuilder/6898/2 "2024-01-06T09:11:40Z")

</div>

This is worth a read..

> [@Notes on signing code with your own hardware (Yubikey)](https://clarionhub.com/t/notes-on-signing-code-with-your-own-hardware-yubikey/6655):
>
> I missed the opportunity to get a non-hardware-based code signing certificate last May. Here are some notes of the process to get a new one. First option is to get it through Lindersoft. Cost is US$681 for the 3 years certificate, plus $50 for the USB token and $40 for standard shipping ($90 for expedited shipping). Average cost is $257 per year. Googling I found the site [SignMyCode](https://signmycode.com/) which is a certificates reseller, but has a lot for resources and tutorials. SignMyCode lets you buy a certi…