Timeline for Implement server serial key for server software
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 13, 2013 at 20:17 | comment | added | Bob Watson | You might find en.m.wikipedia.org/wiki/… useful. Actual implementation may be a question for Server Fault or Stack Overflow. | |
| Feb 13, 2013 at 12:52 | comment | added | Deele | Can you give at least some URL to information about your suggested methods? | |
| Feb 13, 2013 at 11:38 | comment | added | Bob Watson | Edited to reflect the additional information. | |
| Feb 13, 2013 at 11:37 | history | edited | Bob Watson | CC BY-SA 3.0 |
deleted 178 characters in body
|
| Feb 13, 2013 at 11:29 | history | edited | Bob Watson | CC BY-SA 3.0 |
added 4 characters in body
|
| Feb 13, 2013 at 11:22 | comment | added | Bob Watson | The second half is accurate in that case - consider some sort of call-home DRM or distribution via a marketplace? You could even set up a CA and have the client check the server cert against it, then you can revoke it if there's trouble. | |
| Feb 13, 2013 at 11:09 | comment | added | Deele | I think I forgot to mention, that we are not distributing any code, server is compiled C++. | |
| Feb 13, 2013 at 10:35 | history | answered | Bob Watson | CC BY-SA 3.0 |