This is a first in a series of PR's that will transform the way emmy clients and emmy server deal with configuration (crypto parameters, or client/server-specific options).
The purpose of this PR is to remove loading default configuration where it is not needed. For instance, in crypto/zkp/primitives/dlogproofs tests, shcnorr group can be generated on-the-fly, since we don't share the parameters between entities (clients and server) for extended periods of time.
Furthermore, so far client and server code was loading different schonrr groups for demonstration of different protocols/schemes (pedersen, schnorr and pseudonymsys). I think this redundancy complicates configuration handling by both client and the server, and is not needed. This is why clients and server now use a simplified version of the function for loading schnorr group, config.LoadSchnorrGroup().
This is a first in a series of PR's that will transform the way emmy clients and emmy server deal with configuration (crypto parameters, or client/server-specific options).
The purpose of this PR is to remove loading default configuration where it is not needed. For instance, in
crypto/zkp/primitives/dlogproofstests, shcnorr group can be generated on-the-fly, since we don't share the parameters between entities (clients and server) for extended periods of time.Furthermore, so far client and server code was loading different schonrr groups for demonstration of different protocols/schemes (pedersen, schnorr and pseudonymsys). I think this redundancy complicates configuration handling by both client and the server, and is not needed. This is why clients and server now use a simplified version of the function for loading schnorr group,
config.LoadSchnorrGroup().