Security and VBA Macros

[Michael Tissington]

We have purchase a vba certificate and signed the dot that contains a bunch
of macros.

However when the dot is placed on the users machine they get an error that
it is not from a trusted source.

What was the point of us getting a certificate if this pops up on the users
machine.

Is there anything that we can do to make this process clean for the user?

Thanks

 

[Steve Lang]

Hi Michael,

The first time a certificate is seen on a user's machine it will generate a
security warning. If the certificate is not a Self-Cert (by your stating you
purchased it, I'm guessing it is not), your users should get the opportunity
to "Always Trust" that source. Have your users click that check box in the
security warning box and all should be good.

HTH and have a great spook day!

Steve

 

[Lars-Eric Gisslén]

Michael,

From where did you buy the certificate? Seems like the root certificate from
the CA is missing on the computer. We have never had any problems with
Verisign certificates. I think you can not install Windows without getting
at least Verisign's root certificates on the computer. If you have bought
the VBA certificate from Verisign and the root certificate is not on the
problem computer the user (or someone else) must have been playing around
with the registry or the storage without knowing what he/she did.

Regards,
Lars-Eric

 

[Michael Tissington]

Steve,

If the security settings are set to High, then they do not get an option to
trust the certificate.

 

[Joe Fawcett]

We have purchase a vba certificate and signed the dot that contains a bunch
of macros.

However when the dot is placed on the users machine they get an error that
it is not from a trusted source.

What was the point of us getting a certificate if this pops up on the users
machine.

Is there anything that we can do to make this process clean for the user?

Thanks

Remember a certificate just says that someone (Thawte/VeriSign or whoever)
asserts you are who you are and that you signed the code. It is upto the
user to decide if they trust you or not. As long as security is not set to
high and your certificate is a code-signing one, you can still sign VBA
projects with non code signing ones, your user should just have to choose
once. On an intranet if you have permission you can often use logon scripts
or such to pre-trust your signed code.