> "Superfreak3" <Matt.Wal...[ at ]synergis.com> wrote in message
>
> news:1182368147.204904.233260[ at ]e9g2000prf.googlegroups.com...
>
>
>
>
>
> > We are planning on or looking into adding a Digital Signature to
> > our .msi, but not quite sure where to turn or where to start. We use
> > Wise for Windows Installer which provides a Digital Signatures view in
> > which Web URL, Descriptive Name, and Time Stamp URL can be entered.
> > There are also browses to the Credentials File (.spc) and the Private
> > Key File (.pvk).
>
> > Wise mentions VeriSign in its documentation. I was wondering if you
> > have to purchase a digital signature from an organization like
> > VeriSign or is there a way to create your own digital signature?
>
> > We are embarking on this journey due to VISTA and the 'friendlier'
> > dialog that is displayed if the installation package is digitally
> > signed. If a digital signature is added to a package destined for a
> > pre-Vista OS, will the behavior of the installation in any way
> > change? Will there be any dialogs that appear to allow the
> > installation due to the addition of a digital signature? The reason I
> > ask this question is because currently, our application will look to
> > update itself by looking for a new .msi. If found, the installation
> > runs silently. If adding a digital signature would alter this
> > behavior (pre-Vista OS), I may have to rethink the digital signature
> > concept at this time because I wouldn't want to have to maintain a
> > separate install for Vista, which would then include the signature.
>
> > I'm confused and looking for guidance and realize this may not be the
> > best group for these questions, but any help/guidance is greatly
> > appreciated!
>
> > Thanks in advance for any information!!!
>
> Generic code signing info:
http://msdn2.microsoft.com/en-us/library/ms537361.aspxhttp://msdn2.microsoft.com/en-us/library/aa140234(office.10).aspx>
> The second link about shows you how to create a test certificate which is
> useful for local testing only. You shouldn't consider releasing such a
> package to a customer. I suggest working with test certificates to
> understand how it really affects things in your environment.
>
> You don't have to go with VeriSign to get a digital code signing
> certificate. That is unless you want to establish a winqual account in
> order to participate in a windows logo programs/driver signing. Even then
> your code/driver can be signed with another certificate - you just need a
> Verisign certificate to sign agreements/packages that will be uploaded to
> the winqual site itself.
>
> Signing will not negatively affect your MSI file use downlevel from Vista.
> However it won't suddenly allow you to by-pass UAC prompts. Your
> application will have to be elevated in order to silently run the
> installation without prompts -- either that or have a service perform the
> installation for you.
>
> Also note that you can sign your MSI file independently from the tool you
> use to create the MSI package - most MSI creation tools just make it easier
> to do it automatically (as you can see by the various signing fields in the
> Wise application). The basic tools (makecert/signtool) are included in the
> Windows SDK. You can also search the net for step by step instructions on
> how to use each tool.
>
> Sincerely,
> Adrian Accinelli- Hide quoted text -
>
> - Show quoted text -