Saravanan666/pypi-org huggingface dataset:
Package: certbot-httpreq
certbot-httpreq projectcertbot-httpreq is a free and open-source, we develop it to customize and send authenticator and installer certbot requests through HTTP protocol.Table of contentsInstallationUsageConfigurationInstallationpip install certbot-httpreqUsagecertbot \
  --agree-tos \
  --text \
  -a certbot-httpreq:auth \
  -i certbot-httpreq:installer \
  --certbot-httpreq:auth-config /etc/letsencrypt/certbot-httpreq.yml \ # not required
  --certbot-httpreq:installer-config /etc/letsencrypt/certbot-httpreq.yml \ # not required
  runConfiguration file must be placed in /etc/letsencrypt/certbot-httpreq.yml or be specified with arguments --certbot-httpreq:auth-config and --certbot-httpreq:installer-config.ConfigurationYou can customize authenticator HTTP requests for perform and cleanup phases and also installer HTTP requests for deploy phase.# authenticator
perform:
  ### perform HTTP URI ###
  uri: http://localhost
  ### perform HTTP path ###
  path: /
  ### perform HTTP method: PUT or POST ###
  method: PUT
  ### perform HTTP format: json or form-urlencoded ###
  format: json
  ### parameter name in HTTP query string for challenge string ###
  ### default: HTTP path e.g.: http://localhost/HGr8U1IeTW4kY_Z6UIyaakzOkyQgPr_7ArlLgtZE8SX ###
  param_challenge: ~
  ### parameter name in HTTP body for validation string
  ### default: HTTP json payload e.g.: "gfj9Xq...Rg85nM" ###
  param_validation: ~
  ### perform HTTP custom headers ###
  headers: {}
  ### perform HTTP connection timeout ###
  timeout: ~
  ### perform HTTP SSL verify ###
  verify: ~
cleanup:
  ### cleanup HTTP uri ###
  uri: http://localhost
  ### cleanup HTTP path ###
  path: /
  ### cleanup HTTP method: DELETE, PUT or POST ###
  method: DELETE
  ### cleanup HTTP format: json or form-urlencoded ###
  format: json
  ### parameter name in HTTP query string for challenge string ###
  ### default: HTTP path e.g.: http://localhost/HGr8U1IeTW4kY_Z6UIyaakzOkyQgPr_7ArlLgtZE8SX ###
  param_challenge: ~
  ### cleanup HTTP custom headers ###
  headers: {}
  ### cleanup HTTP connection timeout ###
  timeout: ~
  ### cleanup HTTP SSL verify ###
  verify: ~

# installer
deploy:
  ### deploy HTTP URI ###
  uri: http://localhost
  ### deploy HTTP path ###
  path: /
  ### deploy HTTP method: POST or PUT or PATCH ###
  method: POST
  ### deploy HTTP format: json or form-urlencoded ###
  ### e.g.: HTTP json payload: {"domain":"...","cert":"...","key":"...","chain":"..."} ###
  format: json
  ### parameter names in HTTP body
  body_params:
    domain: domain
    cert: cert
    key: key
    chain: chain
  ### deploy HTTP custom headers ###
  headers: {}
  ### deploy HTTP connection timeout ###
  timeout: ~
  ### deploy HTTP SSL verify ###
  verify: ~
Package: certbot-inwx-hook
A hook to be used with the--manualoption of thecertonlysubcommand of certbot. The hooks work with the API ofINWXand thedns-01challenge ofLet’s
encrypt.UsageThis package installs thecertbot_inwx_deployandcertbot_inwx_cleanupentry points. Just supply these to the--manual-auth-hookand--manual-cleanup-hookof certbot.ConfigurationThe configuration file is stored under/etc/certbot_inwx_hook.ini. A
sample is provided undercertbot_iwnx_hook.sample.ini. You can set
the$CERTBOT_INWX_HOOK_CONFIG_FILEenvironment variable to a custom
location, which will take precedence over the default location if set.
In the config file you have to supply your login information. Optionally
you can set additioanl nameserver IPs to check for successful
propagation of the challenge. You would want ot provide the IPs of your
registrar here to speed things up.LicenseThis work is licensed under the MIT license. See License.md for details.
Additionally this work is loosely based onthiscode.
Package: certbot-lego-httpreq
Certbot plugin for HTTP RequestsThis plugin provides a DNS challenge authenticator to solve the challenge using
a HTTP request to a custom endpoint. It uses the same logic aslegowith no HTTPREQ_MODE set.To use the plugin install it using pip and then run certbot usingcertbotcertonly--authenticatordns-httpreq--dns-httpreq-credentials=mycreds.iniwithmycreds.ini:dns_httpreq_endpoint=https://myhost/api/dns/acme/legodns_httpreq_username=someuserdns_httpreq_password=somepassword
Package: certbotlib
A wrapper for Certbot CLIhttps://certbot.eff.org/docs/using.html#manualExecutes certbot on your OS with the given parameters and performs the
requests to Route53 to create the TXT record and validate back to Cerbot.If validation is succeeded, Cerbot will issue the certificates and upload
them in Amazon Certificate Manager. If the certificate for the given domain
already exists, it will replace the certificates instead of creating a new
ARN (this is usually what you want).For obvious reasons, certbot needs access to public DNS zones. At Payconiq,
our DNS is held by Production account but one might need certificates on
Acceptance as well. In this case, the library accepts a profile to
indicate in which account your DNS records are. How to choose a profile is
documented directly on AWS.+info:http://boto3.readthedocs.io/en/latest/guide/configuration.html#shared-credentials-fileDocumentation:http://python.docs.payconiq.io/certbotlibFeaturesCreate certificates from Let’s Encrypt issuer based on DNS validation recordsCreates TXT Record on Route53Upload/Replace them to your ACM in your Amazon accountHistory0.1 (11-09-2017)First release
Package: certbot-loopia
This allows automatic completion ofCertbot’sDNS01 challange for domains managed onLoopiaDNS.Installing$ pip install certbot-loopiaUsageTo use the authenticator you need to provide some required options:--certbot-loopia:credentials(required)INI file withuserandpasswordfor your Loopia API user.usernormally has the formatuser@loopiaapi.The credential file must have the folling format:certbot_loopia:auth_user = user@loopiaapi
certbot_loopia:auth_password = passwordgoeshereFor safety reasons the file must not be world readable. You can solve this by
running:$ chmod 600 credentials.iniKnown issuesDue to caching on Loopia’s side it can take up to 15 minutes before changes
propagates. Therefore the plugin will wait 15 minutes before contacting the
ACME server.ChangelogVersion 0.2.0Released 21st August 2017Rewrote plugin to match the implementation ofcertbot-dns-*pluginsUpdated dependency requirements since the old release was completely broken
for neweracmeandcertbot(seeissue #2)Version 0.1.0Released 10th May 2017Initial releaseDisclaimerThis plugin is neither affiliated with nor endorsed by Loopia AB.
Package: certbot-netdot
Netdot DNS Authenticator for CertbotThis allows automatic completion ofCertbot's <https://github.com/certbot/certbot>_
DNS01 challange for domains managed viaNetdot <https://github.com/cvicente/Netdot/>_ DNS.Installing$ sudo pip install certbot-netdotNote that you should normally install this asroot, unless you know what
you are doing.UsageThe plugin requires a user with the edit, view and delete permissions for the DNS zone you
are creating a certificate in.To use the plugin you need to provide a credentials file--certbot-netdot:credentials(required)INI file withusernameandpasswordfor your Netdot user as well as the endpoint
URL for your netdot instance. You can also provide theverifyflag to disable certificate
verification of the netdot server. This should of course only be used when you want to generate
the certificate for your netdot server itself :)The credentials file must have the following format:certbot_netdot:auth_username = admin
certbot_netdot:auth_password = password
certbot_netdot:auth_endpoint = https://netdot.example.com/netdot
certbot_netdot:auth_verify = TrueFor safety reasons the file must not be world readable. You can solve this by
running:$ chmod 600 credentials.iniThen you can runcertbotusing:$ sudo certbot certonly \
    --authenticator certbot-netdot:auth \
    --certbot-netdot:auth-credentials credentials.ini \
    -d domain.comAttributionThis plugin is based onhttps://github.com/runfalk/certbot-loopiaby Andreas RunfalkChangelogVersion 0.1.1Released 2020-05-15Default cert verification to TrueFixed generating wildcard certs or other multiple certs for a single domain nameVersion 0.1.0Released 2020-05-11Initial Release
Package: certbot-nextlayer
certbot-nextlayernext layer 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 git+https://github.com/nextlayergmbh/certbot-nextlayer.gitVerify:$ certbot plugins --text

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
* certbot-nextlayer
Description: Obtain certificates using a DNS TXT record by using nextlayer DNS
API.
Interfaces: IAuthenticator, IPlugin
Entry point: certbot-nextlayer = certbot_nextlayer.nextlayer_dns:Authenticator

...
...ConfigurationThe credentials file e.g.~/nldns-credentials.inishould look like this:certbot_nextlayer_api_key=abcdefghijklmnopUsagecertbot --authenticator certbot-nextlayer --certbot-nextlayer-credentials ~/nldns-credentials.ini certonly -d nextlayer.at
Package: certbot-nginx-unit
Certbot NGINX Unit pluginThis is a certbot plugin for using certbot in combination with NGINX Unithttps://unit.nginx.org/RequirementThe commandunitcshould be installed and executable.Current FeaturesSupports NGINX Unit/1.31*Supports cerbot 1.21+install certificatesautomatic renewal certificatesInstallationVia Snap (requires certbot to be installed via snap):
Installsnapdinstall certbotsnap install --classic certbotinstall and configure this pluginsudo snap install certbot-nginx-unit 
sudo snap set certbot trust-plugin-with-root=ok
sudo snap connect certbot:plugin certbot-nginx-unitVia Pippip install certbot-nginx-unitVia Pip virtual envCreate a virtual environment, to avoid conflictspython3 -m venv /some/pathuse the pip in the virtual environment to install or update/some/path/bin/pip install -U certbot-nginx-unituse the cerbot from the virtualenv, to avoid accidentally
using one from a different environment that does not have this library/some/path/bin/certbotor uninstall other certbot system installation and link it to /usr/binln -s /some/path/bin/certbot /usr/binUsageConfigure the unit listener with*:80or*:443# unitc /config{
    "listeners": {
        "*:80": {
            "pass": "routes"
        }
        "routes": [
            {
                "action": {
                    "share": "/srv/www/unit/index.html"
                }
            }
        ]
    }
}Now, generate and automatically install the certificate with# certbot --configurator nginx-unit -d www.myapp.comThe result is a certificate created and installed.# unitc /certificates{
	"www.myapp.com_20240202145800": {
		"key": "RSA (2048 bits)",
		"chain": [
			{
				<omissis>
			}
		]
	}
}and the configuration updated# unitc /config{
	"listeners": {
		"*:80": {
			"pass": "routes"
		},

		"*:443": {
			"pass": "routes",
			"tls": {
				"certificate": [
					"www.myapp.com_20240202145800"
				]
			}
		}
	},

	"routes": [
		{
			"match": {
				"uri": "/.well-known/acme-challenge/*"
			},

			"action": {
				"share": "/srv/www/unit/$uri"
			}
		},
		{
			"action": {
				"share": "/srv/www/unit/index.html"
			}
		}
	]
}Auto-renew certificatesCertbot installs a timer on the system to renew certificates one month before the certificate expiration date.Multiple domains/applicationsYou can run the certbot command for each domain# certbot --configurator nginx-unit -d www.myapp1.com
# certbot --configurator nginx-unit -d www.myapp2.com
# unitc '/config/listeners/*:443'{
    "pass": "routes",
    "tls": {
        "certificate": [
            "www.myapp1.com_20240202145800"
            "www.myapp2.com_20240202145800"
        ]
    }
}
Package: certbot-onion
certbot-oniononion-csr-01Authenticator plugin for CertbotThis plugin allows certbot to request certificates for.oniondomains using theonion-csr-01challenge type,
signing the request with the key of the hidden service.Installationpipinstallcertbot-onionUsagecertbot--serverhttps://acme.api.acmeforonions.org/directorycertonly-d5anebu2glyc235wbbop3m2ukzlaptpkq333vdtdvcjpigyb7x2i2m2qd.onion--authenticatoronion-csrThe important arguments here is:--authenticator onion-csrConfiguration arguments--onion-csr-torrc-file /etc/tor/torrc- Provides the path to thetorrcfile, hidden service directories are discovered from this file.--onion-csr-hs-dir /var/lib/tor/example_hs/- Provides the path to the hidden service directory, this can be specified multiple times for multiple domains.If yourtorrcis in the standard location of/etc/tor/torrcthen you do not need to specify any configuration arguments.
Package: certbot-plugin-websupport
Certbot plugin for authentication using Websupport REST APIThis is a plugin forCertbotthat uses the Websupport REST API to allowWebsupportcustomers to prove control of a domain name.UsageObtain an API key and API secret (seeAccount Page)Install the plugin usingpip install certbot-plugin-websupportCreate awebsupport.iniconfig file with the following contents and applychmod 600 websupport.inion it:certbot-plugin-websupport:dns_api_key = APIKEY
certbot-plugin-websupport:dns_api_secret = SECRETReplaceAPIKEYwith your Websupport API key,SECRETwith your API secret and ensure permissions are set
to disallow access to other users.Runcertbotand direct it to use the plugin for authentication and to use
the config file previously created:certbot certonly -a certbot-plugin-websupport:dns --certbot-plugin-websupport:dns-credentials websupport.ini -d domain.comAdd additional options as required to specify an installation plugin etc.Please note that this solution is usually not relevant if you're using Websupport's web hosting services as Websupport offers free automated certificates for all simplehosting plans having SSL in the admin interface.UpdatesThis plugin can be updated by running:pip install certbot-plugin-websupport --upgradeWildcard certificatesThis plugin is particularly useful when you need to obtain a wildcard certificate using dns challenges:certbot certonly -a certbot-plugin-websupport:dns --certbot-plugin-websupport:dns-credentials websupport.ini -d domain.com -d \*.domain.com --server https://acme-v02.api.letsencrypt.org/directoryAutomatic renewalYou can setup automatic renewal usingcrontabwith the following job for weekly renewal attempts:0 0 * * 0 certbot renew -q -a certbot-plugin-websupport:dns --certbot-plugin-websupport:dns-credentials /etc/letsencrypt/websupport/websupport.ini --server https://acme-v02.api.letsencrypt.org/directory
Package: certbot-regru
certbot-regruReg.ru DNS authenticator plugin for CertbotAn authenticator plugin forcertbotto supportLet's EncryptDNS challenges (dns-01) for domains managed by the nameservers ofReg.ru.Requirementscertbot (>=0.21.1)For older Ubuntu distributions check out this PPA:ppa:certbot/certbotInstallationFirst install the plugin:sudo pip install certbot-regruConfigure it with your Reg.ru Credentials:sudo vim /etc/letsencrypt/regru.iniMake sure the file is only readable by root! Otherwise all your domains might be in danger:sudo chmod 0600 /etc/letsencrypt/regru.iniUsageRequest new certificates via a certbot invocation like this:sudo certbot certonly -a certbot-regru:dns -d sub.domain.tld -d *.wildcard.tldRenewals will automatically be performed using the same authenticator and credentials by certbot.Command Line Options--certbot-regru:dns-propagation-seconds PROPAGATION_SECONDS
                        The number of seconds to wait for DNS to propagate
                        before asking the ACME server to verify the DNS record. 
                        (default: 120)
 --certbot-regru:dns-credentials PATH_TO_CREDENTIALS
                        Path to Reg.ru account credentials INI file 
                        (default: /etc/letsencrypt/regru.ini)See alsocertbot --help certbot-regru:dnsfor further information.Removalsudo pip uninstall certbot-regru
Package: certbot-standalone-nfq
certbot-standalone-nfqHTTP authenticator plugin forCertbotwhich is compatible with any web server! (Linux only androotis required.)How?It works by asking the Linux kernel to temporarily divert incoming port 80 HTTP traffic into
a queue. The Certbot plugin then picks out the Let's Encrypt validation requests from the
queue and responds to them. All other traffic reaches its original destination, totally
unchanged. This all happens very quickly and no traffic disruptions occur.Why?Avoids messing about with any webserver configuration, meaning that it can work well
with tricky webservers like Apache Tomcat.Avoids having a proxy in front of your normal webserver, which means all source addresses
(and indeed every network packet) are totally preserved!It is inspiredby this community thread.InstallationviasnapUsing thecertbotsnap is the easiest way to use this plugin. Seeherefor instructions on installing Certbot viasnap.sudosnapinstallcertbot-standalone-nfq
sudosnapsetcertbottrust-plugin-with-root=ok
sudosnapconnectcertbot:plugincertbot-standalone-nfqviapipA source tarballis available.How did you install Certbot?How to install the pluginFromsnapDon't usepip! Use the snap instructions above.Using theofficial Certbotpipinstructionssudo /opt/certbot/bin/pip install certbot-standalone-nfqFromapt,yum,dnfor any other distro package manager. (Requires Certbot 1.25.0 or newer.)pip install certbot-standalone-nfqUsagecertbot-standalone-nfqshould just work without having to configure anything:certbotcertonly-astandalone-nfq\-d"example.com"-d"www.example.com"\--dry-runIf (for some reason, like port forwarding shenanigans) your web server is listening on
a port other than 80, you can use the--http-01-portargument of Certbot to change
the port that the plugin will divert the traffic from.
Package: certbot-vault-installer
Certbot-VaultRunningCreate file with credentials (e.g. /etc/letsencrypt/.hashicorp-vault-creds):vault-addr=https://vault.example.com:8200/vault-token=s.AADSFSDHJGJHGDFGSERWETTRHTTOr define ENV files:exportVAULT_ADDR=https://vault.example.com:8200/exportVAULT_TOKEN=s.AADSFSDHJGJHGDFGSERWETTRHTTRun installer plugin separately (skip--vault-credentialsif creds were provided via ENV variables):certbotinstall-ivault--vault-credentials=/etc/letsencrypt/.hashicorp-vault-creds--vault-path='secret/le-certs'--vault-single--cert-nameexample.comOr as a part or certbot run:certbotrun-a.....-ivault...-dexample.com,www.example.comCLI arguments--vault-credentials- INI file withvault-addr=XYZandvault-token=XYZkey pairs. If not provided, script will attempt to read ENV variablesVAULT_ADDRandVAULT_TOKEN.--vault-path- path in Vault where to store certificates, first component is expected to be engine mount point (e.g. secret, kv, etc...).--vault-dpath- last component of path is always taken from certificate's SAN (e.g. kv/*.example.com). This option can override the domain to something else.--vault-single- upload certs only once if provided multiple SANs via-d example.com,www.example.com- in this case only kv/letsencrypt/example.com will be created.DevelopingHow to setup test env documentedhere. Tl;dr version below:# clone upstream certbot
git clone https://github.com/certbot/certbot.git
cd certbot

# setup virtualenv and install our plugin
python3 tools/venv.py
source venv/bin/activate
pip install -e ../certbot-vault

# run testing ACME server
run_acme_server &

# start Vault dev server and copy root token
vault server -dev &

# generate credentials file for certbot-vault plugin
echo -e 'vault-addr=http://127.0.0.1:8200\nvault-token=ABCDEFG' > ~/dev-hashi-certbot

# issue test certficate
certbot_test run --standalone -d test.example.com -i vault --vault-credentials ~/dev-hashi-certbot --vault-path secret/

# now it should be present in Vault, after checking it, you can try to renew for example
certbot_test renewCurrently supports only kv store.Generate test cert:certbot_test certonly --standalone -d test.example.comInstall cert:certbot_test install -i vault --cert-name test.example.comThis is rather a PoC for newer versions of certbot, but it can be easily modified to support other features in Vault.
Package: certbot-zerossl
Certbot (ZeroSSL Edition)InstallationInstall the client with:python -m pip install certbot-zerosslHow to run the clienthttps://zerossl.com/features/acme/Understanding the client in more depthTo understand what the client is doing in detail, it’s important to
understand the way it uses plugins.  Please see theexplanation of
pluginsin
the User Guide.LinksDocumentation:https://certbot.eff.org/docsUpstream project:https://github.com/certbot/certbotMain Website:https://zerossl.com/features/acme/ACME spec:http://ietf-wg-acme.github.io/acme/ACME working area in github:https://github.com/ietf-wg-acme/acmeSystem RequirementsSeehttps://certbot.eff.org/docs/install.html#system-requirements.Current FeaturesSupports multiple web servers:apache/2.xnginx/0.8.48+webroot (adds files to webroot directories in order to prove control of
domains and obtain certs)standalone (runs its own simple webserver to prove you control a domain)other server software viathird party pluginsThe private key is generated locally on your system.Can talk to the Let’s Encrypt CA or optionally to other ACME
compliant services.Can get domain-validated (DV) certificates.Can revoke certificates.Adjustable RSA key bit-length (2048 (default), 4096, …).Can optionally install a http -> https redirect, so your site effectively
runs https only (Apache only)Fully automated.Configuration changes are logged and can be reverted.Supports an interactive text UI, or can be driven entirely from the
command line.Free and Open Source Software, made with Python.For extensive documentation on using Certbot, go tohttps://certbot.eff.org/docs.
Package: cert-chain-resolver
Python certificate chain resolverResolve / obtain the certificate intermediates of a x509 certificate using the CLI or python API.The CLI writes the full bundle to stdout. The Python API can be used to iterate over the certificates and get additional information on the bundle.from cert_chain_resolver.api import resolve
with open('cert.pem', 'rb') as f:
   fb = f.read()
   chain = resolve(fb)
>>>
for cert in chain:
  print(cert)
<Cert common_name="cert-chain-resolver.remcokoopmans.com" subject="CN=cert-chain-resolver.remcokoopmans.com" issuer="CN=R3,O=Let's Encrypt,C=US">
<Cert common_name="R3" subject="CN=R3,O=Let's Encrypt,C=US" issuer="CN=DST Root CA X3,O=Digital Signature Trust Co.">
<Cert common_name="DST Root CA X3" subject="CN=DST Root CA X3,O=Digital Signature Trust Co." issuer="CN=DST Root CA X3,O=Digital Signature Trust Co.">SupportPKCS7, PEM and DER formatsLetsEncrypt certificatesDependenciescryptographyDocumentationRead more onreadthedocsInstallPypi$ pip install cert-chain-resolverUsageInstalled using PIP$ cert_chain_resolver certificate.crt > bundle.crtOr read from stdin$ cat certificate.crt | cert_chain_resolver > bundle.crtAfter cloning the repositoryInstall dependencies$ makefrom file:$ python -m cert_chain_resolver.cli certificate.crt > bundle.crtfrom stdin:$ cat certificate.crt | python -m cert_chain_resolver.cli > bundle.crtPrint the details of each certificate in resolved chain$ cert_chain_resolver cert.pem --infoDevelopmentbootstrap$ makeTestingUnit testing$ make testsRe-run tests on file changes:$ make tests TEST_ARGS="-- -f"