Prev: INF for Ports class CDC USB device using usbser.sys fails DTM
Next: Access permission for registry in Windows 7
From: Tim Roberts on 25 Apr 2010 22:59
"mpv" <nospam(a)tiscali.nl> wrote:
>
>In this specific case (already signed WinUSB), I don't think so, and I am
>speaking from experience.
>We use a Wise script, together with the WinUSB co-installers, DPInst.exe
>(which also has a 64 bit version), and the .inf file with corresponding
>signed .cat file. That is enough. On installing the package on Vista 64 or
>W7 64, we do not get a warning, just a dialog whether you want to trust our
>company in future.

Yes, that's the one. If the package is WHQL signed, there's no dialog at
all -- the driver installs silently.

As I said, it depends on what you need. Or, more accurately, what your
marketing department demands...
--
Tim Roberts, timr(a)probo.com
Providenza & Boekelheide, Inc.
From: mpv on 26 Apr 2010 15:25
Hi,

"Tim Roberts" <timr(a)probo.com> wrote in message
news:ca0at59o4u8vnpj9rbv3saa9i1jdsk3764(a)4ax.com...
>
> Yes, that's the one. If the package is WHQL signed, there's no dialog at
> all -- the driver installs silently.
>
> As I said, it depends on what you need. Or, more accurately, what your
> marketing department demands...
> --
I think there is a huge difference between a BIG RED warning, that advises
you NOT to install this driver, and a dialog that asks whether you want to
trust this company also in future (meaning the company's certificate is
added to a trusted category in the certificate store).
I don't know what else could happen with cross certificates. Surely this is
the procedure that was meant by Microsoft when they provided these cross
certificates?

Regards, Matt


From: Tim Roberts on 28 Apr 2010 01:14
"mpv" <nospam(a)tiscali.nl> wrote:
>
>I think there is a huge difference between a BIG RED warning, that advises
>you NOT to install this driver, and a dialog that asks whether you want to
>trust this company also in future (meaning the company's certificate is
>added to a trusted category in the certificate store).
>I don't know what else could happen with cross certificates. Surely this is
>the procedure that was meant by Microsoft when they provided these cross
>certificates?

The cross certificates are used for KMCS, not for package signing. A
64-bit driver will not load at all unless it's signed with a code-signing
certificate and the appropriate cross certificate.
--
Tim Roberts, timr(a)probo.com
Providenza & Boekelheide, Inc.
From: JoeB on 29 Apr 2010 04:11
"mpv" wrote:

> In this specific case (already signed WinUSB), I don't think so, and I am
> speaking from experience.
> We use a Wise script, together with the WinUSB co-installers, DPInst.exe
> (which also has a 64 bit version), and the .inf file with corresponding
> signed .cat file. That is enough. On installing the package on Vista 64 or
> W7 64, we do not get a warning, just a dialog whether you want to trust our
> company in future.

Matt, I've been lurking for a while reading your posts and I must say I
think you have the best handle on this situation than anyone else. Bravo.
I'm trying to figure out how to do an automatic install of the driver before
the user plugs the device in, you mentioned using a WISE script, is there any
way you could share that or how it works? Or could you or someone else give
me some direction on how I can pre-install the driver before the device gets
plugged in? I'd be happy to pay you or anyone for their help. Post back or
email please.
From: JoeB on 29 Apr 2010 04:33
Forgot to mention my email address: joebemoan(a)hotmail.com
First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: INF for Ports class CDC USB device using usbser.sys fails DTM
Next: Access permission for registry in Windows 7