# Nitrokey as license token

**URL:** <https://support.nitrokey.com/t/nitrokey-as-license-token/1147>\
**Category:** Nitrokeys\
**Created:** [June 4, 2018, 9:18am UTC](https://support.nitrokey.com/t/nitrokey-as-license-token/1147 "2018-06-04T09:18:33Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![andre](https://support.nitrokey.com/letter_avatar_proxy/v4/letter/a/6de8d8/32.png) [@andre](https://support.nitrokey.com/u/andre)\
**Post date:** [June 4, 2018, 9:18am UTC](https://support.nitrokey.com/t/nitrokey-as-license-token/1147/1 "2018-06-04T09:18:33Z")

</div>

hey,

we are currently exploring the Nitrokey to act as license token for one of our products to replace a mechanism that currently uses the host id of the machine. Ultimately, the software should run on any machine that has valid Nitrokey plugged into it.

I was wondering if anyone else has done something similar before and would be willing to share  
experience? What we are thinking of doing right now is to (1) create a key-pair on the device, (2) sign those  
keys with one of our licensing keys, and then upon startup of the software (3) let the token authenticate  
itself (a random challenge that is encrypted on the token) and (4) check that the public key  
is signed with our licensing key (whose public part is stored in the software binary).

Does anyone see anything wrong with that approach?

Thanks  
Andre

---

<div class="post-metadata">

**Author:** ![Peacekeeper](https://support.nitrokey.com/user_avatar/support.nitrokey.com/peacekeeper/32/132_2.png) [@Peacekeeper](https://support.nitrokey.com/u/Peacekeeper)\
**Post date:** [June 6, 2018, 8:57pm UTC](https://support.nitrokey.com/t/nitrokey-as-license-token/1147/2 "2018-06-06T20:57:43Z")

</div>

Hmm, why do you not use a stick that is build to do this for you - e.g. like CodeMeter from Wibu [http://codemeter.de/us/index.html](http://codemeter.de/us/index.html) ?

It might also workk with the NK, but you might need more effort to do so …  
Just an idea …

---

<div class="post-metadata">

**Author:** ![Herve5](https://support.nitrokey.com/user_avatar/support.nitrokey.com/herve5/32/235_2.png) [@Herve5](https://support.nitrokey.com/u/Herve5)\
**Post date:** [February 13, 2019, 9:55am UTC](https://support.nitrokey.com/t/nitrokey-as-license-token/1147/3 "2019-02-13T09:55:23Z")

</div>

I read this far too late I presume, but I find funny that our OP is asking here for open signature technologies and we manage to tell him to go away to a similar competitor, but closed… 🤔

---

<div class="post-metadata">

**Author:** ![Peacekeeper](https://support.nitrokey.com/user_avatar/support.nitrokey.com/peacekeeper/32/132_2.png) [@Peacekeeper](https://support.nitrokey.com/u/Peacekeeper)\
**Post date:** [March 13, 2019, 8:02am UTC](https://support.nitrokey.com/t/nitrokey-as-license-token/1147/4 "2019-03-13T08:02:41Z")

</div>

Yeah, might be - but on the other side: you don’t use the same car for transportation, speed racing and other stuff, when there is a good solution in place for each separate area of duty. So I think you should use currently NK as designed (key storage and encryption).  
BTW: if you want to use a dongle for licensing, I have my doubts if you really want to publish the way how you check the dongle, nor ?  
Anyhow, nobody else has answered, so I assume nobody did use NK as dongle replacement.
