3 ms·

Interception is LGPL[1], the issue is that Windows requires drivers to be signed and code signing certs aren't cheap. That's also why interception has not updat

by accoil 2y ago

Interception is LGPL[1], the issue is that Windows requires drivers to be signed and code signing certs aren't cheap. That's also why interception has not updated in years to fix the bug where it only supports 10 devices to be connected each boot (each reconnects count as a separate device)[2]. [1]: https://github.com/oblitum/Interception/blob/master/licenses/non-commercial-usage/LGPL%203.0.txt https://github.com/oblitum/Interception/blob/master/licenses... [2]: https://github.com/oblitum/Interception/issues/193 https://github.com/oblitum/Interception/issues/193

pseudalopex 2y ago
> Interception is LGPL The library is LGPL for non commercial purposes. A contradiction. Drivers and installers are called binary assets. Access to all source code is provided with a commercial license.[1] [1] https://github.com/oblitum/Interception/blob/master/README.md#license https://github.com/oblitum/Interception/blob/master/README.m...
- accoil 2y ago
  Oh right, I keep forgetting that. The LGPL part is just the library that lets apps talk to the driver. I still think the main thing Interception has going for it is code signing. I once wrote a keyboard filter driver for personal use, but due to signing requirements I never felt it was worth the trouble & cost trying to use it past the computer I developed it on (and then later moved to firmware based solutions like QMK).
- wakawaka28 2y ago
  The LGPL license applies to the code that they do provide. It's kinda misleading but you have the option to pay and get the code, or not pay and only get what you see. Seems fair enough.
  - pseudalopex 2y ago
    The contradiction is not the library is LGPL and the driver and installer are proprietary. The contradiction is LGPL does not allow a non commercial restriction.
shlomo_z 2y ago
Theoretically, can't people make their own self signed certificates (I assume Windows allows that for development)
- accoil 2y ago
  You can enable test mode[1] which lets you use any certificate, but outside of test mode you need an EV code signing cert[2]. [1]: https://learn.microsoft.com/en-us/windows-hardware/drivers/install/the-testsigning-boot-configuration-option https://learn.microsoft.com/en-us/windows-hardware/drivers/i... [2]: https://learn.microsoft.com/en-us/windows-hardware/drivers/dashboard/code-signing-reqs https://learn.microsoft.com/en-us/windows-hardware/drivers/d...
shlomo_z 2y ago
I really dislike people calling it a bug because the developer put it in there intentionally as a limitation.

by accoil 2y ago

pseudalopex 2y ago

> Interception is LGPL The library is LGPL for non commercial purposes. A contradiction. Drivers and installers are called binary assets. Access to all source code is provided with a commercial license.[1] [1] https://github.com/oblitum/Interception/blob/master/README.md#license https://github.com/oblitum/Interception/blob/master/README.m...

accoil 2y ago
Oh right, I keep forgetting that. The LGPL part is just the library that lets apps talk to the driver. I still think the main thing Interception has going for it is code signing. I once wrote a keyboard filter driver for personal use, but due to signing requirements I never felt it was worth the trouble & cost trying to use it past the computer I developed it on (and then later moved to firmware based solutions like QMK).
wakawaka28 2y ago
The LGPL license applies to the code that they do provide. It's kinda misleading but you have the option to pay and get the code, or not pay and only get what you see. Seems fair enough.
- pseudalopex 2y ago
  The contradiction is not the library is LGPL and the driver and installer are proprietary. The contradiction is LGPL does not allow a non commercial restriction.

shlomo_z 2y ago

Theoretically, can't people make their own self signed certificates (I assume Windows allows that for development)

accoil 2y ago
You can enable test mode[1] which lets you use any certificate, but outside of test mode you need an EV code signing cert[2]. [1]: https://learn.microsoft.com/en-us/windows-hardware/drivers/install/the-testsigning-boot-configuration-option https://learn.microsoft.com/en-us/windows-hardware/drivers/i... [2]: https://learn.microsoft.com/en-us/windows-hardware/drivers/dashboard/code-signing-reqs https://learn.microsoft.com/en-us/windows-hardware/drivers/d...

shlomo_z 2y ago

I really dislike people calling it a bug because the developer put it in there intentionally as a limitation.