https://github.com/WolfWings/wdfcert.sh

Let's Encrypt bash client focused around joker.com and 384-bit ECDSA support
https://github.com/WolfWings/wdfcert.sh

Last synced: 9 days ago
JSON representation

Let's Encrypt bash client focused around joker.com and 384-bit ECDSA support

• Host: GitHub
• URL: https://github.com/WolfWings/wdfcert.sh
• Owner: WolfWings
• License: isc
• Created: 2021-04-23T12:58:21.000Z (over 3 years ago)
• Default Branch: master
• Last Pushed: 2021-05-01T05:21:45.000Z (over 3 years ago)
• Last Synced: 2024-08-01T13:38:11.654Z (3 months ago)
• Language: Shell
• Size: 36.1 KB
• Stars: 10
• Watchers: 3
• Forks: 2
• Open Issues: 1
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# wdfcert.sh

This script came about due to the poor support for automating

Let's Encrypt for the common use case of a root + wildcard

certificate if using the "Joker" registrar's built-in DNS services.

It was expanded upon as even for the few tools that worked with

that provider none of them supported modern ECDSA account keys

and few if any supported ECDSA certificate generation.

A friend read the script after I was finished writing it and

showed them a copy, and suggested I publish it on github as

others may both find it useful to learn how Let's Encrypt works

or may be in a similar situation I was in.

Most of the documentation is in the wdfcert script itself.

Finally: Why wdfcert? It's something I do for 'throwaway' one-off

tools: With the name of Wolf it's a common typographical failure

of various fonts that merges the **ol** into a **d** so

**wolf** -> **wdf**