Mensaje archivado #1052 de la Lista ecs-isp@2rosenthals.com

De:	"Peter Moylan" <ecs-isp@2rosenthals.com>	Encabezados Completos Mensaje no decodificado
Asunto:	Re: [eCS-ISP] Getting started with Let's Encrypt
Fecha:	Sat, 7 Dec 2024 13:28:00 +1100
Para:	eCS ISP Mailing List <ecs-isp@2rosenthals.com>

On 07/12/24 06:45, Massimo S. wrote: https://smedley.id.au/tmp/uacme-1.2.4-os2-20240817.zip https://smedley.id.au/tmp/uacme-1.0.19-os2-20240813.zip personally i still prefere/use 1.0.19 i've found some issues with 1.2.4 Thanks. I've downloaded both, so I can test with both. since the website market, at least here in Italy, is nowadays allmost gone it happens to have one new website/client per year so it's not an issue for me to create a new one when i develop a new website the only difference it's that i need to write the webhosting path directly into each single hook script but i guess that for you "my solution" is simpler since you have to manage just one certificate, maybe two.. Yes, in one way. I only have one server machine, with a single external IP address, so all domains that I host will have to go on the same certificate. (Unless I have missed seeing some detail, there is no way to know which domain is being addressed until the TLS negotiation is finished.) On the other hand, WebServe is my product, and it uses my implementation of TLS, so I need to be in a position to field questions about configuring it, and scripts that don't need too much customisation are better for that. -- Peter Moylan peter@pmoylan.org http://www.pmoylan.org

Suscribirse: Todos, Compendio, Indice.
Desuscribirse
Correo al dueño de la Lista