Synchronet v3.19b-Win32 (install) has been released (Jan-2022).

You can donate to the Synchronet project using PayPal.

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
module:letsyncrypt [2018/02/24 00:58] – Capitalization deucemodule:letsyncrypt [2019/12/07 15:12] – Added more clarifications regarding letsyncrypt.ini and moved stuff around. digital man
Line 1: Line 1:
 ====== LetSyncrypt ====== ====== LetSyncrypt ======
  
-LetSyncrypt is a Let's Encrypt client for Synchronet which uses the ACMEv2 protocol.+LetSyncrypt is a [[https://letsencrypt.org/|Let's Encrypt]] client for Synchronet which uses the ACMEv2 protocol.
  
-===== Setup =====+===== Install =====
  
 LetSyncrypt should be added as a timed event. LetSyncrypt should be added as a timed event.
Line 26: Line 26:
 </file> </file>
  
-If you have multiple domain names, you can have LetSyncrypt put them all in a single certificate, even if you have virtual hosts.  Edit the ''[[dir:ctrl]]/letsyncrypt.ini'' file and add a [Domains] section where the key is the hostname, and the value is the web root for that domain:+===== Configure =====
  
-<file>+LetSyncrypt is configured via the ''[[dir:ctrl]]/[[http://cvs.synchro.net/cgi-bin/viewcvs.cgi/ctrl/letsyncrypt.ini|letsyncrypt.ini]]'' file. 
 + 
 +You must indicate that you agree to the Let's Encrypt Terms of Service by setting ''TOSAgreed = true'' in this file. 
 + 
 +You can specify the ACMEv2 endpoint using the ''Host'' and ''Directory'' keys in the [[config:ini_files#root_section|root section]] of this file.  ''Host'' is the domain name of the ACMEv2 endpoint, and ''Directory'' is appended to it to generate the URL that is fetched for the Directory object.   
 + 
 +<file ini> 
 +Host = acme-v02.api.letsencrypt.org 
 +Directory = /directory 
 +TOSAgreed = true 
 +GroupReadableKeyFile = false 
 +</file> 
 + 
 +Note that without setting ''TOSAgreed = true'', you will likely never get a certificate, but the first few words in this file at present are "This Subscriber Agreement (“Agreement”) is a legally binding contract". 
 + 
 +Do not modify the ''[State]'' or ''[key_id]'' sections of this file. 
 + 
 +==== Domains ==== 
 + 
 +If you have multiple domain names, you can have LetSyncrypt put them all in a single certificate, even if you have virtual hosts.  Edit the ''[[dir:ctrl]]/letsyncrypt.ini'' file and add a ''[Domains]'' section (if it doesn't already exist) and a key for each hostname with the value of the web root for that domain: 
 + 
 +<file ini>
 [Domains] [Domains]
-nix.synchro.net=/sbbs/web/root +nix.synchro.net = /sbbs/web/root 
-home.bbsdev.net=/sbbs/web/root +home.bbsdev.net = /sbbs/web/root 
-gallery.bbsdev.net=/sbbs/web/root/gallery.bbsdev.net +gallery.bbsdev.net = /sbbs/web/root/gallery.bbsdev.net 
-pics.bbsdev.net=/sbbs/web/root/pics.bbsdev.net+pics.bbsdev.net = /sbbs/web/root/pics.bbsdev.net
 </file> </file>
  
-This example has four domains (nix.synchro.net, home.bbsdev.net, gallery.bbsdev.net, and pics.bbsdev.net).  The last two are virtual hosts, so have their web root as a subdirectory of the main web root.+This example has four domains (nix.synchro.net, home.bbsdev.net, gallery.bbsdev.net, and pics.bbsdev.net).  The last two are virtual hosts, so have their web root as a subdirectory of the main [[server:web]] root. 
 + 
 +===== Running Manually ===== 
 + 
 +You can also run the LetSyncrypt script using [[util:jsexec]].  It accepts a number of arguments: 
 + 
 +''%%--new-key%%'' Changes the account key
  
-Do not modify any other sections of this file.+''%%--force%%'' Forces a certificate renewal, ignoring the expiration date of the current certificate.
  
-===== Important Caveat =====+''%%--revoke%%'' Revokes the current certificate, then obtains a new one.
  
-At present (February 24, 2018), Let's Encrypt does not support ACMEv2 for trusted certificates.  The server is expected to go live on February 27, 2018.  On that date, letsyncrypt.js will be updated to use the newly announced server (likely acme-v02.api.letsencrypt.org).  Until then, installed certificates will not be trusted, being issued by the staging server, signed by “Fake LE Intermediate X1”.+''%%--tos%%'' Prints the URL for the Terms of Service.
  
 ===== See Also ===== ===== See Also =====
-  * [[:module:|module index]]+  * [[:module:|Modules]]
  
-{{tag>}}+{{tag>tls ssl cert https crypt}}
  

Trace: