I guess, this requires knowing GUID, which makes hijacking harder.
Can a TF license be hijacked?
I have a question about how hard it is to hijack a connection to a TF license server.Suppose somebody has a TFS's IP:port info + the .dat file. It seems that then it would be possible to connect to that server and hijack any number of unused licenses. Note that the .dat file can be obtained if a company that distributes the app also puts out a trial version, which contains the .dat.I suppose that creating a different product for TF licenses will make it harder to obtain the .dat file (as it will be different from trial versions), but I'd like to avoid creating a different product for TF licenses, if possible. And this product trick doesn't prevent hijacking - only makes it slightly less likely.
No, a license lease from your product version cannot be hijacked from another product version. It has more to do with the different private keys the license leases are signed with than anything else.
An end-user can prevent their instance of the TurboFloat Server from giving leases to people outside their company that are using your program by limiting who can access the TFS (namely, limit it to in-company connections, VPN connections, or specific IP addresses or ranges).
I mean: knowing the IP:Port of the server, GUID, and TurboFloat.dat one can connect to somebody else's license server and thus hijack a connection.The only thing here that is a bit harder to obtain is GUID.Yes, in an intranet environment you can filter out outside connections, but not clear it is easy in a cloud (eg AWS) environment.
Separate apps that use TurboFloat Server cannot steal license leases from a TurboFloat Server for your particular product version in LimeLM. Its just how its designed (its more about public/private cryptography than Version GUIDs or anything else)