Cheap Code Writing Digi ID besides Verisign

[DanOfEarth]

I'm distributing Excel workbooks to clients as tools, and I'm tired of the 2007 security either flagging or shutting down my code. Does anybody know of a cheap "Code-writing Digital ID" service besides Verisign ($499.00 per year). If we have to pay it, we might.

I found other CA's services for $166.00 per year, but I can't make heads or tails of what they include. They keep pushing stupid SSL certificates.:banghead:

Dan

[DanOfEarth]

I think I answered my own question.

For whatever it's worth, this might come in handy...

Apparently, the cheapest solution out there that specializes in "VBA Office and Macro" signing is:

http://www.globalsign.com/developer/code-signing-certificate/index.htm
They sell their services for $229.00 a year. If you buy three years, it goes down to about $180.00 per year.

The below company also sells certificates for $399.00 a year
http://www.certoutlet.com (http://www.certoutlet.com/)

Besides them, Verisign, and about two others....that's all that's out there.

[tpoynton]

I used Comodo (http://www.instantssl.com/code-signing/), but have since stopped. I have read that 2007 has 'trusted locations' that the workbook can be saved in, but I have not used it (them).

[JrDeveloper]

I'm a noobie here (this is my first post), but I have had experience with the Trusted Folders option in Office 2007, and it works as suggested. Any files opened from locations specified in the Trust Center>Trusted Locations don't even ask about enabling macros, they are just enabled. I use these frequently for my own files.

If your clients are willing to save the files you give them in a single folder, and add that folder as a Trusted Location, security should no longer be an issue.

Hope that helps!

[DanOfEarth]

I forgot about Comodo.

Regarding the trusted locations, the "2007 trusted location" even has a wicked video WAV file you can send with the workbook (I ripped it from the microsoft site), explaining how to use the trusted location feature.

In my case however I'm sending these workbooks to potential and current clients, so even asking them to create a trusted file source is a bit much. They get spooked :SHOCKED:on stuff they don't understand. And some system admins won't let private certs through the security filter :nono because they don't know "my intentions", since I'm not an employee of their company.

(LOL...I love that list of smileys)