Saravanan666/pypi-org huggingface dataset:
Package: certbot-dns-tencentcloud
certbot-dns-tencentcloudThis package provides a Certbot authenticator plugin
that can complete the DNS-01 challenge using the Tencent Cloud API.InstallationOnly Tested on python 3.8, should work on python 3.7 too and forward.no plan to support python2dataclassesis used, so python 3.6 and down will not work. However you can try installingdataclassesfrom pypi.Use pip to install this package:sudo pip3 install certbot-dns-tencentcloudVerify the installation with Certbot:sudo certbot pluginsYou should seedns-tencentcloudin the output.UsageTo use this plugin, set the authenticator todns-tencentcloudvia the-aor--authenticatorflag.
You may also set this using Certbot's configuration file (defaults to/etc/letsencrypt/cli.ini).You will also need to provide a credentials file with your Tencent Cloud API key id and secret, like the following:dns_tencentcloud_secret_id  = TENCENTCLOUD_SECRET_ID
dns_tencentcloud_secret_key = TENCENTCLOUD_SECRET_KEYThe path to this file can be provided interactively or via the--dns-tencentcloud-credentialsargument.You can also provide the credential usingTENCENTCLOUD_SECRET_IDandTENCENTCLOUD_SECRET_KEYenvironment variables.CAUTION:Protect your API key as you would the password to your account.
Anyone with access to this file can make API calls on your behalf.
Be sure toread the security tips below.Arguments--dns-tencentcloud-credentialspath to Tencent Cloud credentials INI file (Required)--dns-tencentcloud-propagation-secondsseconds to wait before verifying the DNS record (Default: 10)NOTE:Due to alimitation in Certbot,
these argumentscannotbe set via Certbot's configuration file.ExampleWhen in root:certbot certonly \
  -a dns-tencentcloud \
  --dns-tencentcloud-credentials ~/.secrets/certbot/tencentcloud.ini \
  -d example.comor if providing credentials using environment variable:export TENCENTCLOUD_SECRET_ID=<your_secret_id> TENCENTCLOUD_SECRET_KEY=<your_secret_key>
certbot certonly \
  -a dns-tencentcloud \
  -d example.comSecurity TipsRestrict access of your credentials file to the owner.You can do this usingchmod 600.
Certbot will emit a warning if the credentials file
can be accessed by other users on your system.Use a separate key from your account's primary API key.Make a separate user under your account,
and limit its access to only allow DNS access
and the IP address of the machine(s) that will be using it.FAQWhich strategy should I choose to limit my API key access to only allow DNS resolution related operation?We now use the new DNSPOD api so you need to giveQcloudDNSPodFullAccessstrategy (need to add record so write permission is necessary).renew certs for*.abc.comandabc.comat the same time sometimes show error about incorrect TXT records.It seems Let's Encrypt cache TXT records for at most 60 seconds, since DNSPod doesn't seem
to allow setting TXT record's TTL below 60, in this case the best/safest way is to set--dns-tencentcloud-propagation-secondslonger than 60.Debug mode?--dns-tencentcloud-debug true
Package: certbot-dns-timeweb
certbot-dns-timewebTimeweb DNS Authenticator plugin for CertbotInstallationpipinstallcertbot-dns-timewebGetting startedGet Timeweb Cloudaccess tokenand fill credentials configuration.Then issue a certificate with command like:certbotcertonly--authenticatordns-timeweb\--dns-timeweb-credentials/etc/letsencrypt/timeweb-creds.ini\-dexample.org-d*.example.orgPlugin arguments--dns-timeweb-credentials- path to Credentials configuration.--dns-timeweb-propagation-seconds- seconds when DNS record is propagated (default: 10)Configuration example# /etc/letsencrypt/timeweb-creds.ini is a suggested path for# configuration file. You may place him in any place.dns_timeweb_api_key=XXXXXXXXXXXXXXXXXXXDevelopmentLocal debuggingInstall the plugin in developer modepipinstall--editable./Run (or debug)main.pyscript
Package: certbot-dns-transip
Certbot plugin to authenticate using dns TXT records via Transip APIDocumentation:https://readthedocs.org/projects/certbot-dns-transip/You can also run this directly from Docker, and get the certificates and keys written to disk for further processing.For example the following command can be used. This assumes thetransip.inifile and the keyfile are present in/tmp/letsencrypt.docker run -ti -v `/tmp/letsencrypt`:/etc/letsencrypt \
    -w /etc/letsencrypt \
    hsmade/certbot-transip \
    certonly -n \
    -d 'your.domain.com' \
    -a dns-transip \
    --dns-transip-credentials /etc/letsencrypt/transip.ini \
    --dns-transip-propagation-seconds 240 \
    -m your@domain.com \
    --agree-tos \
    --eff-emailThe contents oftransip.iniare as follows.dns_transip_key_file = transip.key
dns_transip_username = my_userFinally, the key file is an RSA private keyHistory0.4.3 (13-10-2021)adddns_transip_global_keyas option in ini file0.4.1 (07-10-2021)refactored code to use new v6 APIchanged workflow to github actionsupdated docker base image to python:3.90.3.0 (24-03-2020)updated CI and docker to python 3.6changed dockerfile from using CMD to ENTRYPOINT0.2.6 (21-03-2020)updated transip lib0.1.4 (18-01-2019)Added docker image + instructions0.1.2 (12-11-2018)Updated the API for transip to current version0.1 (14-07-2017)First release onhttps://pypi.python.org/pypi/certbot-dns-transip
Package: certbot-dns-transip-simple
certbot-dns-transiptransip_ DNS Authenticator plugin for CertbotThis plugin automates the process of completing adns-01challenge by
creating, and subsequently removing, TXT records using the transip Remote API.Configuration of transipInhttps://www.transip.be/cp/account/api/you need to have to a keypairInstallationpip install certbot-dns-transip-simpleNamed ArgumentsTo start using DNS authentication for transip, pass the following arguments on
certbot's command line:--authenticator certbot-dns-transip:dns-transip: select the authenticator plugin (Required)--dns-transip-credentials: transip Remote User credentials INI file. (Required)--dns-transip-propagation-seconds: waiting time for DNS to propagate before asking the ACME server to verify the DNS record. Default: 10, Recommended: >= 600)CredentialsAn examplecredentials.inifile:dns_transip_username=myremoteuserdns_transip_api_key_file=path/to/transip_api_keyThe path to this file can be provided interactively or using the--dns-transip-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 transip 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:certbotcertonly\--authenticatordns-transip\--dns-transip-credentials/etc/letsencrypt/.secrets/domain.tld.ini\--dns-transip-propagation-seconds900\--serverhttps://acme-v02.api.letsencrypt.org/directory\--agree-tos\--rsa-key-size4096\-d'example.com'\-d'*.example.com'certbotcertonly-d'example.com'-d'*.example.com'--agree-tos--authenticatordns-transip--dns-transip-credentials=credentials.ini-n--email=certbot@example.com--dns-transip-propagation-seconds600It is suggested to secure the folder as follows::
chown root:root /etc/letsencrypt/.secrets
chmod 600 /etc/letsencrypt/.secrets
Package: certbot-dns-valuedomain
# How to install```sh$ sudo pip install certbot-dns-valuedomain...$ certbot plugins- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -* certbot-dns-valuedomain:dnsDescription: Obtain certificates using a DNS TXT record (if you are usingvalue-domain for DNS).Interfaces: IAuthenticator, IPluginEntry point: dns = certbot_dns_valuedomain:Authenticator...```# How to use```sh$ cat << EOF | sudo tee /etc/letsencrypt/valuedomain.inicertbot_dns_valuedomain:dns_username = YOUR_VALUEDOMAIN_USERNAMEcertbot_dns_valuedomain:dns_password = YOUR_VALUEDOMAIN_PASSWORDEOF...$ sudo chmod 600 /etc/letsencrypt/valuedomain.ini...$ sudo certbot certonly --authenticator certbot-dns-valuedomain:dns --domain example.com --domain *.example.com --manual-public-ip-logging-ok --preferred-challenges dns-01...```# Options```sh$ certbot --help certbot-dns-valuedomain:dnsusage:certbot [SUBCOMMAND] [options] [-d DOMAIN] [-d DOMAIN] ...Certbot can obtain and install HTTPS/TLS/SSL certificates.  By default,it will attempt to use a webserver both for obtaining and installing thecertificate.optional arguments:-h, --help            show this help message and exit-c CONFIG_FILE, --config CONFIG_FILEpath to config file (default: /etc/letsencrypt/cli.iniand ~/.config/letsencrypt/cli.ini)certbot-dns-valuedomain:dns:Obtain certificates using a DNS TXT record (if you are using value-domainfor DNS).--certbot-dns-valuedomain:dns-propagation-seconds CERTBOT_DNS_VALUEDOMAIN:DNS_PROPAGATION_SECONDSThe number of seconds to wait for DNS to propagatebefore asking the ACME server to verify the DNSrecord. (default: 10)--certbot-dns-valuedomain:dns-credentials PATHPath to credentials INI file. (default:/etc/letsencrypt/valuedomain.ini)--certbot-dns-valuedomain:dns-max-propagation-seconds SECONDSThe number of maximum seconds to watch for DNS topropagate before asking the ACME server to verify theDNS record. (default: 3600)```# Links* https://certbot.eff.org/docs/using.html#certbot-command-line-options* https://github.com/certbot/certbot/tree/master/certbot-dns-sakuracloud* https://github.com/free2er/certbot-regru/
Package: certbot-dns-vultr
certbot-dns-vultrThis package provides a Certbot authenticator plugin
that can complete the DNS-01 challenge using the Vultr API.InstallationUse pip to install this package:$ sudo pip3 install certbot-dns-vultrVerify the installation with Certbot:$ sudo certbot pluginsYou should seecertbot-dns-vultr:dns-vultrin the output.UsageTo use this plugin, set the authenticator tocertbot-dns-vultr:dns-vultrvia the-aor--authenticatorflag.
You may also set this using Certbot's configuration file (defaults to/etc/letsencrypt/cli.ini).You will also need to provide a credentials file with your Vultr API key, like the following:certbot_dns_vultr:dns_vultr_key = YOUR_VULTR_API_KEYThe path to this file can be provided interactively or via the--certbot-dns-vultr:dns-vultr-credentialsargument.CAUTION:Protect your API key as you would the password to your account.
Anyone with access to this file can make API calls on your behalf.
Be sure toread the security tips below.Arguments--certbot-dns-vultr:dns-vultr-credentialspath to Vultr credentials INI file (Required)--certbot-dns-vultr:dns-vultr-propagation-secondsseconds to wait before verifying the DNS record (Default: 10)NOTE:Due to alimitation in Certbot,
these argumentscannotbe set via Certbot's configuration file.Example$ certbot certonly \
    -a certbot-dns-vultr:dns-vultr \
    --certbot-dns-vultr:dns-vultr-credentials ~/.secrets/certbot/vultr.ini \
    -d example.comSecurity TipsRestrict access of your credentials file to the owner.You can do this usingchmod 600.
Certbot will emit a warning if the credentials file
can be accessed by other users on your system.Use a separate key from your account's primary API key.Make a separate user under your account,
and limit its access to only allow DNS access
and the IP address of the machine(s) that will be using it.
Package: certbot-dns-yandex
certbot-dns-yandexforked from upstream and modified a bit to support yandex dns API :)============Yandex 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-yandexVerify:$ certbot plugins --text

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
* dns-yandex
Description: Obtain certificates using a DNS TXT record (if you are using Yandex
for DNS.)
Interfaces: Authenticator, Plugin
Entry point: dns-yandex = certbot_dns_yandex.dns_yandex:Authenticator

...
...ConfigurationThe credentials file e.g.~/yandex-credentials.inishould look like this:dns_yandex_auth_token = 123456789ABCDEF0000000000000000000000000000000000000Usagecertbot ... \
        -a dns-yandex  \
        --dns-yandex-credentials ~/yandex-credentials.ini \
        --dns-yandex-propagation-seconds 1880
        certonlydon't know why propagation on yandex need such long time, 30 mins is a safe value.CreditsPowerDNScertbot-dns-dynudns-lexiconHelpful linksDNS Plugin listacme.sh
Package: certbot-dns-yandexcloud
YandexCloud DNS Authenticator plugin for CertbotyandexcloudDNS Authenticator plugin forcertbot.This plugin automates the process of completing a dns-01 challenge by creating, and subsequently removing, TXT records using the yandexcloudAPIInstallationpip install certbot-dns-yandexcloudCertbot ArgumentsTo start using DNS authentication for yandexcloud, pass the following arguments on certbot's command line:OptionDescription--authenticator dns-yandexcloudselect the authenticator plugin (Required)--dns-yandexcloud-credentials FILE_PATHyandexcloud credentials INI file path. (Required)CredentialsBefore credentials.ini providing createyandexcloud service accountand createservice-account-keyand get your folder_id where DNS zone is createdAn examplecredentials.inifile:dns_yandexcloud_sa_json_path = "~/.secrets/certbot/sa.json"
    dns_yandexcloud_folder_id = "b0g0kfc0jutlhm000r00"Examplescertbot certonly \
--authenticator dns-yandexcloud \
--dns-yandexcloud-credentials ~/.secrets/certbot/yandexcloud.ini \
--non-interactive --agree-tos --email username@example.com \
-d 'example.com'
Package: certbot-dns-zoneedit
certbot-dns-zoneeditZoneEditDNS Authenticator plugin forCertbot.This plugin automates the process of completing aDNS-01challenge by creating, and subsequently removing,TXTrecords using the ZoneEdit API end-points.Installationpip install certbot-dns-zoneeditNamed ArgumentsTo start using DNS authentication for ZoneEdit, pass the following arguments on Certbot's command line:OptionDescription--authenticator dns-zoneeditSelect the authenticator plugin (Required)--dns-zoneedit-credentials FILEZoneEdit credentials INI file. (Default is/etc/letsencrypt/zoneedit.ini)--dns-zoneedit-propagation-seconds NUMHow long to wait before veryfing the writtenTXTchallenges. (Default is120)CredentialsUse of this plugin requires a configuration file containing your ZoneEdit user name and authentication token.The token can be obtained from theZoneEdit DynDNS settingspage.An examplezoneedit.inifile:dns_zoneedit_user =   <login-user-id>
dns_zoneedit_token =  <dyn-authentication-token>The default path to this file is set to/etc/letsencrypt/zoneedit.ini, but this can can be changed using the--dns-zoneedit-credentialscommand-line argument.CAUTION:You should protect these API credentials as you would the password to your ZoneEdit account
(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-zoneedit \
  --dns-zoneedit-credentials ~/.secrets/certbot/zoneedit.ini \
  --dns-zoneedit-propagation-seconds 900 \
  --keep-until-expiring --non-interactive --expand \
  --server https://acme-v02.api.letsencrypt.org/directory \
  -d 'example.com' \
  -d '*.example.com'DockerYou can build a docker image from source using the includedDockerfileor pull the latest version directly from Docker Hub:docker pull zlaski/certbot-dns-zoneeditOnce the installation is 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 \
  zlaski/certbot-dns-zoneedit certbot certonly \
    --authenticator dns-zoneedit \
    --dns-zoneedit-propagation-seconds 900 \
    --dns-zoneedit-credentials /var/lib/letsencrypt/zoneedit_credentials.ini \
    --keep-until-expiring --non-interactive --expand \
    --agree-tos --email "webmaster@example.com" \
    -d example.com -d '*.example.com'
Package: certbot-extra-formats
certbot-extra-formatsWrites a "Let's Encrypt" certificate
compatible with a given applicationInstallationcertbot-extra-formatsis available through thePython Package Index (PyPI).
Pip is already installed if you are using Python
3 >=3.4 downloaded frompython.org;
if you're using a GNU/Linux distribution,
you can find how to install it on
thispage.
After setting up pip, you can installcertbot-extra-formatsby simply typing in your terminalpip3 install certbot-extra-formatsUsage$ certbot-extra-formats --help

usage: certbot-extra-formats [-h] [--verbose] [--certroot CERTROOT] [app ...]

Writes a "Let's Encrypt" certificate compatible with a given application

positional arguments:
  app                  application that request the certificate: ejabberd, haproxy, lighttpd,
                       tomcat7, httpd-dh (apache <= 2.4.7 with DH parameters)

options:
  -h, --help           show this help message and exit
  --verbose            extended output
  --certroot CERTROOT  directory which contains the letsencrypt certificatesAboutThis program is licensed underGNU Affero General Public License v3 or laterbyPellegrino Prevete.
If you find this program useful, consider offering me abeer, a newcomputeror a part time remotejobto help me pay the bills.
Package: certbot-freenas-deployer
Certbot FreeNAS DeployerA simple tool to deploy TLS certificates obtained using Certbot to FreeNAS systems.Open Source software: Apache Software License 2.0Documentation:https://certbot-freenas-deployer.rtfd.io.FeaturesThis tool is intended to be used as a “deploy hook” in Certbot configurations, where Certbot
is running on a separate system from FreeNAS (either physically separate, or a jail within
the FreeNAS system). In order for Let’s Encrypt to be able to validate ownership of the domain
name used for the certificate, you’ll need to use a suitablechallengemethod. Since the
HTTP-01 and TLS-SNI-01 challenge methods would both require your FreeNAS system to be reachable
by the Let’s Encrypt servers, and this is generally regarded as a signficant security risk,
it is recommended to use the DNS-01 challenge method with a suitable DNS authenticator for your
DNS provider.The tool requires (at least) FreeNAS 11.1, which is the version in which the GUI certificate
update API methods were introduced. It also requires Python 3.5 or a later version.CreditsThis tool was inspired by danb35’sdeploy-freenasscript, but is intended for use with theCertbottool from theElectronic Frontier Foundation.This package was created withCookiecutterand theaudreyr/cookiecutter-pypackageproject template.History1.1.1 (2018-10-29)Revert docs to ‘Alabaster’ theme since ‘Guzzle’ does not work on ReadTheDocs.1.1.0 (2018-10-29)Documentation improvements.Update setup.py to require Python 3.5 or later.Converted docs to ‘Guzzle’ theme.1.0.0 (2018-10-28)First release on PyPI.
Package: certbot-gitlab
GitLab Pages installer plugin for Certbotcertbot-gitlabis an installer plugin for Certbot. It allows you to automate the installation of certificates issued to GitLab Pages domains.You still need to use a separate authenticator plugin. Readthisfor more information on how installer and authenticator plugins.Installationsudopipinstallcertbot-gitlabUsageObtain as access tokenCreate an access tokenon GitLab with theapiscope.Basic Examplecertbot--installercertbot-gitlab:gitlabThis will run Certbot interactively and allow you to choose your specific authentication method.It will also ask for your GitLab access token. This won't be saved, so automatic renewal (viacertbot renew) won't work. SeeCredentials Filefor how to automate renewal.If you don't want automatic authentication, then add--authenticator manual --preferred-challenges dnsto use manual DNS TXT record authentication.Credentials Filecertbot--installercertbot-gitlab:gitlab--certbot-gitlab:gitlab-token'/path/to/gitlab/token/file'This will take the GitLab access token from/path/to/gitlab/token/file, which should contain just the access token, such as:MY_GITLAB_TOKENIMPORTANT: Make sure this file is in a secure location (such as/root/or/etc/letsencrypt/keys/and that it can only be read byroot.chownroot:root'/path/to/gitlab/token/file'chmod600'/path/to/gitlab/token/file'The path to this file will be saved for automatic renewal, so runningcertbot renewwill automatically install the certificate to GitLab when renewed.All Options--certbot-gitlab:gitlab-server CERTBOT_GITLAB:GITLAB_SERVER
                      GitLab server url (default: https://gitlab.com)

--certbot-gitlab:gitlab-config CERTBOT_GITLAB:GITLAB_CONFIG
                      python-gitlab configuration file (default: None)

--certbot-gitlab:gitlab-token CERTBOT_GITLAB:GITLAB_TOKEN
                      GitLab API token (default: None)

--certbot-gitlab:gitlab-project CERTBOT_GITLAB:GITLAB_PROJECT
                      Name of GitLab project (e.g. user/proj) (default: None)Readthisfor how to use--certbot-gitlab:gitlab-config.
Package: certbot-glesys
GleSYS DNS Authenticator for CertbotThis allows automatic completion ofCertbot’sDNS01 challange for domains managed onGleSYSDNS.Installing$ pip install certbot-glesysUsageCreate 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:--certbot-glesys:auth-credentials(required)INI file withuserandpasswordfor your GlesSYS API user.The credentials file must have the following format:certbot_glesys:auth_user = CL00000
certbot_glesys:auth_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 certbot-glesys:auth \
    --certbot-glesys:auth-credentials credentials.ini \
    -d domain.comIf you want to obtain a wildcard certificate you can use the--serverhttps://acme-v02.api.letsencrypt.org/directoryflag and the domain-d*.domain.com.DisclaimerThis plugin is neither affiliated with nor endorsed by GleSYS Internet Services
AB.ChangelogVersion 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