-
-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Driver use authorization. #37
Comments
Precisely, our TOS does not allow unauthorized use as mentionned here :
« … provided that you do not (and do not allow any third party to) copy, modify, create a derivative work of, reverse engineer, reverse assemble or otherwise attempt to discover any source code, sell, assign, sublicense, grant a security interest in or otherwise transfer any right in the CPUID Services or remove or obscure the copyright notice or other notices displayed on the content. »
Why don’t you code your own driver ??
De : Artem Mikoulyak ***@***.***>
Envoyé : samedi 7 octobre 2023 00:55
À : 1a2m3/SPD-Reader-Writer ***@***.***>
Cc : CPUID2021 ***@***.***>; Author ***@***.***>
Objet : Re: [1a2m3/SPD-Reader-Writer] Driver use authorization. (Issue #37)
https://www.cpuid.com/terms-of-service.html
—
Reply to this email directly, view it on GitHub <#37 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AWYEWQPSOQY7ANDTHUUFHULX6CD5PAVCNFSM6AAAAAA5WIICJKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJRGQ4DCNBZGA> .
You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AWYEWQLGO4S27EULBAHJI6TX6CD5PA5CNFSM6AAAAAA5WIICJKWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTIMV6JE.gif> Message ID: ***@***.*** ***@***.***> >
|
How can I contact you to confirm you are from CPUID? I don't think the part you quoted applies to me. I didn't distribute any sources or modification of your work. The first part of the sentence you quoted, starts with "You are hereby granted a personal, nonexclusive, nontransferable, revocable, limited license to view, reproduce, print, cache, store and distribute content retrieved from our Site via a generally available consumer web browser". CPU-Z, which you do allow to download, use and distribute, comes with the driver, which automatically gets installed whenever CPU-Z is started. Anyone can download CPU-Z and use your driver when CPU-Z installs it in %temp% directory. You also sell CPUID SDK, which also uses cpuz driver, but if you aren't happy with a private individual using your SDK in my free project, I can remove all references to cpuz, deal? Why are you witch-hunting me? There are hundreds of other projects that use CPUID SDK and CPUZ drivers, yet you only used your account to shame me, even though you've been here for 2 years. 😔 |
Or would you rather allow me include a reference to CPUID SDK in my project? I'm a hobbyist programmer, not a lawyer, so if you are from CPUID, tell me how I can make things right. |
Hello Artem,
My name is Franck Delattre, I’m well from CPUID, you can contact me at ***@***.*** ***@***.***> or ***@***.*** ***@***.***> .
There is a major difference between distribute cpuz (and its associated driver files) and publically publish the IO control codes. I guess you did not find them in the nature, but by reverse. Then the TOS applies.
But more important : by publishing the IO control codes as you did in CpuZ.cs, you allow anyone to use the cpuz driver in his own project. That is an open door to any malwares / cheat programs / whatever requires kernel fonctions.
The consequence is very predictible : MS will simply block the driver. They already did in the past, FYI.
Why do you think WinRing0 can’t be used anymore ?
For you information, the SDK does not provide the customers with a direct access to the driver functions. Instead, they use high level fonctions in a DLL.
Considering your work, you’re 200% skilled to produce your own kernel mode driver. I know the signature is a major problem, but MS drastic requirements are not my fault or responsability.
By exposing my driver interface as you did, you provide MS with a good reason to block my driver.
I don’t see any other alternative than removing CpuZ.cs.
Thanks,
Franck
De : Artem Mikoulyak ***@***.***>
Envoyé : samedi 7 octobre 2023 11:11
À : 1a2m3/SPD-Reader-Writer ***@***.***>
Cc : CPUID2021 ***@***.***>; Author ***@***.***>
Objet : Re: [1a2m3/SPD-Reader-Writer] Driver use authorization. (Issue #37)
How can I contact you to confirm you are from CPUID?
I don't think the part you quoted applies to me. I didn't distribute any sources or modification of your work.
The first part of the sentence you quoted, starts with "You are hereby granted a personal, nonexclusive, nontransferable, revocable, limited license to view, reproduce, print, cache, store and distribute content retrieved from our Site via a generally available consumer web browser".
CPU-Z, which you do allow to download, use and distribute, comes with the driver, which automatically gets installed whenever CPU-Z is started. Anyone can download CPU-Z and use your driver when CPU-Z installs it in %temp% directory.
You also sell CPUID SDK <https://www.cpuid-pro.com/products-system-information-kit.php> , which also uses cpuz driver, but if you aren't happy with a private individual using your SDK in my free project, I can remove all references to cpuz, deal?
Why are you witch-hunting me? There are hundreds of other projects that use CPUID SDK and CPUZ drivers, yet you only used your account to shame me, even though you've been here for 2 years. 😔
—
Reply to this email directly, view it on GitHub <#37 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AWYEWQNWEZXGFDFMYD2FK4TX6EMAZAVCNFSM6AAAAAA5WIICJKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJRGY2TSNRTGM> .
You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AWYEWQNBZMB6LI622QS6ZL3X6EMAZA5CNFSM6AAAAAA5WIICJKWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTINA2HC.gif> Message ID: ***@***.*** ***@***.***> >
|
Who authorized you to use the cpuz driver ?
The text was updated successfully, but these errors were encountered: