Re: ClickOnce and Certificate
- From: Dominick Baier [DevelopMentor] <dbaier@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 25 Jan 2006 06:32:17 +0000 (UTC)
Hi,
well - you should care!
As developers it is our responsibility to keep the number of times a user is presented with these security dialogs as low as possible.
You want that a client is running your code - then establish some kind of trust relationship. Thats for the philosophical part.
Technically - execution of ClickOnce app without manifests signed by a trusted publisher can be administratively disabled - which would render your app inoperational. Thats a company policy thing - like disabling cookies or javascript - and btw - my recommendation to every IT guy i talk to.
To get a cert for ClickOnce you have 3 options basically
1: makecert: only for testing purposes 2: Windows CA (comes with Windows Server) 3: a commercial one
1 is OK for test purposes. 2 is fine for internal apps and extranet scenarios (or you have to go through the process that your clients must trust your internal CA)
3 is the easiest if your software will get used by clients which don't have a trust relationship to your CA - external clients.
So you need a code signing cert every 12 months - which isn't too bad and btw - ClickOnce supports time stamping servers - which means your signed manifests don't expire when you cert expires and you *don't* have to re-sign your apps every 12 months.. You just have to use the new cert for new signatures.
--------------------------------------- Dominick Baier - DevelopMentor http://www.leastprivilege.com
I am looking into deploying a ClickOnce application and am reading all these things about how you need a certificate to make ClickOnce work.
After looking around, I found that I can use a utility called MakeCert.exe to make my own certificate but then the documentation says that the certification created with this utility is for testing purpose and should not be used for commercial purpose because I think it won't work.
So what am I supposed to do? Is my only option to go and pay for the certificate? What if I don't care that my user see the *danger don't install software from unknown publishers or you will die* message when they install our software? What are my options?
Thanks
.
- Follow-Ups:
- Re: ClickOnce and Certificate
- From: Rene
- Re: ClickOnce and Certificate
- References:
- ClickOnce and Certificate
- From: Rene
- ClickOnce and Certificate
- Prev by Date: Security Exception thrown
- Next by Date: Re: Security Exception thrown
- Previous by thread: ClickOnce and Certificate
- Next by thread: Re: ClickOnce and Certificate
- Index(es):
Relevant Pages
|