So, given the latest sabotage* of the Nord Stream gas pipelines in Scandinavia (irrespective of who dunnit) we are reminded about dependency on Internet connections.
My question is - located in Sweden, what if the Atlantic cables to US/WA are cut off (a matter of time?), will Rhino register and accept locally entered lic.keys indefinitely without going dead locked due to “polling home” being blocked?
If so, I request a new version R7 which doesn’t call home.
Locally entered license keys do not “phone home”. Cloud based licenses do verify with the online license server, you would have up to two weeks of “offline” use were something to happen. There is quite a bit of redundancy as far as I understand, so things might slow down drastically, but maybe not be cut off entirely. However, if you are worried about such an eventuality, I suggest you pull your licenses out of the Cloud Zoo now (if they are there) and install them locally. Of course, they will no longer be shareable.
Otherwise, maybe give Elon a call and set something up with Starlink…
Yes and no. In Options>Licenses, you can click on “Change License” then “Remove license”. In principle this will remove the license from the machine so that you can install it on a different one. However, it also needs to tell the server that the license has been removed so it’s OK to re-validate it on another machine. If the server is not available this will not work and the license will not work on the new machine.
Well I guess this is the part I wanted to ensure that wouldn’t happen. The only way to ensure it doesn’t happen (i.e. allowing transfer to another machine) is to make sure the software validates the license key on its own.
The Cloud Zoo uses a combination of globally distributed Microsoft Azure and Amazon S3 server resources, and the license database on our servers.
It would take a general “Global” disruption of the Internet to bring it all down.
Not true. It depends where its cut. Cut it mid ocean, then you’re right. Cut it nearby and I’d be in the dark (I’m not supposed to give very much details on exactly where, and how near, but you get the idea).
Well, that would be somewhat difficult to do securely. Rhino would have to have some sort of security module built-in that could generate a key when the license is removed - that a Rhino installation on another machine could read to re-vaildate the license. Probably do-able (I’m no security expert), but with what expense and why really? If it’s “security at any cost”, well, then make sure you have a locally installed licence on every machine you need. Plus of course the power sources to run them, as well as a reason that you would absolutely need to run Rhino when the world is crashing down around your ears…
Just trying to be realist here, if things really go south (or north or east or whatever), having a working Rhino license is going to be the least of our worries…
We do have 2 different Floating license managers, Cloud Zoo (requires occasional Internet), and LAN Zoo, that operates locally on your LAN behind your firewall. https://www.rhino3d.com/features/administration/licensing/
