| Groups | Blog | Home |
dotnet compact framework : Hi, Any work around for windows mobile 6 dynamic loading warning message ?
Is there any way to avoid the below message while dynamicaly loading the a dll into windows mobile 6, without signing the dll ? "Starting this program requires a component from an unknown publisher. You should start the program only if you trust the component's publisher. Do you want to continue?" -Manas
Yes by signing your code using a digital signature provided from Verisign or
Thawte. You can sign your code using signtool.exe(.NET 2.0 and later) or signcode.exe (pre .NET 2.0). You can also create your own digital signature using makecert.exe. -- Simon Hart Visual Developer - Device Application Development MVP http://simonrhart.blogspot.com [quoted text, click to view] "Manas" wrote:
> > Is there any way to avoid the below message while dynamicaly loading > the a dll into windows mobile 6, without signing the dll ? > > "Starting this program requires a component from an unknown > publisher. > You should start the program only if you trust the component's > publisher. Do you want to continue?" > > -Manas > >
Hi,
[quoted text, click to view] "Manas" <manasglobal1@gmail.com> wrote in message news:55fdabf0-d387-4264-afa1-5d71f49603ea@y43g2000hsy.googlegroups.com... > Is there any way to avoid the below message while dynamicaly loading > the a dll into windows mobile 6, without signing the dll ? > > "Starting this program requires a component from an unknown > publisher. > You should start the program only if you trust the component's > publisher. Do you want to continue?" In general you can not avoid this prompt without signing your DLL, unless your deployment scenario and device selection enables you to change to a less restrictive device security model. Depending upon the device (and vendor) in question you may not be able to easily change the security model utilised by your device and it may not be something end users would be happy to do to their device at any rate. If you want to get rid of this prompt on a device that employs the "one or two tier with prompt" security model without needing modifications to the PDAs, your only option is to purchase a code signing certificate from the likes of Verisign. The Window Mobile 6 SDK contains sample certificates you may be able to use during development. Hope this helps, Christopher Fairbairn
Hi Simon ,
Many thanks for the answer! I tried to use signcode.exe , I am not able to see any certficates under 'select from store' option in Digital signature wizard to choose . How to get the reuired certificate under 'select from store option'. Which is the right certficate to choose and where can i locate them...i need to sign a test dll and i dont want the message to pop-up as i described in my first mail. What is the select from file otion? can i choose the certificate file as well? I have asked too many questions...wish i dint bug u up:-) [quoted text, click to view] "Simon Hart [MVP]" wrote:
> Yes by signing your code using a digital signature provided from Verisign or > Thawte. You can sign your code using signtool.exe(.NET 2.0 and later) or > signcode.exe (pre .NET 2.0). You can also create your own digital signature > using makecert.exe. > -- > Simon Hart > Visual Developer - Device Application Development MVP > http://simonrhart.blogspot.com > > > "Manas" wrote: > > > > > Is there any way to avoid the below message while dynamicaly loading > > the a dll into windows mobile 6, without signing the dll ? > > > > "Starting this program requires a component from an unknown > > publisher. > > You should start the program only if you trust the component's > > publisher. Do you want to continue?" > > > > -Manas > > > >
You need to add your cert to the certificate store on your dev machine for
nice integration with Visual Studio. Execute on the command-line: start c:\windows\system32\certmgr.msc then import your cert using the wizard. -- Simon Hart Visual Developer - Device Application Development MVP http://simonrhart.blogspot.com [quoted text, click to view] "WinMobileNewMan" wrote:
> Hi Simon , > > Many thanks for the answer! > > I tried to use signcode.exe , I am not able to see any certficates under > 'select from store' option in Digital signature wizard to choose . > > How to get the reuired certificate under 'select from store option'. > > Which is the right certficate to choose and where can i locate them...i need > to sign a test dll and i dont want the message to pop-up as i described in my > first mail. > > What is the select from file otion? can i choose the certificate file as well? > > I have asked too many questions...wish i dint bug u up:-) > > > "Simon Hart [MVP]" wrote: > > > Yes by signing your code using a digital signature provided from Verisign or > > Thawte. You can sign your code using signtool.exe(.NET 2.0 and later) or > > signcode.exe (pre .NET 2.0). You can also create your own digital signature > > using makecert.exe. > > -- > > Simon Hart > > Visual Developer - Device Application Development MVP > > http://simonrhart.blogspot.com > > > > > > "Manas" wrote: > > > > > > > > Is there any way to avoid the below message while dynamicaly loading > > > the a dll into windows mobile 6, without signing the dll ? > > > > > > "Starting this program requires a component from an unknown > > > publisher. > > > You should start the program only if you trust the component's > > > publisher. Do you want to continue?" > > > > > > -Manas > > > > > >
Hi Simon ,
Thanks again! Simon, afterfollowing the command suggested below i could only imported the certificates to certain store(i dont know where it went physically in system:-( )... still i dont see the certificate after clicking on 'select from store' using signcode wizard ' and how to get the corresponding private key(is the key a file or number ?) and where can i locate the key? could you please tell me the detailed step to do it? it would really help! [quoted text, click to view] "Simon Hart [MVP]" wrote:
> You need to add your cert to the certificate store on your dev machine for > nice integration with Visual Studio. > > Execute on the command-line: start c:\windows\system32\certmgr.msc then > import your cert using the wizard. > > -- > Simon Hart > Visual Developer - Device Application Development MVP > http://simonrhart.blogspot.com > > > "WinMobileNewMan" wrote: > > > Hi Simon , > > > > Many thanks for the answer! > > > > I tried to use signcode.exe , I am not able to see any certficates under > > 'select from store' option in Digital signature wizard to choose . > > > > How to get the reuired certificate under 'select from store option'. > > > > Which is the right certficate to choose and where can i locate them...i need > > to sign a test dll and i dont want the message to pop-up as i described in my > > first mail. > > > > What is the select from file otion? can i choose the certificate file as well? > > > > I have asked too many questions...wish i dint bug u up:-) > > > > > > "Simon Hart [MVP]" wrote: > > > > > Yes by signing your code using a digital signature provided from Verisign or > > > Thawte. You can sign your code using signtool.exe(.NET 2.0 and later) or > > > signcode.exe (pre .NET 2.0). You can also create your own digital signature > > > using makecert.exe. > > > -- > > > Simon Hart > > > Visual Developer - Device Application Development MVP > > > http://simonrhart.blogspot.com > > > > > > > > > "Manas" wrote: > > > > > > > > > > > Is there any way to avoid the below message while dynamicaly loading > > > > the a dll into windows mobile 6, without signing the dll ? > > > > > > > > "Starting this program requires a component from an unknown > > > > publisher. > > > > You should start the program only if you trust the component's > > > > publisher. Do you want to continue?" > > > > > > > > -Manas > > > > > > > >
Hi ,
Thanks for your reply! Based on your instruction i created a self signing certificate and used that to sign the dll. Then included the dll during runtime. The message still appears (for the first time only after each recompilation) . is the any other places where i got to include the dll or any other clue? -Manas [quoted text, click to view] "Christopher Fairbairn" wrote:
> Hi, > > "Manas" <manasglobal1@gmail.com> wrote in message > news:55fdabf0-d387-4264-afa1-5d71f49603ea@y43g2000hsy.googlegroups.com... > > Is there any way to avoid the below message while dynamicaly loading > > the a dll into windows mobile 6, without signing the dll ? > > > > "Starting this program requires a component from an unknown > > publisher. > > You should start the program only if you trust the component's > > publisher. Do you want to continue?" > > In general you can not avoid this prompt without signing your DLL, unless > your deployment scenario and device selection enables you to change to a > less restrictive device security model. > > Depending upon the device (and vendor) in question you may not be able to > easily change the security model utilised by your device and it may not be > something end users would be happy to do to their device at any rate. > > If you want to get rid of this prompt on a device that employs the "one or > two tier with prompt" security model without needing modifications to the > PDAs, your only option is to purchase a code signing certificate from the > likes of Verisign. > > The Window Mobile 6 SDK contains sample certificates you may be able to use > during development. > > Hope this helps, > Christopher Fairbairn > >
Have you installed the cert onto the device? you can easily do this by
creating an xml file in the format expected by the certificateStore configuration service provider and wrap this up into a cab file - ensure the xml file is named _setup.xml (ensure you include the underscrore as the install won't work otherwise). -- Simon Hart Visual Developer - Device Application Development MVP http://simonrhart.blogspot.com [quoted text, click to view] "WinMobileNewMan" wrote:
> Hi , > > Thanks for your reply! > > Based on your instruction i created a self signing certificate and used that > to sign the dll. Then included the dll during runtime. The message still > appears (for the first time only after each recompilation) . > > is the any other places where i got to include the dll or any other clue? > > -Manas > > "Christopher Fairbairn" wrote: > > > Hi, > > > > "Manas" <manasglobal1@gmail.com> wrote in message > > news:55fdabf0-d387-4264-afa1-5d71f49603ea@y43g2000hsy.googlegroups.com... > > > Is there any way to avoid the below message while dynamicaly loading > > > the a dll into windows mobile 6, without signing the dll ? > > > > > > "Starting this program requires a component from an unknown > > > publisher. > > > You should start the program only if you trust the component's > > > publisher. Do you want to continue?" > > > > In general you can not avoid this prompt without signing your DLL, unless > > your deployment scenario and device selection enables you to change to a > > less restrictive device security model. > > > > Depending upon the device (and vendor) in question you may not be able to > > easily change the security model utilised by your device and it may not be > > something end users would be happy to do to their device at any rate. > > > > If you want to get rid of this prompt on a device that employs the "one or > > two tier with prompt" security model without needing modifications to the > > PDAs, your only option is to purchase a code signing certificate from the > > likes of Verisign. > > > > The Window Mobile 6 SDK contains sample certificates you may be able to use > > during development. > > > > Hope this helps, > > Christopher Fairbairn > > > >
Hi,
"WinMobileNewMan" <WinMobileNewMan@discussions.microsoft.com> wrote in message news:0D7380B9-43F4-4DF0-8BDA-088938F61FC8@microsoft.com... [quoted text, click to view] > Based on your instruction i created a self signing certificate and used > that > to sign the dll. Then included the dll during runtime. The message still > appears (for the first time only after each recompilation) . As a first step have you tried using the sample certificates included within the Windows Mobile SDKs? Using these will help eliminate the process you have used to create your certificate as the potential source of your problem. Since Windows Mobile devices will not ship with the required client side certificates to trust your self signed certificates (or the Microsoft sample ones) you need to install a certificate into the certificate store of your Windows Mobile device in order for the PDA to accept executables signed with the matching certificate. For example with the Windows Mobile 5.0 Pocket PC SDK you probably have a cab file called sdkcerts.cab located within the C:\Program Files\Windows CE Tools\wce500\Windows Mobile 5.0 Pocket PC SDK\Tools folder. Installing this CAB file onto a PDA will install the required device side certificates in order for the OS to accept executables signed with the various certifcates located within the same folder. See for example the step by step guide available in the "Windows Mobile 5.0 Application Security" article on MSDN underneath the "Signing an Application During Day-to-Day Development" section - http://msdn2.microsoft.com/en-us/library/ms839681.aspx One common mistake made when initially signing executables is forgetting to sign one of the application components. You need to sign your main executable, any *.dll files it loads and the *.cab file itself (if you are deploying your applications in that manor). Hope this helps, Christopher Fairbairn
Hi ,
Thanks! How to to obtain the password for the .pfx (if i use the sample certificate available with sdk) . I am using WM6.0 anyway . [quoted text, click to view] "Christopher Fairbairn" wrote:
> Hi, > > "WinMobileNewMan" <WinMobileNewMan@discussions.microsoft.com> wrote in > message news:0D7380B9-43F4-4DF0-8BDA-088938F61FC8@microsoft.com... > > Based on your instruction i created a self signing certificate and used > > that > > to sign the dll. Then included the dll during runtime. The message still > > appears (for the first time only after each recompilation) . > > As a first step have you tried using the sample certificates included within > the Windows Mobile SDKs? Using these will help eliminate the process you > have used to create your certificate as the potential source of your > problem. > > Since Windows Mobile devices will not ship with the required client side > certificates to trust your self signed certificates (or the Microsoft sample > ones) you need to install a certificate into the certificate store of your > Windows Mobile device in order for the PDA to accept executables signed with > the matching certificate. > > For example with the Windows Mobile 5.0 Pocket PC SDK you probably have a > cab file called sdkcerts.cab located within the C:\Program Files\Windows CE > Tools\wce500\Windows Mobile 5.0 Pocket PC SDK\Tools folder. Installing this > CAB file onto a PDA will install the required device side certificates in > order for the OS to accept executables signed with the various certifcates > located within the same folder. > > See for example the step by step guide available in the "Windows Mobile 5.0 > Application Security" article on MSDN underneath the "Signing an Application > During Day-to-Day Development" section - > http://msdn2.microsoft.com/en-us/library/ms839681.aspx > > One common mistake made when initially signing executables is forgetting to > sign one of the application components. You need to sign your main > executable, any *.dll files it loads and the *.cab file itself (if you are > deploying your applications in that manor). > > Hope this helps, > Christopher Fairbairn >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |