[hpsdr] Ozy/Magister will likely stop working on Win10 in about 60 days

[George Byrkit]

Scott,
This may or may not work on Windows 10.  Certainly I am ONLY talking about Windows 10 Build 1607 and later.  It is not reasonable to expect a Ham to take a boot-time choice each time they (re)boot their computers.  I'm speaking about generally booting a computer.  I suggest that you review the article and other related information and make your own conclusion.

What happens for debugging a driver under development is not relevant to what happens when you use a driver as a normal computer user.  I'm telling you that MANY drivers from the past will stop working on Windows 10 at Day 60 (or is it 90) after the release of Windows 10 Anniversary (build 1607), which occurred on August 2, 2016.  One of those affected is the Ozy/Magister 'libusb0' USB driver.

And it is a separate issue if you have Secure Boot enabled in the BIOS of a modern computer.  YMMV.  Read, be informed, and draw your own conclusions that are relevant to how you use drivers.

I had not seen a warning about this published on this list.  This will affect many pieces of HAM hardware, not just USB devices.  It could affect printers, things like MicroHam 'digikeyer' products and the like, and other pieces of hardware.

73,
George K9TRV

-----Original Message-----
From: Scott Traurig [mailto:scott.traurig at gmail.com] 
Sent: Saturday, August 20, 2016 11:07 AM
To: George Byrkit <ghbyrkit at chartermi.net>
Cc: OpenHPSDR <hpsdr at openhpsdr.org>
Subject: Re: [hpsdr] Ozy/Magister will likely stop working on Win10 in about 60 days

George,

Will this no longer work?

http://www.howtogeek.com/167723/how-to-disable-driver-signature-verification-on-64-bit-windows-8.1-so-that-you-can-install-unsigned-drivers/


73,

Scott/w-u-2-o


On Sat, Aug 20, 2016 at 10:51 AM, George Byrkit <ghbyrkit at chartermi.net <mailto:ghbyrkit at chartermi.net> > wrote:


	***** High Performance Software Defined Radio Discussion List *****
	
	Dear all,
	
	So Microsoft has a policy for double-signed drivers on Windows 10 that didn't exist
	before, and it will take place between 60 and 90 days after the release of Windows 10
	Anniversary (build 1607).
	
	The purpose of this is to ensure that the drivers are fully signed and fully trusted, at a
	level that is greater than before, in order to be able to load on any computer with Secure
	Boot active in the BIOS.
	
	I won't enter into a debate as to whether this is a good thing or a bad thing.  I will
	only point out that the Ozy/Magister USB drivers for PowerSDR, KISS Konsole, etc., are NOT
	double-signed, and I don't really see a need to do that, and take the time, and spend the
	money to do so.
	
	While the current Ozy/Magister USB driver is single-signed, it is signed with a
	certificate that is too old to be able to put the package thru Microsoft to get their
	counter-signature.  If you want more information, I suggest that you visit
	http://www.osr.com/developers-blog <http://www.osr.com/developers-blog>  and check the article 'Driver Signing - more details
	emerge".
	
	To do all of this requires a 'code signing certificate' from one of the vendors of such
	certificates, apparently with 'EV' (extended validation?)  Such seem to cost $200-$400 per
	year.  Since everything new uses Metis technology (Ethernet), I don't think that it is
	worth the cost or the hassle to keep supporting Ozy/Magister on Windows 10.  If someone
	who wants it to keep working donates the money, there might be a chance to reconsider.
	
	73,
	George K9TRV
	
	_______________________________________________
	HPSDR Discussion List
	To post msg: hpsdr at openhpsdr.org <mailto:hpsdr at openhpsdr.org> 
	Subscription help: http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org <http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org> 
	HPSDR web page: http://openhpsdr.org
	Archives: http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/ <http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/>