starred/Standard.Licensing
1
0
Fork 0
mirror of https://github.com/junian/Standard.Licensing.git synced 2026-04-25 05:45:51 +03:00
Code Issues 24 Projects Releases Packages Wiki Activity

[GH-ISSUE #13] use license key instead of file #12

New issue
Open
opened 2026-02-26 01:35:46 +03:00 by kerem · 2 comments
kerem commented 2026-02-26 01:35:46 +03:00
Owner
Copy link

Originally created by @furesoft on GitHub (Jan 30, 2020).
Original GitHub issue: https://github.com/junian/Standard.Licensing/issues/13

is it possible to use a licence key in this format instead of a file?
xxxx-xxx-xxxx-xxxx-xxx

Originally created by @furesoft on GitHub (Jan 30, 2020). Original GitHub issue: https://github.com/junian/Standard.Licensing/issues/13 is it possible to use a licence key in this format instead of a file? xxxx-xxx-xxxx-xxxx-xxx
kerem commented 2026-02-26 01:35:46 +03:00
Author
Owner
Copy link

@dataweasel commented on GitHub (May 21, 2022):

I know this is kind of old...but for anyone else who might wonder...

What I did for this was simply to encrypt the license with AES. Created an application-specific Salt string that is used when encrypting the license. It's too long to expect a customer to type it in, but it can be sent in an email, then copy-n-pasted.

<!-- gh-comment-id:1133666472 --> @dataweasel commented on GitHub (May 21, 2022): I know this is kind of old...but for anyone else who might wonder... What I did for this was simply to encrypt the license with AES. Created an application-specific Salt string that is used when encrypting the license. It's too long to expect a customer to type it in, but it can be sent in an email, then copy-n-pasted.
kerem commented 2026-02-26 01:35:46 +03:00
Author
Owner
Copy link

@CraigRichards commented on GitHub (Oct 8, 2022):

I know this is kind of old...but for anyone else who might wonder...

What I did for this was simply to encrypt the license with AES. Created an application-specific Salt string that is used when encrypting the license. It's too long to expect a customer to type it in, but it can be sent in an email, then copy-n-pasted.

This sounds interesting.
Do you have a sample of this?

<!-- gh-comment-id:1272227292 --> @CraigRichards commented on GitHub (Oct 8, 2022): > I know this is kind of old...but for anyone else who might wonder... > > What I did for this was simply to encrypt the license with AES. Created an application-specific Salt string that is used when encrypting the license. It's too long to expect a customer to type it in, but it can be sent in an email, then copy-n-pasted. This sounds interesting. Do you have a sample of this?
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
v1.2.2
v1.2.1
v1.1.9
v1.1.7
v1.1.6
v1.1.5
Labels
Clear labels   
pull-request

Mirrored from GitHub Pull Request

No labels
pull-request
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Standard.Licensing#12
No description provided.