TwinHaelix
Unfortunately, I think you’re unlikely to find anything besides the ones made by the big companies: Google, Apple, Samsung, and Garmin are the ones I know. They each have agreements with the banks and credit card companies to handle the secure exchange of data required for the touch payment system. In fact, there are still some issues resulting from a lack of cooperation (such as Citi Bank not working with Garmin Pay because they can’t be bothered to set up the relationship). I imagine an open source software would be unable to get the banks to pay attention to them to establish a partnership, or would otherwise be declined because the financial institutions wouldn’t trust them.
Creating a driver requires a deep understanding of some pretty low-level pieces of Linux. If you’re new to Linux, you should probably start with some “new to Linux” tutorials and get an understanding of some basic command line usage. Work your way up to being able to follow a guide on compiling the Linux kernel (without any of your own modifications). After that, you can seek out guides on creating a driver.
As a second note, fingerprint drivers are categorically difficult to work with, so this would really be jumping in on the deepest of deep ends. You can do it! But it will take a LOT of self-education.
Fix is to address a critical CVE:
Specific handling of an attacker-controlled VP8 media stream could lead to a heap buffer overflow in the content process. We are aware of this issue being exploited in other products in the wild.
Just want to shout out to reviewbrah for giving us this absolute gem of a phrase
KMS requires phoning back to MS periodically to keep the license activated. It’s still “permanent” because there’s no limit on duration (as of now at least).
HWID activation registers a hardware ID in MS servers to permanently license it. That means no renewal, just forever activation that survives reinstalls.