> In this case, the checkConfiguration() function should depend on a new private/public key pair, which btw. is weird to begin with. I mean, why do you need a new key if you want to do operations with an existing key pair?

We introduced this check to see if the basic configuration is set up correctly before starting to generate keys, etc. But we could improve the check a bit by first checking if a private/public key already exists. If yes everything should be fine and we can skip the openssl_pkey_new() test. This should avoid to execute this operation on every log-in... @ringmaster can you change this in your branch?