Saravanan666/pypi-org huggingface dataset:
Package: certbot-dns-domeneshop
DomeneshopDNS Authenticator plugin forcertbot.This plugin automates the process of completing adns-01challenge by
creating, and subsequently removing, TXT records using theDomeneshop API.Named Arguments--dns-domeneshop-credentialsdomeneshopcredentialsINI file.(required)--dns-domeneshop-propagation-secondsThe number of seconds to wait for DNS to propagate before asking the ACME server to verify the DNS record(Default: 120)Note that for certbot1.6.0and older, a prefix (certbot-dns-domeneshop:) is required in front of the arguments, see the examples below. The prefix is also required in the credentials file.Installationpipinstallcertbot-dns-domeneshopCredentialsUse of this plugin requires a configuration file containing Domeneshop API
credentials.See theDomeneshop APIdocumentation for more information (in Norwegian).An examplecredentials.inifile:dns_domeneshop_client_token=1234567890abcdefdns_domeneshop_client_secret=1234567890abcdefghijklmnopqrstuvxyz1234567890abcdefghijklmnopqrsThe path to this file can be provided interactively or using the--dns-domeneshop-credentialscommand-line argument. Certbot
records the path to this file for use during renewal, but does not store the
file’s contents.CAUTION:You should protect these API credentials as you would the
password to your Domeneshop user account. Users who can read this file can use these
credentials to issue arbitrary API calls on your behalf. Users who can cause
Certbot to run using these credentials can complete adns-01challenge to
acquire new certificates or revoke existing certificates for associated
domains, even if those domains aren’t being managed by this server.If applicable, we suggest that you create API credentials for domains used by your
application, in order to reduce the potential impact of lost credentials.Certbot will emit a warning if it detects that the credentials file can be
accessed by other users on your system. The warning reads “Unsafe permissions
on credentials configuration file”, followed by the path to the credentials
file. This warning will be emitted each time Certbot uses the credentials file,
including for renewal, and cannot be silenced except by addressing the issue
(e.g., by using a command likechmod 600to restrict access to the file).ExamplesTo acquire a single certificate for bothexample.comandwww.example.com, waiting 120 seconds for DNS propagation (the default):certbotcertonly\--authenticatordns-domeneshop\--dns-domeneshop-credentials~/.secrets/certbot/domeneshop.ini\--dns-domeneshop-propagation-seconds120\-dexample.com\-dwww.example.comIf you are using certbot1.6.0or older, you should call the plugin with prefixes the prefix:certbotcertonly\--authenticatorcertbot-dns-domeneshop:dns-domeneshop\--certbot-dns-domeneshop:dns-domeneshop-credentials~/.secrets/certbot/domeneshop.ini\--certbot-dns-domeneshop:dns-domeneshop-propagation-seconds120\-dexample.com\-dwww.example.comIn this second example, make sure you are also adding the prefixes in~/.secrets/certbot/domeneshop.ini(e.g.certbot-dns-domeneshop:dns_domeneshop_client_token``). Certbot will fail to discover your credentials otherwise.
Package: certbot-dns-dynu
certbot-dns-dynuDynu DNS Authenticator plugin forCertbot.This plugin is built from the ground up and follows the development style and life-cycle
of othercertbot-dns-*plugins found in theOfficial Certbot Repository.Installationpip install --upgrade certbot
pip install certbot-dns-dynuVerify:$ certbot plugins --text

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
* dns-dynu
Description: Obtain certificates using a DNS TXT record (if you are using Dynu
for DNS.)
Interfaces: Authenticator, Plugin
Entry point: dns-dynu = certbot_dns_dynu.dns_dynu:Authenticator

...
...ConfigurationThe credentials file e.g.~/dynu-credentials.inishould look like this:dns_dynu_auth_token = AbCbASsd!@34Usagecertbot ... \
        --authenticator dns-dynu  \
        --dns-dynu-credentials ~/dynu-credentials.ini \
        certonlyFAQWhy such long name for a plugin?This follows the upstream nomenclature:certbot-dns-<dns-provider>.Why do I have to use:separator in the name? And why are the configuration file parameters so weird?This is a limitation of the Certbot interface towardsthird-partyplugins.For details read the discussions:https://github.com/certbot/certbot/issues/6504#issuecomment-473462138https://github.com/certbot/certbot/issues/6040https://github.com/certbot/certbot/issues/4351https://github.com/certbot/certbot/pull/6372DevelopmentCreate a virtualenv, install the plugin (editablemode),
spawn the environment and run the test:virtualenv -p python3 .venv
. .venv/bin/activate
pip install -e .
docker-compose up -d
./test/run_certonly.sh test/dynu-credentials.iniLicenseCopyright (c) 2021Bikramjeet SinghCreditsPowerDNSdns-lexiconHelpful linksDNS Plugin listacme.shdynu with acme.shdynu api
Package: certbot-dns-dynu-dev
certbot-dns-dynuDynu DNS Authenticator plugin forCertbot.This plugin is built from the ground up and follows the development style and life-cycle
of othercertbot-dns-*plugins found in theOfficial Certbot Repository.Installationpip install --upgrade certbot
pip install certbot-dns-dynuVerify:$ certbot plugins --text

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
* dns-dynu
Description: Obtain certificates using a DNS TXT record (if you are using Dynu
for DNS.)
Interfaces: Authenticator, Plugin
Entry point: dns-dynu = certbot_dns_dynu.dns_dynu:Authenticator

...
...ConfigurationThe credentials file e.g.~/dynu-credentials.inishould look like this:dns_dynu_auth_token = AbCbASsd!@34Usagecertbot ... \
        --authenticator dns-dynu  \
        --dns-dynu-credentials ~/dynu-credentials.ini \
        certonlyFAQWhy such long name for a plugin?This follows the upstream nomenclature:certbot-dns-<dns-provider>.Why do I have to use:separator in the name? And why are the configuration file parameters so weird?This is a limitation of the Certbot interface towardsthird-partyplugins.For details read the discussions:https://github.com/certbot/certbot/issues/6504#issuecomment-473462138https://github.com/certbot/certbot/issues/6040https://github.com/certbot/certbot/issues/4351https://github.com/certbot/certbot/pull/6372DevelopmentCreate a virtualenv, install the plugin (editablemode),
spawn the environment and run the test:virtualenv -p python3 .venv
. .venv/bin/activate
pip install -e .
docker-compose up -d
./test/run_certonly.sh test/dynu-credentials.iniLicenseCopyright (c) 2021Bikramjeet SinghCreditsPowerDNSdns-lexiconHelpful linksDNS Plugin listacme.shdynu with acme.shdynu api
Package: certbot-dns-exonet
Certbot plugin for authentication using the Exonet DNSCertbotDNS Authenticator plugin forExonet DNSConventionsCode style guide: PEP 8.Docstring conventions: Google Python Style Guide and Markdown.InstallationInstall using pip:pipinstallcertbot-dns-exonetUsageRequest an Exonet API token (contact Exonet)After the installation, verify if the plugin is available in certbot:certbotpluginsCreate an exonet.ini file:touch/etc/letsencrypt/exonet.inichmod0600/etc/letsencrypt/exonet.iniAdd the Exonet API token in /etc/letsencrypt/exonet.ini:dns_exonet_token=YOUR_EXONET_API_TOKENRequest a certificate with certbot and this plugin to obtain a certificate using DNS record authentication:certbotcertonly\--config-dir/etc/letsencrypt\--work-dir/etc/letsencrypt\--logs-dir/etc/letsencrypt\--authenticatordns-exonet\--dns-exonet-credentials/etc/letsencrypt/exonet.ini\-ddomain.comChange logPlease seereleasesfor more information on what has changed recently.SecurityIf you discover any security related issues please emaildevelopment@exonet.nlinstead of using the issue tracker.CreditsExonetAll ContributorsLicenseThe MIT License (MIT). Please seeLicense Filefor more information.
Package: certbot-dns-glesys
GleSYS DNS Authenticator for CertbotThis allows automatic completion ofCertbot’sDNS01 challange for domains managed onGleSYSDNS.InstallingInstallation of Certbot plugins are a bit tricky. The least bad way is to create
a Python virtual environment asrootand install it there.$ cd /root/
$ python3 -m venv --prompt=certbot certbot
$ source certbot/bin/activate
$ pip install --upgrade pip setuptools
$ pip install certbot-dns-glesysYou can now run Certbot using/root/certbot/bin/certbot.If you use Fedora like me I have preparedan RPMyou can use
instead.$ sudo dnf install https://github.com/runfalk/certbot-dns-glesys/releases/download/2.0.0/python3-certbot-dns-glesys-2.0.0-1.fedora33.noarch.rpmIf you use another RPM based distribution you may be able to build it yourself.
On Fedora I installrpmdevtoolsbefore this. Note that this command must not
be run inside a virtualenv (or the installation path will be incorrect). You can
verify the installation path usingrpm -qpl dist/*.rpm.$ ./make_rpm.shPRs are welcome for other distributions.UsageCreate an API key with the following permissions:domain:listdomain:listrecordsdomain:addrecorddomain:deleterecordDon’t forget to give access to the appropriate IP-address range. If you want
to be able to run the client from anywhere, enter0.0.0.0/0.To use the authenticator you need to provide some required options:--dns-glesys-credentials(required)INI file withuserandpasswordfor your GlesSYS API user.The credentials file must have the following format:dns_glesys_user = CL00000
dns_glesys_password = apikeygoeshereFor safety reasons the file must not be world readable. You can solve this by
running:$ chmod 600 credentials.iniThen you can runcertbotusing:$ certbot certonly \
    --authenticator dns-glesys \
    --dns-glesys-credentials credentials.ini \
    -d domain.comIf you want to obtain a wildcard certificate you can use the the domain-d"*.domain.com".DisclaimerThis plugin is neither affiliated with nor endorsed by GleSYS Internet Services
AB.ChangelogVersion 2.1.0Released 21st August 2022Fixed plugin not being detected by newer certbot versions.Version 2.0.0Released 28th December 2020This is a breaking change. The CLI arguments and the name of the package has
changed to match other DNS authenticator plugins.Updated name tocertbot-dns-glesysto match other DNS pluginsMove away from legacy Certbot API (means you need to reconfigure your
authenticator). All arguments and parameters are now prefix-lessDropped Python 2 supportDropped Python 3.5 supportVersion 1.0.0Released 11th April 2020Changed to GleSYS JSON APIAdded RPM as an installation optionDropped support for EOL Python versionsVersion 0.2.0Released on 23rd April 2018This is a breaking change since it requires thedomain:listpermission.Added proper support for sub domain guessing, pull request#4(@Lillecarl)Version 0.1.1Released on 15th March, 2018Bumped default propagation time to 90 seconds to improve reliabilityFixed wrong base url inGlesysDomainApiClient, pull request#2(@montaniasystemab)Version 0.1.0Released on 30th September, 2017Initial release
Package: certbot-dns-google-domains
certbot-dns-google-domainsA Certbot DNS Authenticator forGoogle Domains.Named ArgumentsOptionDescription--authenticator dns-google-domainsSelect this authenticator plugin.--dns-google-domains-credentials FILEPath to the INI file with credentials.--dns-google-domains-propagation-seconds INTHow long to wait for DNS changes to propagate. Default = 30s.--dns-google-domains-zone STRINGWhat the registered domain on Google domains is. Default: Retrieved from either the credentials file, or by using the public suffix list to guess.CredentialsThe credentials file includes the access token for Google Domains.dns_google_domains_access_token = abcdefOptionally, you can also define the zone in this file.dns_google_domains_access_token = abcdef
dns_google_domains_zone = example.comUsage ExampleDocker / Podmandockerrun\-v'/var/lib/letsencrypt:/var/lib/letsencrypt'\-v'/etc/letsencrypt:/etc/letsencrypt'\--cap-drop=all\ghcr.io/aaomidi/certbot-dns-google-domains:latest\certbotcertonly\--authenticator'dns-google-domains'\--dns-google-domains-credentials'/var/lib/letsencrypt/dns_google_domains_credentials.ini'\--server'https://acme-v02.api.letsencrypt.org/directory'\--non-interactive\--dns-google-domains-zone'example.com'\-d'a.example.com'Notes:-v '/var/lib/letsencrypt:/var/lib/letsencrypt'is where certbot by default outputs certificates, keys, and account information.-v '/etc/letsencrypt:/etc/letsencrypt'is where certbot keeps its configuration.--authenticator 'dns-google-domains'uses the dns-google-domains authenticator.--dns-google-domains-credentials '/var/lib/letsencrypt/dns_google_domains_credentials.ini'is the path to the credentials file.--dns-google-domains-zone 'example.com'is the main domain you have registered with Google domains. This is optional.To ensure successful execution, this command requires you to intentionally provide both the --email and --agree-tos arguments. The command does not include them by default, as it is important for users to consciously agree to the terms of service and supply their email address.PythonYou can get thecertbot-dns-google-domainspackage fromPyPi:pip3installcertbotcertbot-dns-google-domains

certbotcertonly\--authenticator'dns-google-domains'\--dns-google-domains-credentials'/var/lib/letsencrypt/dns_google_domains_credentials.ini'\--server'https://acme-v02.api.letsencrypt.org/directory'\--dns-google-domains-zone'example.com'\-d'a.example.com'Note: If you have installed Certbot from a non-pip3 source, the certbot-dns-google-domains plugin might not be compatible with your existing Certbot installation. In this case, consider using pip3 to install Certbot and its plugins to ensure compatibility.Homebrewbrewinstallcertbot$(brew--prefixcertbot)/libexec/bin/pip3installcertbot-dns-google-domainsNotes on Zone ResolutionGoogle Domains does not provide an API to obtain the zone for a domain based on a subdomain. This plugin employs the following logic to determine the zone:If the--dns-google-domains-zoneargument is specified, use that.If the credentials file specifies a zone, use that.Utilize thePublic Suffix Listto determine the zone.
Package: certbot-dns-he
Hurricane Electric DNSAuthenticator plugin forCertbotInstallationInstallcerbot-dns-heto your Certbot’s environment with pip. For example, the line below works for me after runningcertbot-auto.$sudo/opt/eff.org/certbot/venv/bin/pipinstallcerbot-dns-heYou can also usegit+https://github.com/TSaaristo/certbot-dns-he.gitor clone the repository and install from the directory, but pip is recommended.Example usageCreate a configuration file with your username and password:certbot_dns_he:dns_he_user = Mecertbot_dns_he:dns_he_pass = my HE passwordand chmod it to600:$chmod600dns_he.iniThen request a certificate with something like:$certbot-autocertonly\-acertbot-dns-he:dns-he--certbot-dns-he:dns-he-propagation-seconds30\--certbot-dns-he:dns-he-credentials/home/me/dns_he.ini-d'mydomain.com,*.mydomain.com'\--serverhttps://acme-v02.api.letsencrypt.org/directory--agree-tos\--manual-public-ip-logging-ok--preferred-challengesdns-mme@email.comYou’re done!--certbot-dns-he:dns-he-propagation-secondscontrols the duration waited for the DNS record(s) to propagate.--certbot-dns-he:dns-he-credentialsspecifies the configuration file path.These are stored in cerbot’s renewal configuration, so they’ll work on your automatic renewals.
Package: certbot-dns-hetzner
Hetzner DNS Authenticator certbot pluginThis certbot plugin automates the process of
completing a dns-01 challenge by creating, and
subsequently removing, TXT records using the Hetzner DNS API.RequirementsFor certbot < 2Notice that this plugin is only supporting certbot>=2.0 from 2.0 onwards. For older certbot versions use 1.x releases.InstallInstall this package via pip in the same python environment where you installed your certbot.pip install certbot-dns-hetznerUsageTo start using DNS authentication for the Hetzner DNS API, pass the following arguments on certbot's command line:OptionDescription--authenticator dns-hetznerselect the authenticator plugin (Required)--dns-hetzner-credentialsHetzner DNS API credentials INI file. (Required)--dns-hetzner-propagation-secondsSeconds to wait for the TXT record to propagateCredentialsFrom the hetzner DNS control panel athttps://dns.hetzner.comgo to "API Tokens" and add a personal access token.An examplecredentials.inifile:dns_hetzner_api_token=nohnah4zoo9Kiejee9aGh0thoopee2saExamplesTo acquire a certificate forexample.comcertbotcertonly\\--authenticatordns-hetzner\\--dns-hetzner-credentials/path/to/my/hetzner.ini\\-dexample.comTo acquire a certificate for*.example.comcertbotcertonly\\--authenticatordns-hetzner\\--dns-hetzner-credentials/path/to/my/hetzner.ini\\-d'*.example.com'Thanks toOf course certbot, which examples and documentation I used to implement this plugin. And tohttps://github.com/m42e/certbot-dns-ispconfigwhich served as an excellent example and README template as well.
Package: certbot-dns-hotline
certbot-dns-hotlineCertbot DNS plugin for HotlineBased onhttps://github.com/schleuss/certbot_dns_freednsandhttps://github.com/m42e/certbot-dns-ispconfigThis is used in conjunction withHotlinefor issuing SSL certificates for the callback domain.UsageChange the domains to match your callback domain, along with the--dns-hotline-pathto the directory shared with the DNS callback service$ certbot certonly \
    --authenticator dns-hotline \
    --dns-hotline-path /hotline/acme \
    --server https://acme-v02.api.letsencrypt.org/directory \
    --agree-tos \
    --rsa-key-size 4096 \
    -d 'hotlinecallback.net' \
    -d '*.hotlinecallback.net'
Package: certbot-dnshub
Multi dns provider authentication plugin for certbotEnglish |中文Multi dns provider authentication plugin for certbot. It can help you automatically apply and update Let's Encrypt wildcard certificates.Usageyou can use this plugin with docker or pip. We recommend using docker.dockerpullcertbot/certbot
dockerrun-it--rm--namecertbot\-v"/etc/letsencrypt:/etc/letsencrypt"\-v"/var/lib/letsencrypt:/var/lib/letsencrypt"\-v"/path/to/credentials.ini:/path/to/credentials.ini"\--entrypoint/bin/shcertbot/certbot
pipinstallcertbot-dnshubchmod600/path/to/credentials.ini
certbotcertonly-adnshub\--dnshub-credentials/path/to/credentials.ini\-dwww.example.comexample of credentials file as below:dnshub_provider=dnspoddnshub_api_id=12345dnshub_api_token=1234567890abcdef1234567890abcdefFAQ
Package: certbot-dns-infomaniak
InfomaniakDNS Authenticator plugin forcertbotThis plugin enables usage of Infomaniak public API to completedns-01challenges.Issue a tokenAt your Infomaniak managerdashboard, to to the API section and generate a token
with “Domain” scopeInstallationpipinstallcertbot-dns-infomaniakUsageVia environment variableexportINFOMANIAK_API_TOKEN=xxxcertbotcertonly\--authenticatordns-infomaniak\--serverhttps://acme-v02.api.letsencrypt.org/directory\--agree-tos\--rsa-key-size4096\-d'death.star'If certbot requires elevated rights, the following command must be used instead:exportINFOMANIAK_API_TOKEN=xxxsudo--preserve-env=INFOMANIAK_API_TOKENcertbotcertonly\--authenticatordns-infomaniak\--serverhttps://acme-v02.api.letsencrypt.org/directory\--agree-tos\--rsa-key-size4096\-d'death.star'Via INI fileCertbot will emit a warning if it detects that the credentials file can be
accessed by other users on your system. The warning reads “Unsafe permissions
on credentials configuration file”, followed by the path to the credentials
file. This warning will be emitted each time Certbot uses the credentials file,
including for renewal, and cannot be silenced except by addressing the issue
(e.g., by using a command likechmod 600to restrict access to the file).--authenticatordns-infomaniakselect the authenticator plugin (Required)--dns-infomaniak-credentialsInfomaniak Token credentials
INI file. (Required)An examplecredentials.inifile:dns_infomaniak_token=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXTo start using DNS authentication for Infomaniak, pass the following arguments on certbot’s command line:certbotcertonly\--authenticatordns-infomaniak\--dns-infomaniak-credentials<pathtofile>\--serverhttps://acme-v02.api.letsencrypt.org/directory\--agree-tos\--rsa-key-size4096\-d'death.star'Automatic renewalBy default, certbot installs a service that periodically renews its
certificates automatically. In order to do this, the command must know the API
key, otherwise it will fail silently.In order to enable automatic renewal for your wildcard certificates, you will
need to edit/lib/systemd/system/certbot.service. In there, add the
following line inService, with <YOUR_API_TOKEN> replaced with your actual
token:Environment="INFOMANIAK_API_TOKEN=<YOUR_API_TOKEN>"AcknowledgmentsBased on certbot-dns-ispconfig plugin athttps://github.com/m42e/certbot-dns-ispconfig/
Package: certbot-dns-innovativity
certbot-dns-innovativityAn Authenticator plugin for Certbot DNS-01 ACME that uses Innovativity's DNS Manager module.OverviewInnovativityis a cloud/devops consulting company based in Italy. We offer many
IT-related services to our customers, including a centralized panel for ACME DNS authentication for multiple
providers (CloudFlare, DigitalOcean, Hetzner, and more).This package is currently meant for Innovativity customers, although plans are on the way to opensource the whole
project.The API called by this authenticator provides a way to create/delete DNS ACME challenges. The API verifies the
credentials and their permission on the requested domain/subdomain and creates a TXT record on success for a
DNS-01 challenge. The cleanup allows deletion of that record only.
This provides more granularity of most providers' API tokens, such as CloudFlare's Zone Token or DigitalOcean's API Key.InstallationInstall using pip:pip install certbot-dns-innovativityUsageCreate a credentials file with strict permissions:touch ~/.secrets/certbot/innovativity.ini
chmod 600 ~/.secrets/certbot/innovativity.iniConfigure API url and token:# DNS Manager credentials used by Certbotdns_innovativity_dashboard_url=http://localhost:8000/dns_innovativity_api_token=1234567890asdfghjkl1234567890asdfghjklThe path to this file can be provided interactively or using the--dns-innovativity-credentialscommand-line argument.This file will be used again by Certbot during renewal, so it shouldn't be deleted nor moved without changing renew configurations.To acquire a new certificate, run:certbot certonly \
   --authenticator dns-innovativity \
   --dns-innovativity-credentials ~/.secrets/certbot/innovativity.ini \
   -d domain.example.com