![hardware fingerprint generator hardware fingerprint generator](https://ageecomputer.com/wp-content/uploads/2019/10/c-6.jpg)
- Hardware fingerprint generator full#
- Hardware fingerprint generator software#
- Hardware fingerprint generator license#
- Hardware fingerprint generator windows#
Not only does our license server rely on this, but also our client package for the license manager. Our entire licensing eco-system revolves strongly around this part of the API. Net Framework, it means that our applications that are running on Core would no longer be able to work correctly. I refer to the link below, or am I misunderstanding?Īs the decision that has been made for ASP.NET Core to stop support for the.
Hardware fingerprint generator full#
To the best of my knowledge it does exist in the full framework today. I see only 1 vote here, hence it is naturally lower in the backlog.
![hardware fingerprint generator hardware fingerprint generator](https://maker.pro/storage/cXoFfmw/cXoFfmwreMGBPUi4mBZuCq0z94cVAKiBjuFvoZQH.jpeg)
I don't understand why lack of this API would affect your decision to drop ASP.NET Core. It is up-for-grabs, so anyone is welcome to take a stab at it. It is marked Future = we do not intend to work on it now. I updated the text above with link and "next steps" prefix, that will hopefully clarify it - sorry for the text not being clear (it was at the time we just started with proper triage). I really think there is a need for such an api to exist as their are truly many use cases that warrant it. In another example we are using that fingerprint to identify nodes in a distributed communication system. I think that solution sat well with clients because within 3 months if memory serves me correctly, there was around 100Gb moving through Azure a month.
Hardware fingerprint generator software#
That allowed us to deliver software without requiring the customer in question to first acquire a static ip address to expose their services to mobile devices and other server instances. While it is not hack proof if there even still exists such a notion, we find that in our specific industry it serves us well.Īs for the particulars for the example you had a question about, an instance of that software connects a local running service (SOAP as example) and then connects it to the public internet via Azure Service Bus, specifically a relay binding. In another project, we are using the above to create a fingerprint used for licensing server instances of our software.
![hardware fingerprint generator hardware fingerprint generator](https://enscape3d.com/community/wp-content/uploads/2021/03/al_apply_button.png)
Net framework's () to get hardware information and then from that constructed a fingerprint.
Hardware fingerprint generator windows#
Of course that solution was on Windows and we used the. The example I added was just 1 feature we have built before that required a unique per device id, which we called a fingerprint. I am merely trying to show that licensing is not the only use case to have a fingerprint or the ability to create one from hardware information. While virtualisation comes with its own set of issues, those issues are more relevant and perhaps more problematic when it comes to licensing as a use case.
![hardware fingerprint generator hardware fingerprint generator](http://media.gadgetsin.com/2013/01/myidkey_fingerprint_secure_bluetooth_usb_drive_3.jpg)
This allowed customers to not require a public ip address for the software to which devices and services connect too. This also has other use cases other than licensing, I was involved in a project which delivers a service to customers, where each instance of the application gets a unique fingerprint for the hardware that it is currently running on, it then dynamically creates Azure service bus items. If providing a "fingerprint" method is harder to achieve, I think providing developers with an api that will allow them to get hardware details which they can use to create their own fingerprint for their software. While it may make sense for a user app to be able to transition from device to device the same should not be said for server applications. I think that there should be a distinction between user applications and server applications.