blob: 5cb1237ce778c0cbd2a113e1192fcd8453a5a0a0 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
|
#! /bin/sh
# Normally, you don't need to regenerate the private key.
#
# openssl genrsa 4096 > key.pem
openssl req -x509 -new -key key.pem -days 1825 -config default-openssl.cnf > \
default-cert.pem
cat default-cert.pem | openssl x509 -sha256 -noout -fingerprint | \
sed -n 's/^SHA256 Fingerprint=\(.*\)$/\1/p' >default-cert-fp
openssl req -x509 -new -key key.pem -days 1825 -config mismatch-openssl.cnf > \
mismatch-cert.pem
openssl req -x509 -new -key key.pem -days 1825 -config noemail-openssl.cnf > \
noemail-cert.pem
openssl req -x509 -new -key key.pem -days 1825 \
-config subdomain-openssl.cnf > subdomain-cert.pem
openssl req -x509 -new -key key.pem -days 1825 -config self-openssl.cnf > \
self-cert.pem
openssl req -x509 -new -key key.pem -days 1825 -config self-any-openssl.cnf > \
self-any-cert.pem
# Normally, you have no reason to regenerate expired-cert.pem, as need to keep
# it expired for the testing purposes. But if you do, copy expired-cert.pem
# content to the certificate value of the following manifest files:
# ../rep-auth/expired/repositories
#
# To regenerate the packages and signature manifest files run bpkg rep-create
# command, for example:
#
# ../../bpkg/bpkg rep-create ../rep-auth/expired --key key.pem
#
# We cannot do it in the testscript since the certificate has expired. This is
# also the reason why we store these auto-generated manifests in git.
#
# Will have to wait 1 day until the certificate expires. Until then testscript
# will be failing.
#
# openssl req -x509 -new -key key.pem -days 1 -config default-openssl.cnf > \
# expired-cert.pem
|
