undefined | Better HN

0 pointsnly4y ago0 comments

I'm curious how this works at the technical level.

The license key presumable encodes both an expiry date and what version numbers it is valid for when it was issued (and therefore will continue to work for even after expiry)?

0 comments

ben-schaaf4y ago

Licenses encode an issue date and builds have a build date.

nlyOP4y ago

Of course!

J_tt4y ago

I'm assuming there's just a licensing server keeping track of each license key and it's purchase date along with each versions release date.

I don't see any need for encoding this data within the license key

nlyOP4y ago

I don't think it communicates back to them when used.

j / k navigate · click thread line to collapse

0 pointsnly4y ago0 comments

I'm curious how this works at the technical level.

The license key presumable encodes both an expiry date and what version numbers it is valid for when it was issued (and therefore will continue to work for even after expiry)?

0 comments

ben-schaaf4y ago

Licenses encode an issue date and builds have a build date.

nlyOP4y ago

Of course!

J_tt4y ago

I'm assuming there's just a licensing server keeping track of each license key and it's purchase date along with each versions release date.

I don't see any need for encoding this data within the license key

nlyOP4y ago

I don't think it communicates back to them when used.

j / k navigate · click thread line to collapse