scripts/ssl_mgmt/tests/ssl_mgmt.conf

testDir=${0%/*}/tests

workDir=$testDir/workdir

csrSubdir=csr

certSubdir=newcerts

keySubdir=newkeys

# relative to workdir
destDir=../destdir

certDestDir=$destDir/certs

keyDestDir=$destDir/private

opensslCnfFile=openssl.cnf

rootCAPwdPath=./root_ca

managedCerts=./managed_certs

notifiedUsers=nobody
Add simple test infrastructure 2014-05-03 12:12:11 +02:00			`testDir=${0%/*}/tests`
[ssl_mgmt] Add automated testsuite 2014-05-11 06:09:55 +02:00
Add simple test infrastructure 2014-05-03 12:12:11 +02:00			`workDir=$testDir/workdir`
[ssl_mgmt] Add automated testsuite 2014-05-11 06:09:55 +02:00
			`csrSubdir=csr`

			`certSubdir=newcerts`

			`keySubdir=newkeys`

			`# relative to workdir`
			`destDir=../destdir`

Add simple test infrastructure 2014-05-03 12:12:11 +02:00			`certDestDir=$destDir/certs`
[ssl_mgmt] Add automated testsuite 2014-05-11 06:09:55 +02:00
Add simple test infrastructure 2014-05-03 12:12:11 +02:00			`keyDestDir=$destDir/private`
[ssl_mgmt] Add automated testsuite 2014-05-11 06:09:55 +02:00
Add simple test infrastructure 2014-05-03 12:12:11 +02:00			`opensslCnfFile=openssl.cnf`
[ssl_mgmt] Add automated testsuite 2014-05-11 06:09:55 +02:00
			`rootCAPwdPath=./root_ca`

			`managedCerts=./managed_certs`

[ssl_mgmt] Use nobody to test email nobody should be present on most (all?) unix system and is thus better for test. However it's still not ideal as it might be connected to an account that is not the one running the testsuite and the mail might surprise that user. 2014-05-19 15:11:28 +02:00			`notifiedUsers=nobody`