docs/fixtures
HuKeping e77db8a308 [PATCH 1/4] Use seperate databases for notary server and signer
For security, server should not be able to access the `private_key` table
and we can go further more, say, use seperate databases for the server
and signer.

This patch creates two users corresponding to the different databases.

Signed-off-by: Hu Keping <hukeping@huawei.com>
2016-01-29 10:10:25 +08:00
..
compatibility Test import/export of old repo format. 2015-12-23 11:47:37 -08:00
intermediate-ca.crt Reissued all certs with correct SANs 2015-07-15 21:42:24 -07:00
notary-server.crt Reissued all certs with correct SANs 2015-07-15 21:42:24 -07:00
notary-server.key Reissued all certs with correct SANs 2015-07-15 21:42:24 -07:00
notary-signer.crt Reissued all certs with correct SANs 2015-07-15 21:42:24 -07:00
notary-signer.key Reissued all certs with correct SANs 2015-07-15 21:42:24 -07:00
root-ca.crt Reissued all certs with correct SANs 2015-07-15 21:42:24 -07:00
secure.example.com.crt Reissued all certs with correct SANs 2015-07-15 21:42:24 -07:00
secure.example.com.key Reissued all certs with correct SANs 2015-07-15 21:42:24 -07:00
self-signed_docker.com-notary.crt Added basic tests for ValidateRoot 2015-07-17 14:33:05 -07:00
self-signed_secure.example.com.crt Fixed bug in Root Validation and added more test 2015-07-17 14:33:05 -07:00
server-config-local.json Add some standalone (does not require MySQL) configuration files for 2015-11-30 14:14:16 -08:00
server-config.json [PATCH 1/4] Use seperate databases for notary server and signer 2016-01-29 10:10:25 +08:00
signer-config-local.json Add some standalone (does not require MySQL) configuration files for 2015-11-30 14:14:16 -08:00
signer-config.json [PATCH 1/4] Use seperate databases for notary server and signer 2016-01-29 10:10:25 +08:00