Thanks for the prompt reply!
As for now, the current running version (1.61.5), doesn't honor the existing secp384r1 key, and generates a new 4096 key.
I'll keep you posted, when the version is installed!
Same here! Initial certificate is a EC-384, as requests via the WebGui of DirectAdmin, but after 60 days, the renewal falls back to RSA-4096.
Cannot find the file /usr/local/directadmin/data/users/username/domains/domain.tld.san_config, but the script should create it if it's missing. Ingoring...
I really have no clue. Wasn't that possible in the past? After running DirectAdmin for years now..
I've delete the IPv6 address and found a "new option" called "Linked IP". Now everything works fine :)
But still, we could add a extra check ;)
See attached image; The date should represent "26-06-2019, 06:57:07" instead of "177-06-2019, 06:57:07"
This happens on multiple page, for example: "My messages"
Cheers!
https://directadminfqdn.tld:2222/admin/dns/domain.tld/security
On this page you could press the button "Generate keys"
After this, the following page will be shown:
A refresh shows again this page:
Also the domain.tld.db.signed domain.tld.ksk.key domain.tld.ksk.private domain.tld.zsk.key...
When a user doesn't have the Tow Factor enabled, the user isn't able to create a new secret.
directadmin.conf: login_keys=1
Admin-level: login_keys=ON
Reseller-level: login_keys=ON
User-level: login_keys=ON
Reseller-package: login_keys=ON
User-package: login_keys=ON