Difference between revisions of "Talk:Driver Signing"
Colin Finck (talk | contribs) |
|||
| Line 5: | Line 5: | ||
I just don't get it. | I just don't get it. | ||
:The complete feature list says: ''(32-bit only) Bypass almost all forms of process protection''. As the foundation only signs the 64-bit version, this feature is not included. (Disclaimer: I'm not involved in this Driver Signing initiative) - [[User:Colin Finck|Colin Finck]] 12:19, 11 March 2011 (UTC) | :The complete feature list says: ''(32-bit only) Bypass almost all forms of process protection''. As the foundation only signs the 64-bit version, this feature is not included. (Disclaimer: I'm not involved in this Driver Signing initiative) - [[User:Colin Finck|Colin Finck]] 12:19, 11 March 2011 (UTC) | ||
| + | |||
| + | Where are the drastically changed requirements for signing described? Some community members are interested as to what happened, I'd like to give them a link. --[[User:Black Fox|Black Fox]] ([[User talk:Black Fox|talk]]) 16:55, 16 February 2017 (UTC) | ||
Latest revision as of 16:55, 16 February 2017
- This offer is contingent on fulfilling the following conditions: The driver may not be used to circumvent security features in the OS.
- Key features of Process Hacker: Powerful process termination that bypasses security software.
- Projects signed by the ReactOS Foundation: Process Hacker
I just don't get it.
- The complete feature list says: (32-bit only) Bypass almost all forms of process protection. As the foundation only signs the 64-bit version, this feature is not included. (Disclaimer: I'm not involved in this Driver Signing initiative) - Colin Finck 12:19, 11 March 2011 (UTC)
Where are the drastically changed requirements for signing described? Some community members are interested as to what happened, I'd like to give them a link. --Black Fox (talk) 16:55, 16 February 2017 (UTC)
