are considered copyrighted IP in North America. Many of the paid device codes are often not like other Communication Device Class drivers or free generic HID devices listed in the USB standard.
Early next year Windows 11 will be locking out unsigned drivers from the OS. Good for keeping the kernel more consistent, but could be bad for hobby hardware drivers.
Personally, I think it is ludicrous, but for 83% of users they have no other option than pay $6.32 for a $$0.43 chip. =3
Yes they may be, but in the Sega v. Accolade case I mentioned earlier it was decided that copying of both copyrighted and trademarked material for interoperability purposes is fair use. In that case Accolade had to literally embed "SEGA" inside their ROM and send the text to the Genesis III in order for it to boot their games. The Ninth Circuit court ruled that this constituted fair use.
Hardware drivers not certified by the Microsoft lab will not install. No longer can folks dismiss the nag screen to run some bespoke piece of hardware.
This is apparently being done to improve kernel security and reliability. It could be a PR disaster depending how it is rolled out...
People can blame things like the old generic PC-case-bling LED driver CVE people and even its original author lost patience with years ago... lol =3
Hardware drivers not certified by the Microsoft lab will not install. No longer can folks dismiss the nag screen to run some bespoke piece of hardware.
Again, that's been the case since Windows 7. You have to go out of your way to boot the system in "Test Mode" to install an unsigned driver. Either that, or use Zadig to self-sign the driver. (Maybe they're no longer allowing that?)
Signatures were enforced only for 64-bit drivers in Windows 7, but Windows 10 enforces them for all drivers.
There is nothing in that article saying anything about any upcoming requirements. Also it is written by a ChatGPT bot account, so it would be an invalid source even if it did.
The only update even mentioned in that article is "Windows 10, version 1607 (the Anniversary Update released in August 2016)". In case you haven't noticed, that happened 9 years ago...
If at some point I can recall the interview from earlier this year, than I will post a link. Otherwise, we will both have to wait and see. Best regards. =3
What is "it" that might break something? There is nothing that is going to happen. The AI-slop you linked doesn't mention anything that is going to happen. It's just a summary of changes that have happened in the past and a list of pros and cons of the driver signing requirement from more than a decade ago. There is nothing to "wait and see" for.
It goes well beyond strict USB-C port WHCP compliance rules if I recall correctly, and is not about just banning old WinRing 0 nuisance drivers ( https://www.youtube.com/watch?v=H_O5JtBqODA ).
I can't put any significant time into a proper search right now, but if I recall the interview I'll post a URI. Have a great day. =3
> copycats are free to write thier own drivers though?
Sure, anyone paying for a Microsoft certified hardware driver, USB PID allocation, and cert fees every year... Everyone else is not allowed in the OS we paid for...
It is a decades old serial port emulation chip... Racketeering with a computer should still be illegal. =3
I can kinda see where the idea of "copyrighting a number" makes sense when you're talking about a number that's multiple kilobytes in size, but trying to stake a legal claim to one of the 65536 possible 16-bit numbers is just wrong imo.
Indeed, the USB standards body prevented allocated company VID reuse, and thus greatly simplified identifying the correct hardware. There is also additional generic information like company name (often Trademarked) or serial number that may be queried from many devices as well.
If it were free or cheap, than people would have just started another domain squatting business. That could have been far worse. =3
> lsusb
or
C:\> Get-PnpDevice -PresentOnly | Where-Object { $_.InstanceId -match '^USB' } | Format-List
are considered copyrighted IP in North America. Many of the paid device codes are often not like other Communication Device Class drivers or free generic HID devices listed in the USB standard.
Early next year Windows 11 will be locking out unsigned drivers from the OS. Good for keeping the kernel more consistent, but could be bad for hobby hardware drivers.
Personally, I think it is ludicrous, but for 83% of users they have no other option than pay $6.32 for a $$0.43 chip. =3