From 7670e1aae4761ef97018d891e10a9c625238fe62 Mon Sep 17 00:00:00 2001
From: =?utf8?q?Felix=20D=C3=B6rre?= <felix@dogcraft.de>
Date: Thu, 5 Oct 2017 18:43:15 +0200
Subject: [PATCH] upd: enhance "generateTruststoreNRE"-script to generate
 gigi-keys

... for development

Change-Id: I1ebb0c157fb6bcca8a83e27037b9f26c7d707019
---
 config/generateTruststoreNRE.sh | 38 ++++++++++++++++++++++++++++++---
 1 file changed, 35 insertions(+), 3 deletions(-)

diff --git a/config/generateTruststoreNRE.sh b/config/generateTruststoreNRE.sh
index fa2408d0..fbc5e6ed 100755
--- a/config/generateTruststoreNRE.sh
+++ b/config/generateTruststoreNRE.sh
@@ -1,5 +1,7 @@
 #!/bin/bash
 # this script imports the root certs into a Java key store
+# additionally it can generate the certs for gigi, if none are provided and the CA-keys are available in the config folder for the Simple Signer
+# This script is generally only intended for development purposes.
 
 rm -f cacerts.jks
 
@@ -23,8 +25,38 @@ for i in ca/*_*_*; do
   import ${i%.crt}
 done
 
-for i in ../keys/*.pkcs12; do
-  importP $i
-done
+# Generate Gigi certificates manually
+cabasename=assured
+caname=${cabasename}_$(date +%Y)_1
+ca=../signer/ca/$caname/ca
+if [[ -f "$ca.key" ]] && ! [[ -f keystore.pkcs12 ]]; then
+    # when the domain is provided externally as environment variable, use it and do not prompt for it.
+    [[ -z $DOMAIN ]] && read -rp "I need to generate gigi-certificates. I need your base domain: " DOMAIN
+    # Assuming we have access to the CA-keys we generate two certificates and present them to gigi
+    # One to be used for all 4 https domains and one as email certificate.
+
+    # Generate two keys and certs requests. The CN of the SSL-server cert doesn't really matter, as we use subject alt names anyways.
+    openssl req -newkey rsa:2048 -keyout www.key -out www.csr -nodes -subj "/CN=gigi server certificate"
+    openssl req -newkey rsa:2048 -keyout mail.key -out mail.csr -nodes -subj "/CN=gigi system"
+
+    # Sign the two requests with the keys in the config of the simple signer. Use serials 1000001 and 1000002 to probably not collide with the "simple signer"
+    openssl x509 -req -in www.csr -out www.crt -CA $ca.crt -CAkey $ca.key -set_serial 1000001 -extfile <(printf "[ext]\nsubjectAltName=DNS:www.$DOMAIN,DNS:secure.$DOMAIN,DNS:static.$DOMAIN,DNS:api.$DOMAIN\nbasicConstraints=CA:FALSE\nextendedKeyUsage=serverAuth\nkeyUsage=digitalSignature,keyEncipherment\n") -extensions ext
+    openssl x509 -req -in mail.csr -out mail.crt -CA $ca.crt -CAkey $ca.key -set_serial 1000002 -extfile <(printf "[ext]\nsubjectAltName=email:support@$DOMAIN\nbasicConstraints=CA:FALSE\nextendedKeyUsage=emailProtection\nkeyUsage=digitalSignature,keyEncipherment\n") -extensions ext
 
+    # Store the webserver cert in 4 different pkcs12-keystores to have different "key aliases" and import them all into the "keystore.pkcs12" using the "importP"-method
+    for t in www api secure static; do
+        # concatenate private key and certificate chain together
+        # and filter out comments from .crt files with "openssl x509"
+        # before feeding them into "openssl pkcs12"
+        cat www.key www.crt ca/$caname.crt ca/$cabasename.crt ca/root.crt |\
+            (openssl pkey; for i in {1..4}; do openssl x509; done) |\
+            openssl pkcs12 -export -out $t.pkcs12 -name "$t" -passout pass:changeit
+        importP "$t.pkcs12"
+    done
+    # and finally add the mail certificate
+    cat mail.key mail.crt ca/$caname.crt ca/$cabasename.crt ca/root.crt |\
+        (openssl pkey; for i in {1..4}; do openssl x509; done) |\
+        openssl pkcs12 -export -out mail.pkcs12 -name "mail" -passout pass:changeit
+    importP "mail.pkcs12"
+fi
 keytool -list -keystore ../config/cacerts.jks -storepass "changeit"
-- 
2.39.2