upstream/certbot
1
0
Fork 0
mirror of https://github.com/certbot/certbot.git synced 2026-06-19 13:39:03 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions 2
certbot/tools/venv.sh

31 lines
744 B
Bash
Raw Permalink Normal View History

Developer virtualenv bootstrap scripts.
2015-09-27 16:57:31 -04:00
#!/bin/sh -xe
Rename misc files
2016-04-14 13:20:23 -04:00
# Developer virtualenv setup for Certbot client
Developer virtualenv bootstrap scripts.
2015-09-27 16:57:31 -04:00
Choose Python for better integration with boulder
2016-04-15 15:40:37 -04:00
if command -v python2; then
export VENV_ARGS="--python python2"
elif command -v python2.7; then
export VENV_ARGS="--python python2.7"
else
echo "Couldn't find python2 or python2.7 in $PATH"
exit 1
fi
python2 and clarified coverage
2015-10-06 13:49:33 -04:00
Quick test farm fix
2016-02-10 22:09:05 -05:00
./tools/_venv_common.sh \
Clean up dev/testing extras messup (fixes #2140).
2016-01-10 13:37:41 -05:00
-e acme[dev] \
-e .[dev,docs] \
rename letshelp-letsencrypt
2016-04-13 20:42:19 -04:00
-e certbot-apache \
Cloudflare DNS Authenticator Implement an Authenticator which can fulfill a dns-01 challenge using the Cloudflare API. Applicable only for domains using Cloudflare for DNS. Testing Done: * `tox -e py27` * `tox -e lint` * Manual testing: * Used `certbot certonly --dns-cloudflare -d`, specifying a credentials file as a command line argument. Verified that a certificate was successfully obtained without user interaction. * Used `certbot certonly --dns-cloudflare -d`, without specifying a credentials file as a command line argument. Verified that the user was prompted and that a certificate was successfully obtained. * Used `certbot certonly -d`. Verified that the user was prompted for a credentials file after selecting cloudflare interactively and that a certificate was successfully obtained. * Used `certbot renew --force-renewal`. Verified that certificates were renewed without user interaction. * Negative testing: * Path to non-existent credentials file. * Credentials file with unsafe permissions (644). * Credentials file missing e-mail address. * Credentials file with blank API key. * Credentials file with incorrect e-mail address. * Credentials file with malformed API key. * Credentials file with invalid API key. * Domain name not registered to Cloudflare account.
2017-05-02 13:12:23 -04:00
-e certbot-dns-cloudflare \
CloudXNS DNS Authenticator (#4585) Implement an Authenticator which can fulfill a dns-01 challenge using the CloudXNS DNS API. Applicable only for domains using CloudXNS DNS. Testing Done: * `tox -e py27` * `tox -e lint` * Manual testing: * Used `certbot certonly --dns-cloudxns -d`, specifying a credentials file as a command line argument. Verified that a certificate was successfully obtained without user interaction. * Used `certbot certonly --dns-cloudxns -d`, without specifying a credentials file as a command line argument. Verified that the user was prompted and that a certificate was successfully obtained. * Used `certbot certonly -d`. Verified that the user was prompted for a credentials file after selecting cloudxns interactively and that a certificate was successfully obtained. * Used `certbot renew --force-renewal`. Verified that certificates were renewed without user interaction. * Negative testing: * Path to non-existent credentials file. * Credentials file with unsafe permissions (644). * Domain name not registered to CloudXNS account.
2017-05-19 19:23:53 -04:00
-e certbot-dns-cloudxns \
DigitalOcean DNS Authenticator Implement an Authenticator which can fulfill a dns-01 challenge using the DigitalOcean API. Applicable only for domains using DigitalOcean for DNS. Testing Done: * `tox -e py27` * `tox -e lint` * Manual testing: * Used `certbot certonly --dns-digitalocean -d`, specifying a credentials file as a command line argument. Verified that a certificate was successfully obtained without user interaction. * Used `certbot certonly --dns-digitalocean -d`, without specifying a credentials file as a command line argument. Verified that the user was prompted and that a certificate was successfully obtained. * Used `certbot certonly -d`. Verified that the user was prompted for a credentials file after selecting digitalocean interactively and that a certificate was successfully obtained. * Used `certbot renew --force-renewal`. Verified that certificates were renewed without user interaction. * Negative testing: * Path to non-existent credentials file. * Credentials file with unsafe permissions (644). * Credentials file missing token. * Credentials file with blank token. * Credentials file with incorrect token. * Domain name not registered to DigitalOcean account.
2017-04-28 17:53:07 -04:00
-e certbot-dns-digitalocean \
DNSimple DNS Authenticator (#4587) Implement an Authenticator which can fulfill a dns-01 challenge using the DNSimple DNS API. Applicable only for domains using DNSimple DNS. Testing Done: * `tox -e py27` * `tox -e lint` * Manual testing: * Used `certbot certonly --dns-dnsimple -d`, specifying a credentials file as a command line argument. Verified that a certificate was successfully obtained without user interaction. * Used `certbot certonly --dns-dnsimple -d`, without specifying a credentials file as a command line argument. Verified that the user was prompted and that a certificate was successfully obtained. * Used `certbot certonly -d`. Verified that the user was prompted for a credentials file after selecting dnsimple interactively and that a certificate was successfully obtained. * Used `certbot renew --force-renewal`. Verified that certificates were renewed without user interaction. * Negative testing: * Path to non-existent credentials file. * Credentials file with unsafe permissions (644). * Path to credentials file with an invalid token. * Path to credentials file without a token. * Domain name not registered to DNSimple account.
2017-05-22 20:06:04 -04:00
-e certbot-dns-dnsimple \
DNS Made Easy DNS Authenticator (#4603) Implement an Authenticator which can fulfill a dns-01 challenge using the DNS Made Easy API. Applicable only for domains using DNS Made Easy. Testing Done: * `tox -e py27` * `tox -e lint` * Manual testing: (`http://api.sandbox.dnsmadeeasy.com/V2.0` used as the `api_endpoint` for all manual testing) * Used `certbot certonly --dns-dnsmadeeasy -d`, specifying a credentials file as a command line argument. Verified that a certificate was successfully obtained without user interaction. * Negative testing: * Path to non-existent credentials file. * Credentials file with unsafe permissions (644). * Path to credentials file with an invalid API key. * Path to credentials file with a malformed API key. * Path to credentials file with an invalid Secret key. * Path to credentials file with a malformed Secret key. * Domain name not registered to DNS Made Easy account.
2017-06-15 19:41:00 -04:00
-e certbot-dns-dnsmadeeasy \
Google Cloud DNS Authenticator (#4581) Implement an Authenticator which can fulfill a dns-01 challenge using the Google Cloud DNS API. Applicable only for domains using Google Cloud DNS for DNS. Testing Done: * `tox -e py27` * `tox -e lint` * Manual testing: * Used `certbot certonly --dns-google -d`, specifying a credentials file as a command line argument. Verified that a certificate was successfully obtained without user interaction. * Used `certbot certonly --dns-google -d`, without specifying a credentials file as a command line argument. Verified that the user was prompted and that a certificate was successfully obtained. * Used `certbot certonly -d`. Verified that the user was prompted for a credentials file after selecting google interactively and that a certificate was successfully obtained. * Used `certbot renew --force-renewal`. Verified that certificates were renewed without user interaction. * Negative testing: * Path to non-existent credentials file. * Credentials file with unsafe permissions (644). * Domain name not registered to Google Cloud Platform account.
2017-05-17 14:26:26 -04:00
-e certbot-dns-google \
LuaDNS DNS Authenticator (#4605) Implement an Authenticator which can fulfill a dns-01 challenge using the LuaDNS API. Applicable only for domains using LuaDNS for DNS. Testing Done: * `tox -e py27` * `tox -e lint` * Manual testing: * Used `certbot certonly --dns-luadns -d`, specifying a credentials file as a command line argument. Verified that a certificate was successfully obtained without user interaction. * Negative testing: * Path to non-existent credentials file. * Credentials file with unsafe permissions (644). * Path to credentials file without an email. * Path to credentials file with an invalid email. * Path to credentials file without a token. * Path to credentials file with an invalid token. * Domain name not registered to LuaDNS account.
2017-06-16 17:43:12 -04:00
-e certbot-dns-luadns \
NS1 DNS Authenticator (#4602) Implement an Authenticator which can fulfill a dns-01 challenge using the NS1 DNS API. Applicable only for domains using NS1 DNS. Testing Done: * `tox -e py27` * `tox -e lint` * Manual testing: * Used `certbot certonly --dns-nsone -d`, specifying a credentials file as a command line argument. Verified that a certificate was successfully obtained without user interaction. * Used `certbot certonly --dns-nsone -d`, without specifying a credentials file as a command line argument. Verified that the user was prompted and that a certificate was successfully obtained. * Used `certbot certonly -d`. Verified that the user was prompted for a credentials file after selecting dnsimple interactively and that a certificate was successfully obtained. * Used `certbot renew --force-renewal`. Verified that certificates were renewed without user interaction. * Negative testing: * Path to non-existent credentials file. * Credentials file with unsafe permissions (644). * Path to credentials file with an invalid token. * Path to credentials file without a token. * Domain name not registered to NS1 account.
2017-05-26 14:24:38 -04:00
-e certbot-dns-nsone \
RFC 2136 DNS Authenticator (#4701) Introduce a plugin that automates the process of completing a dns-01 challenge by creating, and subsequently removing, TXT records using RFC 2136 Dynamic Updates (a.k.a. nsupdate). This plugin has been tested with BIND, but may work with other RFC 2136-compatible DNS servers, such as PowerDNS.
2017-06-16 19:53:46 -04:00
-e certbot-dns-rfc2136 \
route53: rename to match other DNS plugins (#4747) This change renames certbot-route53 to certbot-dns-route53 and updates the package's setup.py file to maintain backwards compatibility. Testing Done: * Run `certbot` with `-a certbot-route53:auth`, verify the plugin runs. * Run `certbot` with `--dns-route53`, verify the plugin runs.
2017-06-06 18:41:04 -04:00
-e certbot-dns-route53 \
rename letshelp-letsencrypt
2016-04-13 20:42:19 -04:00
-e certbot-nginx \
Add certbot-postfix to tools pep8ify Delint cover++ test more_info() Refactor get_config_var Don't duplicate changes to Postfix config document instance variables Always clear save_notes on save Test deploy_cert and save and add MockPostfix. Move mock and call to InstallerTest Add getters and setters Use postfix getters and setters protect get_config_var bump cover to 100% bump required coverage to 100 s/config_dir/config_utility Decrease minimum version to Postfix 2.6. This is the minimum version that allows us to set ciphers to be used with opportunistic TLS and is the oldest version packaged in any major distro. Use tls_security_level instead of use_tls. smtpd_tls_security_level should be used instead according to Postfix documentation. Test smtpd_tls_security_level conditional make dunder method an under method refactor postconf usage add check_all_output test check_all_output Add and test verify_exe_exists Add PostfixUtilBase Add ReadOnlyMainMap Use _get_output instead of _call Fix split strip typo
2017-08-24 19:08:47 -04:00
-e certbot-postfix \
rename letshelp-letsencrypt
2016-04-13 20:42:19 -04:00
-e letshelp-certbot \
-e certbot-compatibility-test
Reference in a new issue Copy permalink