wm: doc

Info  •  Files  •  Log  •  Branches

Add example.com.key to factotum and set the role to client

--- a/acmed.ms

+++ b/acmed.ms

@@ -10,21 +10,22 @@

 cpu% auth/rsa2jwk username@example.com.key > /sys/lib/tls/acmed/username@example.com.pub

-We store our private key into secstore, then factotum:

+We next generate a private key for the host, and set the proper file permissions,

+and copy it into /sys/lib/tls/acmed/:

+cpu% auth/rsagen -t 'service=tls role=client owner=*' > example.com.key

+cpu% chmod 600 username@example.com.key example.com.key 

+cpu% cp username@example.com.key example.com.key /sys/lib/tls/acmed/

+

+We store our keys into secstore, then factotum:

+

 cpu% auth/secstore -g factotum

 secstore password:

 cpu% cat username@example.com.key >> factotum

+cpu% cat example.com.key >> factotum

 cpu% auth/secstore -v -p factotum

 secstore password:

 cpu% read -m factotum > /mnt/factotum/ctl

-

-We next generate a private key for the host, and set the proper file permissions,

-and copy it into /sys/lib/tls/acmed/:

-

-cpu% auth/rsagen -t 'service=tls owner=*' > example.com.key

-cpu% chmod 600 username@example.com.key example.com.key 

-cpu% cp username@example.com.key example.com.key /sys/lib/tls/acmed/

 We generate a certificate signing request, then create the .well-known/acme-challenge

 directory, then pass the CSR to acmed: