J
John Blight
We have a template associated with a single stencil, both of which are
digitally signed using a Thawte multi-purpose certificate. When a document is
created from the template, and we are prompted with the 'Security Warning'
(or equivalent) dialog, we can view the certificate details successfully,
with the certificate path being recognised properly. If we choose to 'Always
trust macros from this publisher', we aren't prompted on subsequent
occasions. So far, so good.
However, if we try to view the certificate through Internet Explorer or
through the trusted publishers listing in Visio, we get a message reporting
'Windows does not have enough information to verify this certificate'. The
certification path isn't recognised (it ought to be 'Thawte Premium Server
CA' > 'Thawte Code Signing CA' > [Our Certificate]).
Trying to view the certificate through the VBA editor window gives different
results depending on the version of Visio - Visio 2003 behaves as we would
wish, but Visio 2002 and 2007 do not, failing to give the certification path.
However, opening files on subsequent occasions does not prompt for a
response, so the VBA code must be verified.
Installing the 'Thawte Code Signing CA' intermediate certificate results in
the certification path being recognised fully, but this would be a clumsy
implementation of digital signatures.
Any thoughts/explanations would be appreciated.
digitally signed using a Thawte multi-purpose certificate. When a document is
created from the template, and we are prompted with the 'Security Warning'
(or equivalent) dialog, we can view the certificate details successfully,
with the certificate path being recognised properly. If we choose to 'Always
trust macros from this publisher', we aren't prompted on subsequent
occasions. So far, so good.
However, if we try to view the certificate through Internet Explorer or
through the trusted publishers listing in Visio, we get a message reporting
'Windows does not have enough information to verify this certificate'. The
certification path isn't recognised (it ought to be 'Thawte Premium Server
CA' > 'Thawte Code Signing CA' > [Our Certificate]).
Trying to view the certificate through the VBA editor window gives different
results depending on the version of Visio - Visio 2003 behaves as we would
wish, but Visio 2002 and 2007 do not, failing to give the certification path.
However, opening files on subsequent occasions does not prompt for a
response, so the VBA code must be verified.
Installing the 'Thawte Code Signing CA' intermediate certificate results in
the certification path being recognised fully, but this would be a clumsy
implementation of digital signatures.
Any thoughts/explanations would be appreciated.