Re: How do we make our macros "signed"?

From: Jay Freedman (jay.freedman_at_verizon.net)
Date: 02/03/05 

Date: Thu, 3 Feb 2005 10:12:40 -0500

Yes, you can sign your macro code, and each user will be asked once whether
to trust your macros.

To do this, you first need a code signing certificate. For internal use only
(on your PC and possibly on those in your organization where you're known
and trusted), you can create a certificate by running the SelfCert.exe
application in the Office program folder. This won't do for code you're
emailing out of your office; for that you need a certificate issued by one
of the public certificate authorities, such as Verisign or Thawte. Verisign
wants $400, but I couldn't find a statement on their site of how long the
certificate lasts (they all expire). Thawte charges $200 for one year or
$400 for two years.

Once you have a certificate, you install it on your development machine.
Then in the VBA editor you can use the Tools > Digital Signatures dialog to
sign the current project. 

-- 
Regards,
Jay Freedman
Microsoft Word MVP          FAQ: http://word.mvps.org
StargateFan wrote:
> I ran across a new default, the security level at this new contract is
> set for high.  Everywhere I've been up till now, it's been medium, so
> I'd never run into problem of macros not working until re-setting the
> security level.
>
> Since this is the case, and since I'm creating Word documents and
> spreadsheets with macros to share with other colleagues, thought it
> might be prodent to look into that "signed" business or whatever it's
> called.  I'm assuming that if I configure, or whatever, all these
> macros in that way, that that will also perhaps stop the macro
> confirmation box that keeps coming up whenever one opens up a document
> with macros??  That would be ideal.  These are necessary and safe
> macros that I write strictly for the purposes of making people's lives
> easier.
>
> Any point in the right direction will be greatly appreciated.  Thanks!