![]() new_certs_dir = $dir/certs # default place for new certs. tsa_policy1 = 1.2.3.4.1 tsa_policy2 = 1.2.3.4.5.6 tsa_polic圓 = 1.2.3.4.5.7 # default_ca = CA_default # The default ca section dir = $ENV::HOME/tls # Where everything is kept certs = $dir/certs # Where the issued certs are kept database = $dir/index.txt # database index file. # Add a simple OID like this: # testoid1=1.2.3.4 # Or use config file substitution like this: # testoid2=$.5.6 # Policies used by the TSA examples. RANDFILE = $ENV::HOME/.rnd # Extra OBJECT IDENTIFIER info: #oid_file = $ENV::HOME/.oid oid_section = new_oids # To use this configuration file with the "-extfile" option of the # "openssl x509" utility, name here the section containing the # X.509v3 extensions to use: # extensions = # (Alternatively, use a configuration file that has only # X.509v3 extensions in its main section.) # We can add new OIDs in here for use by 'ca', 'req' and 'ts'. # This definition stops the following lines choking if HOME isn't # defined. ![]() # This is mostly being used for generation of certificate requests. Example openssl.cnf # OpenSSL example configuration file. The following files, openssl.cnf and config.yml, should be placed in the same directory where the server is started from. The configuration file holds the definitions for controls, der, end devices and other settings that will be used during the runtime The second is the configuration for the server itself. Key/certs/ca unless -no-create-certs is passed to the server startup method. Each time the server is started up it will attempt to regenerate We shell out to openssl for key/cert/ca generation during runtime. The first is for generation of certificates and keys for the system (openssl.cnf). The server requires two configuration files. # Activate the environment in the current shell source env/bin/activate # creates an environment 'env' in the current directory Create a virtual environment and installĢ030.5 server as follows. The recommended way to install this project from pypi is in a virtual environment. The serverĬan work in both in-band and out-of-band registration models detailed in CCIP Implementation Guide v2 ![]() The GridAPPS-D IEEE 2030.5 Server implements the Common Smart Inverter Profile (CSIP).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |