Question about multiple identification methods

[ricardborras]

Hi,

thanks for good work on this library. I have 2 cases where I would run to license my software:

• Pc identification is based on a hw identifier (such as ETHERNET, CPU, etc)
• Pc identification is based on a text file

Second case is needed because my customers install computers and identifies them by a text file in the filesystem. I have forked library and added this second case using a new strategy. In my license project, I have added this strategy.

The question is that I would like to generate a executable with some parameters to manage both cases. How to do it? In method acquire_license from the API I cannot change the strategy, and it seems that it returns 2 ids for the same computer.

Thanks,

Ricard

[gcontini]

Hi Ricard,

Let me see if i understood your requirements:

1. if a file exists on the licensee computer use it to generate a pc identifier
2. if the file doesn't exist use the standard ETHERNET/DISK way to generate pc identifier.
3. when verify a license use the same method used to generate it.

Let me have a look to your branch this week-end

[ricardborras]

Hi, yes, those were my requirements. Unfortunately, these requirements have changed and your library does not fit as good as before. I changed to another library sorry for the inconvenience, Ricard

…

On Fri, Jun 11, 2021 at 8:35 AM Gabriele Contini ***@***.***> wrote: Hi Ricard, Let me see if i understood your requirements: 1. if a file exists on the licensee computer use it to generate a pc identifier 2. if the file doesn't exist use the standard ETHERNET/DISK way to generate pc identifier. 3. when verify a license use the same method used to generate it. Let me have a look to your branch this week-end — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#124 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACNRYLN64PJHKH6DJ6DJQALTSGVDRANCNFSM46KKWHJA> .

-- *Ricard Borràs Navarra* Linkedin: http://www.linkedin.com/in/ricardborras Twitter: https://twitter.com/RicardBorras

[BotellaA]

@ricardborras Which other library are you using? I might have some common requirements with you.

[ricardborras]

Yes, I use this one: https://github.com/amrayn/licensepp It uses a more flexible approach for computer identification (basically, you have to provide it on your own) and you can add a custom payload to licenses, which is something i need best, Ricard

…

On Mon, Jun 14, 2021 at 4:27 PM Arnaud Botella ***@***.***> wrote: @ricardborras <https://github.com/ricardborras> Can you tell which other library are you using? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#124 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACNRYLJVPA3BOKYS27FRZZLTSYGWHANCNFSM46KKWHJA> .

-- *Ricard Borràs Navarra* Linkedin: http://www.linkedin.com/in/ricardborras Twitter: https://twitter.com/RicardBorras

[gcontini]

Hi Richard, Good you've found something that solves your problem. Custom payload is supported also in licensecc: http://open-license-manager.github.io/licensecc/usage/issue-licenses.html (see parameter extra-data) And you can implement your own signature generator: http://open-license-manager.github.io/licensecc/api/hardware_identifiers.html On Mon, Jun 14, 2021 at 10:32 PM ricardborras ***@***.***> wrote:

…

Yes, I use this one: https://github.com/amrayn/licensepp It uses a more flexible approach for computer identification (basically, you have to provide it on your own) and you can add a custom payload to licenses, which is something i need best, Ricard On Mon, Jun 14, 2021 at 4:27 PM Arnaud Botella ***@***.***> wrote: > @ricardborras <https://github.com/ricardborras> Can you tell which other > library are you using? > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > < #124 (comment) >, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/ACNRYLJVPA3BOKYS27FRZZLTSYGWHANCNFSM46KKWHJA > > . > -- *Ricard Borràs Navarra* Linkedin: http://www.linkedin.com/in/ricardborras Twitter: https://twitter.com/RicardBorras — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#124 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAIR3A5RC3IWIZOOAIQM6T3TSYHGBANCNFSM46KKWHJA> .