Re: [Libusb-win32-devel] Antwort: 64-bit support

[Paarvai N. <ope...@gm...>]

Hi Graeme,

Yes, it does appear that the publisher can self-sign once they have
obtained a software publishing certificate (SPC) from Microsoft.  The
process of obtaining the SPC requires a Verisign certificate which
costs ~$500.

Paarvai

On Nov 9, 2007 2:27 AM, Graeme Gill <gr...@ar...> wrote:
> Stephan Meyer wrote:
>
> > It's not possible to sign just a driver (.sys file).
> > You always have to sign the combination of the driver and the device
> > specific .inf file.
>
> Since Microsoft seem to have at least shifted their policy to
> allow companies other than themselves to sign drivers ("Self-Signing"),
> this seems more feasible that it once was, but it's still
> a significant barrier to non-commercial developers.
>
> Is there any distinction between how unsigned .sys and
> unsigned .inf files are handled ?
>
> As I understand it, the administrator simply cannot load an
> unsigned .sys file, unless the operating system has
> been booted up with some special flags that permit this.
>
> Does anyone know if the same apply to .inf files, or is it
> merely that the administrator will get an warning/OK dialog for
> an unsigned .inf file ?
>
> If not, then there seems less point in continuing to develop
> a winusb.sys version of libusb-win32.
>
> Graeme Gill.
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>