From now on, all communication between you (the web interface or the client app) is protected with 256 bit encryption (AES 256 and RSA 2048) by default.
If you are using SKGL Extension API, the only thing you have to do is to upgrade to version 188.8.131.52. If you are sending customized requests (from another server or a different platform), you can simply change from http to https.
This change was performed yesterday, and there might have been short disruptions when logging in into SKM, during external key generation, key activation and validation. The secured connection is now working properly, and no more disruptions should occur.
Our goal is to continue improving the security measures in order to ensure that only you are able to access your information. If you want to find out more about the security measures, please see this article:
In the last post, there was a questionnaire about whether or not the access to the “notes” field should be given through key validation or key activation. The results of the questionnaire were mixed.
All opinions are very important for us, so, as a result, the notes field access is implemented in such a way to allow those users that want to access it being able to do so, while those users that don’t want the notes field to be exposed will be able to restrict access to it.
So, if you want to get the notes field exposed, please see this article. If you don’t, there is nothing that has to be done. Simply keep using Serial Key Manager as you’ve always have done!
The recently released version of SKGL Extension API, v. 184.108.40.206, incorporates a new “notes” field in the KeyInformation class. The notes field is saved in the same way as creation date and other serial key features into a file during offline key validation (one time key activation with a digital signature). For those users that decide not to activate notes field access, nothing has to be done either. Serial Key Manager platform will work with 220.127.116.11 as usual.
It would be great if you find this way of implementing the access to the “notes” field is the optimal solution, but it might not be the case. If there is something you don’t like about this change or if you simply want to tell us what you think, you are warmly welcome to contact us!
There is an idea to make the “notes” field accessible by the API and web requests during key validation/activation. Before we can implement this, we have make sure that no one is against such a change. Please submit a short feedback form below:
Two great features are now implemented and accessible by all users of Serial Key Manager (SKM): External key generation and passive key validation.
External key generation
From now on, you can generate new keys with a simple web request without exposing neither the password of a product nor the log in details to your account. Everything is handled by a private key that you can change at any time. This feature can be activated/deactivated at any time also.
This is particularly good if you want to automatize the entire software distribution cycle (app downloaded, evaluated, purchased, activated).
For more information, please read the following article or see the video embedded in the end of this post.
Passive key validation
One of the greatest advantages of SKM is that you can control all apps that are connected to SKM servers. That is, all your changes on the server will instantly reach the client app.
In some cases, however, there is no need to validate keys each time the application starts. You might, for instance, want to validate a key only once or possibly once in a month (or any other interval of time), and, at the same time, be sure that the key information has not been altered.
For more information on how this can be accomplished, please read the following article.
Both of these features were suggested by users of SKM. As I’ve mentioned in the previous posts, all your suggestions are very important to make SKM a great product. In contrast to the early version of SKM, there are now so many new functionality available in SKM. Because of this, all users that registered before the 11th of August have received an extended trial period.
Serial Key Manager is now entirely platform independent! Not only can validation and activation occur on any platform, but even the additional data like set time, features, can be retrieved using a simple web request. This means that no password has to be stored in the application, which drastically improves the security.
Yesterday, Serial Key Manager was updated with a new feature specifically for trial keys.
Ability to create trial keys – Trial activation allows you to create trial keys and/or time limited keys that are activated only when the user first uses the key. This means that you can generate keys several months before you start distributing them and they will still work the amount of time you specified originally.
In addition, because the server tracks each activation, you do not need to store anything on the client computer except for the key itself.
If keys were generated sometime before the time of activation, a new key will replace the old key and is going to be sent back to the user. This can only occur once unless ou have configured the key otherwise.
This feature was suggested by a user of Serial Key Manager some days ago. I encourage all users and visitors of Serial Key Manager to ask questions and suggest new things directly by contacting us. Remember that you can phrase your question in either English, Swedish or Russian. You can use German too but it might take a bit longer for me to process it.
Two main changes were implemented into Serial Key Manager this week. The first one allows you to change the key features and edit its notes, while the second one allows you to adjust machine code locking settings. Both features are platform independent.
The machine code locking feature in Serial Key Manager was taken a step further. Instead of locking a key to a specific machine, you are now able to generate keys that are not bound to any machine from the beginning. However, once a client starts the activation process, you have the ability to either allow automatic activation, which means that the program will send details to the server and return a value, or manually add your client’s machine code to the database. For corporate environments where some computers do not have access to the internet, you can instead create an online interface for clients to activate their license on any computer that has access to the internet (the computer will have to access internet once, but it does not have to activate itself on its own).
Instead of forcing Serial Key Manager users to use a specific hash algorithm, it allows you to pick any function and set up your own method for collecting information that is to be hashed. For .NET users, there is already an open source library that does this in several lines of code (see here), however, since these methods analyse web server requests, serial key validation and activation can occur on any platform and operating system.
At this point, there are two tutorials that cover this topic. The first one is in the form of an article (see here) while the second one is a video tutorial (see here).
Please note that feedback is important to develop Serial Key Manager according to your needs. This feature in particular was suggested by Travis (here). I am very thankful to all users of Serial Key Manager, Software Protector and SKGL for their questions and suggestions. Thanks to all messages, I can shape these individual products to contribute to a more effective serial key management!