i issued and installed ecdsa cert first for example domain.com, then --force reissued at 09:30 time for rsa but the private is untouched and remains ECC based ?
see timestamps
ls -lah /root/.acme.sh/domain.com/
total 36K
drwxr-xr-x 2 root root 4.0K May 25 09:30 .
drwx------ 5 root root 4.0K May 25 07:44 ..
-rw-r--r-- 1 root root 1.7K May 25 09:30 ca.cer
-rw-r--r-- 1 root root 1.5K May 25 09:30 domain.com.cer
-rw-r--r-- 1 root root 596 May 25 09:30 domain.com.conf
-rw-r--r-- 1 root root 371 May 25 09:30 domain.com.csr
-rw-r--r-- 1 root root 302 May 25 07:42 domain.com.key
-rw-r--r-- 1 root root 79 May 25 09:30 domain.com.ssl.conf
-rw-r--r-- 1 root root 3.2K May 25 09:30 fullchain.cer
domain.com.key checked for BEGIN EC PRIVATE KEY to confirm
acme.sh -v
https://github.com/Neilpang/acme.sh
v2.2.5
ok seems this works
--createDomainKey... until you want to renew.
@heldchen ah yes that would be problematic unless i script the renewal myself with these steps instead of relying on acme.sh client for renewal
if you're going to script it rather use two separate acme.sh installations on the same server and use one for ECC and the other for RSA. but I still feel like that should be a feature within the acme.sh script (see #74)
Hi, @centminmod @heldchen
# Issue the RSA cert.
acme.sh --issue -d aa.com -d www.aa.com ...........
#Then issue a ECC cert.
acme.sh --issue --keylength ec-256 -d ecc.aa.com -d aa.com -d www.aa.com .......
If you don't like the domain ecc.aa.com , you can do it like :
acme.sh --issue --keylength ec-256 -d www.aa.com -d aa.com .......
Then the 2 certs will be in 2 different directories, and will be renewed automatically without any problems.
so happy that acme.sh is bash shell based as I can contribute and follow the code unlike python LOL
still working on integrating acme.sh into my centminmod.com LEMP stack install's nginx vhost generator - 1st manual attempt at dual ssl certs https://community.centminmod.com/dualsslcerts :)
the workaround with having different primary domain is nice too !
thinking of the top of my head, maybe do it this way
domain.com-ecc.key but not the ecc certificatedomain.com-ecc.key exists and use that to issue the ecdsa cert instead of the rsa domain.com.key so it remains untouched and have the issued files with suffix of -ecc or in a separate subdirectory for the domain saved files or just duplicate the --issue routines for a new flag --issue-dualcerts and have that new routine auto generate both rsa and ecc certs with additional keylength options like 2048-ecc256, 2048-ecc384, 4096-ecc256, 4096-ecc384 for rsa and ecdsa so that --issue-dualcerts saves the rsa and ecc cert files with different names and/or directories
my suggestion would be: if ecc is used, add the suffix "-ecc" to the domain directory, but keep the rest the same.
@heldchen Sounds good.
@Neilpang I am using this kind of solution but I don't think it sounds good.
My idea is use file name example.com.key for RSA keys and example.com.ecc.key for ECC keys.
addition:
fullchain.cer for RSA, fullchain.ecc.cerfor ECC.
aa.com.cer for RSA, aa.com.ecc.cer for ECC.
@wangqiliang
Fixed https://github.com/Neilpang/acme.sh/issues/74