Organizations that are concerned about the spread of macro viruses such as the Melissa virus can use macro signing technology to enable the internal sharing of macros without the risks associated with macro viruses. Office 2000 allows a user to trust all signed macro's, or to trust specific developers. Thawte does not audit or assess every macro signed with a Thawte Developer Certificate. Receiving a signed macro does not necessarily mean that the macro will do no harm. However, the digital signature on the macro does include the name of the developer to whom the digital certificate was issued, which will ensure that signed code is auditable and traceable to specific developers and cryptographic keys.
Developers are responsible for their own cryptographic keys.
Print out that page and use it as a guide to the process. As always, please make sure that you check this against the latest documentation from Microsoft. The Office 2000 macro signing tools expect to find your Developer certificate and keys in the registry of your computer. When enrolling for your Developer Certificate, make sure that you choose to store your key in the registry instead of storing it in a PVK file. Customers who have already purchased certificates and have their keys in a PVK file can use a utility from Microsoft to import the key into their system registry.