[Freedombox-discuss] LetsEncrypt - 4096 certificate option
- Subject: [Freedombox-discuss] LetsEncrypt - 4096 certificate option
- From: petrus@miosweb.mooo.com (Pierre L.)
- Date: Sat, 24 Jun 2017 15:01:46 +0200
- Message-id: <[🔎] d51d65e6-e615-f01f-8275-7344dd2fe4b4@miosweb.mooo.com>
- In-reply-to: <94a9f214-3228-949f-1527-2e87229e0a18@autistici.org>
- References: <dba9168e-3cbe-4275-3f6a-66c1765da783@miosweb.mooo.com> <3336900.x04yKRXlAO@bagend> <94a9f214-3228-949f-1527-2e87229e0a18@autistici.org>
Hey!
(sorry for being soooo late about this topic...)
Now I got it working with 4096 certificate generated by modding this
file, as Daddy wrote before (thx to him!) :
Add the command argument as this : '--rsa-key-size', '4096',
You will be able to find/tune this line in this file
/usr/share/plinth/actions/letsencrypt
**Before :
def subcommand_obtain(arguments):
[...]
'letsencrypt', 'certonly', '--text', '--agree-tos',
'--register-unsafely-without-email', '--domain', arguments.domain,
[...]
**After :
def subcommand_obtain(arguments):
[...]
'letsencrypt', 'certonly', '--text', '--agree-tos',
'--rsa-key-size', '4096',
'--register-unsafely-without-email', '--domain', arguments.domain,
[...]
ps: don't forget Sunil's GitHub issue, it's still opened...
https://github.com/freedombox/Plinth/issues/737
Le 13/02/2017 ? 16:13, Daddy a ?crit :
> If that doesn't work, you can look at the way plinth builds the
> command in following file:
> /usr/share/plinth/actions/letsencrypt
> Function subcommand_obtain seems to be responsible for preparation of
> the request and lists the arguments passed.
> Unfortunately, I can't test it, as I get error when requesting
> certificate ("FileNotFoundError: [Errno 2] No such file or directory:
> 'letsencrypt' "; maybe missing dependency).
>
> D.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/freedombox-discuss/attachments/20170624/61bbc59e/attachment.sig>
Reply to: