You should be able to avoid the popup by cross signing with MSFT cert provided by Verisign. If your issue is some unknown black magic, this might help.
~Kenny
From: Ami Awbadhhomailto:xxxxx
Sent: ?Saturday?, ?January? ?25?, ?2014 ?1?:?15? ?AM
To: Windows System Software Devs Interest Listmailto:xxxxx
i dont know why there is so much confusion created by my email my apologies to you all.
In my original post I had written :
1. the rc file is proper, even though i couldnt show you the exact strings, since my employer wouldn’t like it, at least we verified that all the relevant place holders were in place.
2. i also said in the original email that displaying the properties of the sys file by right clicking on it and going to the properties->details tab displays all the information correctly.
3. I also said, that i re-verified (after max’s qn) that a previous version of this already released driver which is whql signed displays the information correctly. since we are still making changes in this release, we haven’t got it whqled yet. so we temporarily sign with verisign class 3 so that testers and beta customers can load it on 64 bit Os. It is this version of the verisign signed driver where we see the problem.
4. This is not the only driver we ship. we have other drivers, volume filters, file system filters etc. All of which are signed in the same way with the same verisign class 3 cert. however, those drivers show version info correctly.
5. this makes me think that this case is unique for root bus extenders. i think ms has something else going on for such drivers. And filters to FS, or storage are exempt fr0m that extra bit of ‘whatever’.
6. In a separate non related incident, we saw that this same driver while installation, also throws a popup asking whether we want to trust this third party signer. Again, the other drivers like vol filter etc don’t throw the message. we opened a case with MSFT regarding this, and they confirmed that for bus drivers, this is by design, filters only extend the bus, hence the warning is not given for them.
7. Point 6 above is my hypothesis, that maybe even verifier behaves differently for a bus extender.
Any thoughts would help.
On Sat, Jan 25, 2014 at 8:23 AM, > wrote:
> There is a file with the extension .RC that has the data that Driver
> Verifier and the properties in the shell uses. This file is compiled with
> the “resource compiler” and then linked into your driver. The data in
> that
> file is totally separate from the signing data.
For non-drivers, it can hold a lot more stuff, such as dialog templates,
string resources, icons, and other GUI-related objects; sound resources
and image resources. But even for drivers, if you are doing your own
error codes, you can use the message compiler, mc, which creates the text
of the message as a MESSAGETABLE resource, and you can tell the Event
Viewer where your .sys file is, and it can decode your private message
codes. Similarly, you can have an application go after the .sys file (or
a separate .dll file) to get the (localized) text for your private error
messages. But one of the things that is not in it (and never has been) is
the signing data.
joe
>
>
> Don Burn
> Windows Filesystem and Driver Consulting
> Website: http://www.windrvr.com
> Blog: http://msmvps.com/blogs/WinDrvr
>
>
>
>
> -----Original Message-----
> From: xxxxx@lists.osr.commailto:xxxxx
> [mailto:xxxxx@lists.osr.commailto:xxxxx] On Behalf Of Ami Awbadhho
> Sent: Friday, January 24, 2014 1:48 PM
> To: Windows System Software Devs Interest List
> Subject: Re: [ntdev] Verifier GUI and Provider Names
>
> sorry don, I couldnt understand your comment
>
>
> On Sat, Jan 25, 2014 at 12:09 AM, Don Burn > wrote:
>
>
> Because the RC file data has nothing to do with the signing data.
> Take a
> look at any driver project in the WDK and look at the resource data.
>
>
> Don Burn
> Windows Filesystem and Driver Consulting
> Website: http://www.windrvr.com
> Blog: http://msmvps.com/blogs/WinDrvr
>
>
>
>
> -----Original Message-----
> From: xxxxx@lists.osr.commailto:xxxxx
> [mailto:xxxxx@lists.osr.commailto:xxxxx] On Behalf Of Ami
> Awbadhho
> Sent: Friday, January 24, 2014 1:37 PM
> To: Windows System Software Devs Interest List
> Subject: Re: [ntdev] Verifier GUI and Provider Names
>
> hmmph…Max, you are spot on! the driver in question is not whql
> signed,
> but it is verisign signed. i also checked on another machine, where
> we have
> a whql signed version of the same binary, and all the information is
> corectly visible there.
>
> i do not understand this ofcourse, verisign class 3 cert should be
> at the
> same level of trust as a whql cert, but from past experience I do
> know that
> for bus drivers/extenders, whql has precedence
>
> in the past we had raised this issue with msft, that our verisign
> signed
> drivers are throwing up warnings while installing, and the ans we
> got was
> that the popup will go away if the driver is whql signed…
>
>
> but i do wonder why they cant show version info as well for a
> verisign class
> 3 signed bus extender.
>
>
> On Fri, Jan 24, 2014 at 11:51 PM, Speer, Kenny
> >
> wrote:
>
>
> Well of course there is more. All you’ve shown is a generic
> verioninfo.rc file. You have to assign your specific strings. Do
> you have
> another .h or .rc file which actually assigns values to the fields?
>
>
>
> From: xxxxx@lists.osr.commailto:xxxxx
> [mailto:xxxxx@lists.osr.commailto:xxxxx] On Behalf Of Ami
> Awbadhho
> Sent: Friday, January 24, 2014 7:16 AM
>
>
> To: Windows System Software Devs Interest List
>
> Subject: Re: [ntdev] Verifier GUI and Provider Names
>
>
>
>
>
> all that is there …
>
>
>
> what else needs to be added for this?
>
>
>
>
>
> //--------------------------------------------------------------------------
> -
>
> //
>
> // Version
>
> //
>
>
>
> //--------------------------------------------------------------------------
> -
>
> VS_VERSION_INFO VERSIONINFO
>
> FILEVERSION
> VER_FILEVERSION_DWORDS
>
> PRODUCTVERSION
> VER_PRODUCTVERSION_DWORDS
>
> FILEFLAGSMASK VER_FILEFLAGSMASK
>
> FILEFLAGS VER_FILEFLAGS
> |
> VS_FF_SPECIALBUILD
>
> FILEOS VER_FILEOS
>
> FILETYPE
> VER_FILETYPE
>
> FILESUBTYPE VER_FILESUBTYPE
>
> BEGIN
>
> BLOCK “StringFileInfo”
>
> BEGIN
>
> BLOCK “040904B0” /*
> LANG_ENGLISH/SUBLANG_ENGLISH_US, Unicode CP */
>
> BEGIN
>
> VALUE “CompanyName”,
> VER_COMPANYNAME_STR
>
> VALUE “FileDescription”,
> VER_FILEDESCRIPTION_STR
>
> VALUE “FileVersion”,
> VER_FILEVERSION_STR
>
> VALUE “InternalName”,
> VER_INTERNALNAME_STR
>
> VALUE “LegalCopyright”,
> VER_LEGALCOPYRIGHT_STR
>
> VALUE “LegalTrademarks”,
> VER_TRADEMARKS_STR
>
> VALUE “ProductName”,
> VER_PRODUCTNAME_STR
>
> VALUE “ProductVersion”,
> VER_PRODUCTVERSION_STR
>
> VALUE “SpecialBuild”,
> VER_SPECIALBUILD_STR
>
> END
>
>
>
> END
>
>
>
> BLOCK “VarFileInfo”
>
> BEGIN
>
> VALUE “Translation”, VER_VERSION_TRANSLATION
>
> END
>
> END
>
>
>
>
>
> On Fri, Jan 24, 2014 at 8:35 PM, Doron Holan
> > wrote:
>
> You need to add version info to your resources
> section of
> the binary, ie the .rc file
>
> d
>
> Bent from my phone
>
> ________________________________
>
>
> From: Ami Awbadhho mailto:xxxxx>
>
> Sent: 1/24/2014 5:54 AM
> To: Windows System Software Devs Interest List
>
> mailto:xxxxx>
>
> Subject: [ntdev] Verifier GUI and Provider Names
>
> All,
>
>
>
> we have a KMDF based root bus extender. When we
> launch
> verifier to add this driver to the test list, we see that the
> ‘Provider’
> fielnd and the ‘version’ field are coming as ‘’ in the GUI.
>
>
>
> In teh INF of the driver we have all the proper
> fields
> defined and when we right click on the sys file and do a ‘details’
> view, it
> also shows everything properly, that is version, company name etc
> etc.
>
>
>
> The question is what extra is needed to make the
> display of
> verifier happy?
>
>
>
> Thanks in advance.
>
>
>
> Awbadhho
>
> — NTDEV is sponsored by OSR Visit the list at:
> http://www.osronline.com/showlists.cfm?list=ntdev
> http: OSR is HIRING!!
> See
>
> http://www.osr.com/careers http: For our
> schedule of
>
> WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars To
> unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
>
> —
> NTDEV is sponsored by OSR
>
> Visit the list at:
> http://www.osronline.com/showlists.cfm?list=ntdev
> http:
>
> OSR is HIRING!! See http://www.osr.com/careers
>
> For our schedule of WDF, WDM, debugging and other
> seminars
> visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR
> Online
> at http://www.osronline.com/page.cfm?name=ListServer
> http:
>
>
>
> — NTDEV is sponsored by OSR Visit the list at:
> http://www.osronline.com/showlists.cfm?list=ntdev
> http: OSR is HIRING!!
> See
>
> http://www.osr.com/careers http: For our
> schedule of
>
> WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars To
> unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
>
> —
> NTDEV is sponsored by OSR
>
> Visit the list at:
> http://www.osronline.com/showlists.cfm?list=ntdev
>
>
> OSR is HIRING!! See http://www.osr.com/careers
>
> For our schedule of WDF, WDM, debugging and other seminars
> visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online
> at
> http://www.osronline.com/page.cfm?name=ListServer
>
>
> — NTDEV is sponsored by OSR Visit the list at:
> http://www.osronline.com/showlists.cfm?list=ntdev OSR is HIRING!!
> See
> http://www.osr.com/careers For our schedule of WDF, WDM, debugging
> and other
> seminars visit: http://www.osr.com/seminars To unsubscribe, visit
> the List
> Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
>
> —
> NTDEV is sponsored by OSR
>
> Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev
>
> OSR is HIRING!! See http://www.osr.com/careers
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
>
>
> — NTDEV is sponsored by OSR Visit the list at:
> http://www.osronline.com/showlists.cfm?list=ntdev OSR is HIRING!! See
> http://www.osr.com/careers For our schedule of WDF, WDM, debugging and
> other
> seminars visit: http://www.osr.com/seminars To unsubscribe, visit the List
> Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
>
> —
> NTDEV is sponsored by OSR
>
> Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev
>
> OSR is HIRING!! See http://www.osr.com/careers
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
—
NTDEV is sponsored by OSR
Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev
OSR is HIRING!! See http://www.osr.com/careers
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
— NTDEV is sponsored by OSR Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev OSR is HIRING!! See http://www.osr.com/careers For our schedule of WDF, WDM, debugging and other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer</http:></http:></http:></http:></http:></http:></mailto:xxxxx></mailto:xxxxx></mailto:xxxxx></mailto:xxxxx></mailto:xxxxx></mailto:xxxxx></mailto:xxxxx></mailto:xxxxx></mailto:xxxxx></mailto:xxxxx>