Saravanan666/pypi-org huggingface dataset:
Package: certbot-dns-plesk
certbot-dns-pleskplesk 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 certbot-dns-pleskVerify:$ certbot plugins --text

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
* dns-plesk
Description: Obtain certificates using a DNS TXT record by using the plesk dns api.
Interfaces: IAuthenticator, IPlugin
Entry point: dns-plesk = certbot_dns_plesk.dns_plesk:Authenticator

...ConfigurationThe credentials file e.g.~/plesk-credentials.inishould look like this:dns_plesk_username = your-username
dns_plesk_password = secret
dns_plesk_api_url = https://plesk-api-host:8443Usagecertbot certonly \
        --authenticator dns-plesk  \
        --dns-plesk-credentials ~/plesk-credentials.ini \
        --dns-plesk-propagation-seconds 30 \
        -d your-domain
Package: certbot-dnspod
certbot-dnspodA certbot plugin for DNSPod安装pip install certbot-dnspod创建证书sudo certbot certonly \
--authenticator certbot-dnspod \
--certbot-dnspod-credentials ~/.secrets/certbot/dnspod.ini \
-d example.com \
-d *.example.com其中~/.secrets/certbot/dnspod.ini为配置文件路径，内容certbot_dnspod_token_id = <your token id>
certbot_dnspod_token = <your token>chmodchmod 600 ~/.secrets/certbot/dnspod.ini参数官方插件是参数形式是--dns-cloudflare-credentials而第三方插件的参数是::--authenticator certbot-dnspod或者-a certbot-dnspod其他certbot命令行参数编写一个certbot插件官方插件三方插件poetry加自定义的entry_points
Package: certbot-dns-powerdns
certbot-dns-powerdnsPowerDNS 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-powerdnsVerify:$ certbot plugins --text

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
* certbot-dns-powerdns:dns-powerdns
Description: Obtain certificates using a DNS TXT record (if you are using
PowerDNS for DNS.)
Interfaces: IAuthenticator, IPlugin
Entry point: dns-powerdns = certbot_dns_powerdns.dns_powerdns:Authenticator

...
...ConfigurationThe credentials file e.g.~/pdns-credentials.inishould look like this:certbot_dns_powerdns:dns_powerdns_api_url = https://api.mypowerdns.example.org
certbot_dns_powerdns:dns_powerdns_api_key = AbCbASsd!@34Usagecertbot ... \
        --authenticator certbot-dns-powerdns:dns-powerdns  \
        --certbot-dns-powerdns:dns-powerdns-credentials ~/pdns-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/pdns-credentials.iniLicenseCopyright (c) 2019DT Pan-Net s.r.o
Package: certbot-dns-powerdns-admin
certbot-dns-powerdnsPowerDNS 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-powerdnsVerify:$ certbot plugins --text

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
* certbot-dns-powerdns:dns-powerdns
Description: Obtain certificates using a DNS TXT record (if you are using
PowerDNS for DNS.)
Interfaces: IAuthenticator, IPlugin
Entry point: dns-powerdns = certbot_dns_powerdns.dns_powerdns:Authenticator

...
...ConfigurationThe credentials file e.g.~/pdns-credentials.inishould look like this:certbot_dns_powerdns:dns_powerdns_api_url = https://api.mypowerdns.example.org
certbot_dns_powerdns:dns_powerdns_api_key = AbCbASsd!@34Usagecertbot ... \
        --authenticator certbot-dns-powerdns:dns-powerdns  \
        --certbot-dns-powerdns:dns-powerdns-credentials ~/pdns-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/pdns-credentials.iniLicenseCopyright (c) 2019DT Pan-Net s.r.o
Package: certbot-dns-powerdns-bbr
Certbot DNS Authenticator for PowerDNSPowerDNS DNS Autenticator plugin for Certbot DNS-01 challenge.This plugin uses the PowerDNS HTTP REST API.Installpip install certbot-dns-powerdns-bbrUsageCreate credential file.mkdir -m 600 /etc/letsencrypt/.secret
touch /etc/letsencrypt/.secret/dns-powerdns-bbr.ini
chmod 600 /etc/letsencrypt/.secret/dns-powerdns-bbr.ini/etc/letsencrypt/.secret/dns-powerdns-bbr.inidns_powerdns_bbr_endpoint = http://localhost:8081
dns_powerdns_bbr_server_id = localhost
dns_powerdns_bbr_api_key = <Your API Key>Run certbot certonly with credentials file path.certbot certonly \
  --authenticator dns-powerdns-bbr \
  --dns-powerdns-bbr-credentials /etc/letsencrypt/.secret/dns-powerdns-bbr.ini \
  --dns-powerdns-bbr-propergation-seconds 60 \
  -d 'your.1st.domain.here' \
  -d 'your.2nd.domain.here'
Package: certbot-dns-rackspace
certbot-dns-rackspaceCertbot plugin for ACME DNS-01 Challenge on Rackspace Cloud DNSUsagecertbot certonly \
  -a certbot-dns-rackspace \
  -d example.com \
  --certbot-dns-rackspace:dns-rackspace-credentials="/path/to/creds.ini" \
  --certbot-dns-rackspace:dns-rackspace-zone=example.comExample ConfigurationSave the following somewhere safe, like a protectedrax.inifile accessible only to certbot.certbot_dns_rackspace:dns_rackspace_username = foobarbaz
certbot_dns_rackspace:dns_rackspace_api_key = 1337cafef00dd00dbabe
Package: certbot-dns-rcode0
RcodeZeroDNS Authenticator plugin forcertbot.This plugin automates the process of completing adns-01challenge by
creating, and subsequently removing, TXT records using theRcodeZero DNS APIvialexicon.Installationpip install certbot-dns-rcode0Named ArgumentsTo start using DNS authentication for RcodeZero DNS, pass the following arguments on
certbot’s command line:--authenticatorcertbot-dns-rcode0:dns-rcode0select the authenticator
plugin (Required)--certbot-dns-rcode0:dns-rcode0-credentialsRcodeZero DNScredentialsINI file. (Required)--certbot-dns-rcode0:dns-rcode0-propagation-secondswaiting time for DNS to propagate before askingthe ACME server to verify the DNS record.(Default: 10, Recommended: >= 600)You may need to set an even higher propagation time (>= 900 seconds) to give
the RcodeZero DNS network time to propagate the entries! This may be annoying when
calling certbot manually but should not be a problem in automated setups.(Note that the verbose and seemingly redundantcertbot-dns-rcode0:prefix
is currently imposed by certbot for external plugins.)CredentialsUse of this plugin requires a configuration file containing RcodeZero DNS API
ACME token, obtained from your RcodeZeroaccount page. See also theRcodeZero DNS APIdocumentation.An examplecredentials.inifile:certbot_dns_rcode0:dns_rcode0_api_key  = acme_0123456789abcdef0123456789abcdef01234567The path to this file can be provided interactively or using the--certbot-dns-rcode0:dns-rcode0-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 the API token as you would protect the
password to your RcodeZero 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 any domain under the
RcodeZero account, even if those domains aren’t being managed by this server.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.comand*.example.com, waiting 900 seconds for DNS propagation:certbotcertonly\--authenticatorcertbot-dns-rcode0:dns-rcode0\--certbot-dns-rcode0:dns-rcode0-credentials~/.secrets/certbot/rcode0.ini\--certbot-dns-rcode0:dns-rcode0-propagation-seconds900\--serverhttps://acme-v02.api.letsencrypt.org/directory\-d'example.com'\-d'*.example.com'
Package: certbot-dns-scaleway
ScalewayDNS Authenticator plugin forCertbotThis plugin automates the process of completing adns-01challenge by adding/removing TXT records using the Scaleway DNS API.Configuration of Scaleway Certbot PluginGenerate a Token for your Project at Scaleway Console (followhttps://www.scaleway.com/en/docs/generate-api-keys/)Installationpip install certbot-dns-scalewayNamed ArgumentsTo start using DNS authentication for Scaleway, use the following arguments on certbot’s command line:--authenticatordns-scalewayselect the authenticator plugin (Required)--dns-scaleway-credentialsScaleway credentials INI file. (Required)--dns-scaleway-propagation-secondswaiting time for DNS to propagate before asking
the ACME server to verify the DNS record.
(Default: 60)CredentialsAn examplescaleway.inifile:dns_scaleway_application_token=b3a0b9a9-3814-4f12-95b0-a7473bf8b306CAUTION:You should protect these API credentials as you would the
password to your Scaleway project. 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.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.comand*.example.com, waiting 900 seconds for DNS propagation:certbotcertonly\--authenticatordns-scaleway\--dns-scaleway-credentials/etc/letsencrypt/.secrets/scaleway.ini\--dns-scaleway-propagation-seconds900\--serverhttps://acme-v02.api.letsencrypt.org/directory\--agree-tos\--rsa-key-size4096\-d'example.com'\-d'*.example.com'DockerIn order to create a docker container with a certbot-dns-scaleway installation,
create an empty directory with the followingDockerfile:FROMcertbot/certbotRUNpipinstallcertbot-dns-scalewayProceed to build the image:docker build -t certbot/dns-scaleway .Once that’s finished, the application can be run as follows:docker run --rm \
   -v /var/lib/letsencrypt:/var/lib/letsencrypt \
   -v /etc/letsencrypt:/etc/letsencrypt \
   --cap-drop=all \
   certbot/dns-scaleway certonly \
   --authenticator dns-scaleway \
   --dns-scaleway-propagation-seconds 900 \
   --dns-scaleway-credentials \
       /etc/letsencrypt/.secrets/scaleway.ini \
   --no-self-upgrade \
   --keep-until-expiring --non-interactive --expand \
   --server https://acme-v02.api.letsencrypt.org/directory \
   -d example.com -d '*.example.com'It is suggested to secure the folder as follows:chown root:root /etc/letsencrypt/.secrets
chmod 600 /etc/letsencrypt/.secrets
Package: certbot-dns-solidserver
certbot-dns-solidserverSOLIDserver DNS Authenticator plugin for CertbotThis plugin automates the process of completing adns-01challenge by
creating, and subsequently removing, TXT records using the SOLIDserver REST API.Configuration of SOLIDserverIn theAdministration -> Usersyou have to have a user, with the following rightsDNS zone functionsDNS record functionsInstallationpip install certbot-dns-solidserverNamed ArgumentsTo start using DNS authentication for solidserver, pass the following arguments on
certbot's command line:ArgumentDescription--authenticator dns-solidserverSelect the authenticator plugin (Required)--dns-solidserver-credentialsSOLIDserver REST User credentials INI file. (Default:/etc/letsencrypt/solidserver.ini)--dns-solidserver-propagation-secondsWaiting time for DNS to propagate before asking the ACME server to verify the DNS record. (Default: 10)CredentialsAn examplesolidserver.inifile:# Sample SOLIDserver INI file
# Default location /etc/letsencrypt/solidserver.ini
#
dns_solidserver_hostname="your.solidserver.host"
dns_solidserver_username="myremoteuser"
dns_solidserver_password="verysecureremoteuserpassword"
dns_solidserver_dnsname="my.dns.server"
#
# Optional: uncomment this line if dnsview must be used
#dns_solidserver_viewname="external"The path to this file can be provided interactively or using the--dns-solidserver-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 solidserver 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.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.comand*.example.com, waiting 900 seconds for DNS propagation:certbot certonly \
 --authenticator dns-solidserver \
 --dns-solidserver-credentials /etc/letsencrypt/.secrets/domain.tld.ini \
 --dns-solidserver-propagation-seconds 60 \
 --server https://acme-v02.api.letsencrypt.org/directory \
 --agree-tos \
 --rsa-key-size 4096 \
 -d 'example.com' \
 -d '*.example.com'NotesThis is based on the work incertbot-dns-ipsconfigand theeiprestSOLIDserver REST client python package.
Package: certbot-dns-stackit
Certbot DNS-STACKIT Authenticator PluginThe Certbot DNS-STACKIT Authenticator Plugin facilitates the procurement of SSL/TLS certificates from Let's Encrypt
utilizing the DNS-01 challenge methodology in conjunction with STACKIT as the designated DNS service provider. This
document elucidates the procedural steps for the installation and operational utilization of this plugin.InstallationTo initialize the Certbot DNS-STACKIT Authenticator Plugin, deploy the following pip command:pipinstallcertbot-dns-stackitUsageUpon successful integration of the plugin, it becomes viable to employ it with Certbot for the retrieval of SSL/TLS
certificates. The subsequent section delineates the pertinent arguments and their respective examples:ArgumentsArgumentExample ValueDescription--authenticatordns-stackitEngages the STACKIT authenticator mechanism. This must be configured as dns-stackit. (Mandatory)--dns-stackit-credentials./credentials.iniDenotes the directory path to the credentials file for STACKIT DNS. This document must encapsulate the dns_stackit_auth_token and dns_stackit_project_id variables. (Mandatory)--dns-stackit-propagation-seconds900Configures the delay prior to initiating the DNS record query. A 900-second interval (equivalent to 15 minutes) is recommended. (Default: 900)ExampleBelow is a structured example detailing the application of Certbot in conjunction with the DNS-STACKIT
Authenticator Plugin to retrieve a certificate:certbotcertonly\--authenticatordns-stackit\--dns-stackit-credentials./credentials.ini\--dns-stackit-propagation-seconds900\--serverhttps://acme-v02.api.letsencrypt.org/directory\--agree-tos\--rsa-key-size4096\-d'example.runs.onstackit.cloud'\-d'*.example.runs.onstackit.cloud'For this example, example.runs.onstackit.cloud represents the designated domain (zone) for certificate procurement.Example of credentials.iniTo operationalize the plugin, it's imperative to curate a credentials.ini file encompassing your STACKIT DNS
credentials:dns_stackit_auth_token="your_token_here"dns_stackit_project_id="your_project_id_here"It's crucial to replace "your_token_here" and "your_project_id_here" placeholders with the genuine STACKIT
authentication token and project ID. The token's associated service account necessitates project membership privileges
for record set creation.Test ProceduresUnit Testing:maketestLinting:makelintContributeSeeCONTRIBUTING.md
Package: certbot-dns-standalone
Standalone DNS Authenticator plugin for CertbotThis is a plugin that uses an integrated DNS server to respond to the_acme-challengerecords. Simultaneous challenges are supported.A subdomain needs to be created that defines certbot as its nameserver,
e.g. foracme.example.com:acme     IN  NS  ns-acme.example.com.
ns-acme  IN  A   1.2.3.4where 1.2.3.4 is the IP of the server where certbot will be run. This
configuration directs any requests to*.acme.example.comto 1.2.3.4
where the plugin will respond with the relevant challenge.Any server can be used as long as port 53 is available which means that
a DNS server cannot be run at that particular IP at the same time.The plugin binds to all available interfaces. The validation usually
takes less than a second.Next,_acme-challengefor the domain that the certificate is
requested for must be configured as a CNAME record todomain.acme.example.com, e.g. forexample.net:_acme-challenge  IN  CNAME  example.net.acme.example.com.This means that any requests to_acme-challenge.example.netshould
be performed toexample.net.acme.example.cominstead which is where
our certbot runs. No further changes to the DNS ofexample.netare
necessary.Installation# pip3 install certbot certbot-dns-standaloneUsageJust runcertbot certonlyand use thedns-standaloneplugin:# certbot certonly
Saving debug log to /var/log/letsencrypt/letsencrypt.log

How would you like to authenticate with the ACME CA?
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
1: Obtain certificates using an integrated DNS server
(certbot-dns-standalone:dns-standalone)
2: Spin up a temporary webserver (standalone)
3: Place files in webroot directory (webroot)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Select the appropriate number [1-3] then [enter] (press 'c' to cancel): 1
Plugins selected: Authenticator dns-standalone, Installer None
Please enter in your domain name(s) (comma and/or space separated)  (Enter 'c' to cancel): *.example.netNon-interactive usage:certbot --non-interactive --agree-tos --email certmaster@example.com certonly \
  --preferred-challenges dns --authenticator dns-standalone \
  --dns-standalone-address=0.0.0.0 \
  --dns-standalone-ipv6-address=:: \
  --dns-standalone-port=53 \
  -d example.comTo renew the certificates addcertbot renewtocrontab.Parameters supportedParameters can be specified as--dns-standalone-PARAMETER=VALUE. For older certbot versions it should be--certbot-dns-standalone:dns-standalone-PARAMETER=VALUE.Supported parameters are:address– IPv4 address to bind to, defaults to0.0.0.0ipv6-address– IPv6 address to bind to, defaults to::port– port to use, defaults to 53Third party projectsThird party projects integrating certbot-dns-standalone:CertCache
Package: certbot-dns-synergy-wholesale
certbot-dns-synergy-wholesaleASynergy WholesaleDNS plugin forCerbotto authenticate and retrieve Lets Encrypt certificates. Automates the process of completing adns-01challenge by creating, and subsequently removing,TXTrecordsInstallation# create a virtual environment, to avoid conflicts
python3 -m venv /some/path

# use the pip in the virtual environment to install or update
/some/path/bin/pip install -U certbot-dns-synergy-wholesale

# use the cerbot from the virtualenv, to avoid accidentally
# using one from a different environment that does not have this library
/some/path/bin/certbotNamed ArgumentsTo start using DNS authentication for Synergy Wholesale, pass the following arguments on certbot's command line:OptionDescription--authenticator dns-synergy-wholesaleselect the authenticator plugin (Required)--dns-synergy-wholesale-credentials FILEcredentials INI file. (Required)CredentialsUse of this plugin requires a configuration file containing API credentials, obtained from yourmanage.synergywholesale.com.Warning:You must whitelist the IP address from where certbot will run, Otherwise you'll run into API errors.Remember this file will need to have 600 permissions.An examplecredentials.inifile:dns_synergy_wholesale_reseller_id = 1
dns_synergy_wholesale_api_key = abc123ExamplesTo acquire a single certificate for bothexample.comand*.example.comcertbot certonly \
  --authenticator dns-synergy-wholesale \
  --dns-synergy-wholesale-credentials /path/to/credentials.ini \
  -d 'example.com' \
  -d '*.example.com'You can also add addtional paramaters such as--keep-until-expiring --non-interactive --expandfor automation. More informationhereDockerYou can build a docker image from source using the includedDockerfileor pull the latest version directly from Docker Hub:docker pull alamellama/certbot-dns-synergy-wholesaleOnce that's finished, the application can be run as follows:docker run --rm \
  -v /var/lib/letsencrypt:/var/lib/letsencrypt \
  -v /etc/letsencrypt:/etc/letsencrypt \
  --cap-drop=all \
  alamellama/certbot-dns-synergy-wholesale certbot certonly \
    --authenticator dns-synergy-wholesale \
    --dns-synergy-wholesale-credentials /var/lib/letsencrypt/credentials.ini \
    --keep-until-expiring --non-interactive --expand \
    --server https://acme-v02.api.letsencrypt.org/directory \
    --agree-tos --email "webmaster@example.com" \
    -d example.com -d '*.example.com'You may want to change the volumes/var/lib/letsencryptand/etc/letsencryptto local directories where the certificates and configuration should be stored.