Can anyone reccomend an affordable way to sign my macros?

Self-cert is no good for me as the tick-box to "always trust content
from..." is only available on the machine it was created on.

But I can only find certificates that cost hundreds of dollars a year.

I'm happy to pay for a certificate, but they seem VERY expensive for what
I'm going to use them for. AND they only last for a year.

Have I missed something? Is there a longer lasting one, or a cheaper
alternative? Or can I do something to enable the "Always trust content
from..." tick box so that I could use the self-cert option?

All input vey gratefully received

Thanks

M

Can't you just copy your certificate to the other machines as well?

Press <Alt><F11> to go to VBA. Click on Tools, digital Signatures, view
your signature, select copy to file, and then follow the prompts to export it
to a file. Mail this to the other user.
To import, left click on the attachemnt, select open. Now click on the set
contact trust button. When the Import Contact Settings box appears, check
the first two option boxes and click OK, and OK out.

Now open the signed project, select the imported signature, and sign. You
can now make changes on the user's PC
--
HTH

Kassie

Replace xxx with hotmail


"Michelle" wrote:

> Can anyone reccomend an affordable way to sign my macros?
>
> Self-cert is no good for me as the tick-box to "always trust content
> from..." is only available on the machine it was created on.
>
> But I can only find certificates that cost hundreds of dollars a year.
>
> I'm happy to pay for a certificate, but they seem VERY expensive for what
> I'm going to use them for. AND they only last for a year.
>
> Have I missed something? Is there a longer lasting one, or a cheaper
> alternative? Or can I do something to enable the "Always trust content
> from..." tick box so that I could use the self-cert option?
>
> All input vey gratefully received
>
> Thanks
>
> M
>

Besides what you said, usually you are required to be a 'business' and
registered as such to obtain anything other than self-cert. About the least
expensive I've seen is through GoDaddy.com ($199.99/yr or $179.99/yr if you
purchase 2 yrs at once). And they have the must-be-a-business rule in effect.

Look at what Kassie suggested, probably the easiest way to go if you have a
established group that you want to provide a certificate to so that using
your applications is easier for them. But if it comes down to that, it's
usually a matter of trust, and my clients seem to trust my work, signed or
not. I mean they've got to have trust in you to install your self-cert on
their systems anyhow, don't they?

"Michelle" wrote:

> Can anyone reccomend an affordable way to sign my macros?
>
> Self-cert is no good for me as the tick-box to "always trust content
> from..." is only available on the machine it was created on.
>
> But I can only find certificates that cost hundreds of dollars a year.
>
> I'm happy to pay for a certificate, but they seem VERY expensive for what
> I'm going to use them for. AND they only last for a year.
>
> Have I missed something? Is there a longer lasting one, or a cheaper
> alternative? Or can I do something to enable the "Always trust content
> from..." tick box so that I could use the self-cert option?
>
> All input vey gratefully received
>
> Thanks
>
> M
>

Very true, but it is nice to run on High security, and so keep out other
junk. I find that doing it this way saves a lot of hassel, and of course it
is for free!

--
HTH

Kassie

Replace xxx with hotmail


"JLatham" wrote:

> Besides what you said, usually you are required to be a 'business' and
> registered as such to obtain anything other than self-cert. About the least
> expensive I've seen is through GoDaddy.com ($199.99/yr or $179.99/yr if you
> purchase 2 yrs at once). And they have the must-be-a-business rule in effect.
>
> Look at what Kassie suggested, probably the easiest way to go if you have a
> established group that you want to provide a certificate to so that using
> your applications is easier for them. But if it comes down to that, it's
> usually a matter of trust, and my clients seem to trust my work, signed or
> not. I mean they've got to have trust in you to install your self-cert on
> their systems anyhow, don't they?
>
> "Michelle" wrote:
>
> > Can anyone reccomend an affordable way to sign my macros?
> >
> > Self-cert is no good for me as the tick-box to "always trust content
> > from..." is only available on the machine it was created on.
> >
> > But I can only find certificates that cost hundreds of dollars a year.
> >
> > I'm happy to pay for a certificate, but they seem VERY expensive for what
> > I'm going to use them for. AND they only last for a year.
> >
> > Have I missed something? Is there a longer lasting one, or a cheaper
> > alternative? Or can I do something to enable the "Always trust content
> > from..." tick box so that I could use the self-cert option?
> >
> > All input vey gratefully received
> >
> > Thanks
> >
> > M
> >

Kassie

Are you saying that you can export a selfcert DS to another computer?

Easy enough to create a *.cer file but how do you export the key?


Gord Dibben MS Excel MVP

On Sun, 13 Sep 2009 02:52:01 -0700, Kassie <(E-Mail Removed)> wrote:

>Very true, but it is nice to run on High security, and so keep out other
>junk. I find that doing it this way saves a lot of hassel, and of course it
>is for free!

Hi Gord,

From a previous post of mine. . .
Press <Alt><F11> to go to VBA. Click on Tools, digital Signatures, view
your signature, select Copy to file, and then follow the prompts to export it
to a file. Mail this to the other user.
To import, left click on the attachemnt, select open. Now click on the set
contact trust button. When the Import Contact Settings box appears, check
the first two option boxes and click OK, and OK out.

Now open the signed project, select the imported signature, and sign. You
can now make changes on the user's PC

--
HTH

Kassie

Replace xxx with hotmail


"Gord Dibben" wrote:

> Kassie
>
> Are you saying that you can export a selfcert DS to another computer?
>
> Easy enough to create a *.cer file but how do you export the key?
>
>
> Gord Dibben MS Excel MVP
>
> On Sun, 13 Sep 2009 02:52:01 -0700, Kassie <(E-Mail Removed)> wrote:
>
> >Very true, but it is nice to run on High security, and so keep out other
> >junk. I find that doing it this way saves a lot of hassel, and of course it
> >is for free!
>
>

No problem copying to file *.cer

But how do you export the Private Key or do you need it?

I have tried this previously but was never able to make it work.

I have tried installing into Trusted Root Certificates and Trusted
Publishers but when I tried to use the DS I received the message about not
having a key.

If not too much trouble could you email me a copy of a selfcert DS so I may
install on my computer?

gorddibbATshawDOTca


Thanks, Gord

On Sun, 13 Sep 2009 21:44:02 -0700, Kassie <(E-Mail Removed)> wrote:

>Hi Gord,
>
>From a previous post of mine. . .
>Press <Alt><F11> to go to VBA. Click on Tools, digital Signatures, view
>your signature, select Copy to file, and then follow the prompts to export it
>to a file. Mail this to the other user.
>To import, left click on the attachemnt, select open. Now click on the set
>contact trust button. When the Import Contact Settings box appears, check
>the first two option boxes and click OK, and OK out.
>
>Now open the signed project, select the imported signature, and sign. You
>can now make changes on the user's PC

While I have never used this info, have a look at the following site:
http://www.source-code.biz/snippets/vbasic/3.htm

Christian d'Heureuse suggests the use of makecert.exe, cert2spc.exe and
pvkimprt.exe to achieve this objective. These commands form part of the .NET
Framework and Platform SDK.

--
HTH

Kassie

Replace xxx with hotmail


"Gord Dibben" wrote:

> No problem copying to file *.cer
>
> But how do you export the Private Key or do you need it?
>
> I have tried this previously but was never able to make it work.
>
> I have tried installing into Trusted Root Certificates and Trusted
> Publishers but when I tried to use the DS I received the message about not
> having a key.
>
> If not too much trouble could you email me a copy of a selfcert DS so I may
> install on my computer?
>
> gorddibbATshawDOTca
>
>
> Thanks, Gord
>
> On Sun, 13 Sep 2009 21:44:02 -0700, Kassie <(E-Mail Removed)> wrote:
>
> >Hi Gord,
> >
> >From a previous post of mine. . .
> >Press <Alt><F11> to go to VBA. Click on Tools, digital Signatures, view
> >your signature, select Copy to file, and then follow the prompts to export it
> >to a file. Mail this to the other user.
> >To import, left click on the attachemnt, select open. Now click on the set
> >contact trust button. When the Import Contact Settings box appears, check
> >the first two option boxes and click OK, and OK out.
> >
> >Now open the signed project, select the imported signature, and sign. You
> >can now make changes on the user's PC
>
>

Thanks for the pointer to that site.

I will look into this Kassie.

From your earlier reply to OP I thought your sending of the DS to another
computer was referring to a selfcert DS.

I guess you meant a commercial DS


Gord


On Wed, 16 Sep 2009 00:12:01 -0700, Kassie <(E-Mail Removed)> wrote:

>While I have never used this info, have a look at the following site:
> http://www.source-code.biz/snippets/vbasic/3.htm
>
>Christian d'Heureuse suggests the use of makecert.exe, cert2spc.exe and
>pvkimprt.exe to achieve this objective. These commands form part of the .NET
>Framework and Platform SDK.

No, it was a selfcert DS, but have never worked on a server environment. As
I understand it, that is where you need the key. All I know is that I export
ym Selfcert, import it on the other PC, and it works.

--
HTH

Kassie

Replace xxx with hotmail


"Gord Dibben" wrote:

> Thanks for the pointer to that site.
>
> I will look into this Kassie.
>
> From your earlier reply to OP I thought your sending of the DS to another
> computer was referring to a selfcert DS.
>
> I guess you meant a commercial DS
>
>
> Gord
>
>
> On Wed, 16 Sep 2009 00:12:01 -0700, Kassie <(E-Mail Removed)> wrote:
>
> >While I have never used this info, have a look at the following site:
> > http://www.source-code.biz/snippets/vbasic/3.htm
> >
> >Christian d'Heureuse suggests the use of makecert.exe, cert2spc.exe and
> >pvkimprt.exe to achieve this objective. These commands form part of the .NET
> >Framework and Platform SDK.
>
>