Yes … get the driver signed. With Server 2003 I believe you can acquire an Authenticode certificate from Verisign, or another authority, and sign the driver your self.
–
The personal opinion of
Gary G. Little
“Vikas Ahluwalia” wrote in message news:xxxxx@ntdev…
I am trying to install a PNP driver (unsigned) in windows 2003 from a remote session using Setup APIs. This pops-up the unsigned driver security window warning the user that the driver is not signed by WHQL. The problem is that this window does not pop up at remote session but on main machine session.
Is there a work-around?
Can I detect that I am running in remote session via windows API?
-Vikas
The driver is already signed using Authenticate certificate from Verisign. However it is not WHQL signed and I need a solution for the test teams that work from remote sessions with the daily builds (non-WHQL signed driver).
Vikas
“Gary G. Little” wrote in message news:xxxxx@ntdev…
Yes … get the driver signed. With Server 2003 I believe you can acquire an Authenticode certificate from Verisign, or another authority, and sign the driver your self.
–
The personal opinion of
Gary G. Little
“Vikas Ahluwalia” wrote in message news:xxxxx@ntdev…
I am trying to install a PNP driver (unsigned) in windows 2003 from a remote session using Setup APIs. This pops-up the unsigned driver security window warning the user that the driver is not signed by WHQL. The problem is that this window does not pop up at remote session but on main machine session.
Is there a work-around?
Can I detect that I am running in remote session via windows API?
-Vikas
It depends on the class of the device/driver:
* If the device is a class for which there are WHQL tests, then
you can get a test signature from Microsoft for each daily build - you
have to also install a test certificate on the systems but that only
needs to be done once. The process of getting a test signature is,
unfortunately, somewhat manual - you have to build a cab file and submit
it via a web site - so it’s not possible to build this into your
automated nightly build.
* If the device is a class for which there are no WHQL tests then
you can self-sign the driver in W2K3 - you still have to install your
certificate on the test systems but again that only needs to be done
once.
I must admit I’m a bit woolly on the distinction between the two classes
- I know that, for example, SCSIPort and NDIS NIC drivers cannot be
self-signed and PCI bus filter drivers can but I’ve never seen a
definitive list of what classes can and can not be self signed…
/simgr
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Vikas Ahluwalia
Sent: Thursday, August 04, 2005 1:56 PM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] how to handle unsigned driver popup in installation
from remote session?
The driver is already signed using Authenticate certificate from
Verisign. However it is not WHQL signed and I need a solution for the
test teams that work from remote sessions with the daily builds
(non-WHQL signed driver).
Vikas
“Gary G. Little” wrote in message
news:xxxxx@ntdev…
Yes … get the driver signed. With Server 2003 I believe you
can acquire an Authenticode certificate from Verisign, or another
authority, and sign the driver your self.
–
The personal opinion of
Gary G. Little
“Vikas Ahluwalia” wrote in message
news:xxxxx@ntdev…
I am trying to install a PNP driver (unsigned) in
windows 2003 from a remote session using Setup APIs. This pops-up the
unsigned driver security window warning the user that the driver is not
signed by WHQL. The problem is that this window does not pop up at
remote session but on main machine session.
Is there a work-around?
Can I detect that I am running in remote session via
windows API?
-Vikas
—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com