Certificats Let's Encrypt
Find a file
Brad Warren edbb3a73c6 Take advantage of urllib3 pyopenssl rewrite (#3805)
* pin requests version in py26-oldest

* Determine requests security deps dynamically

Starting with requests 2.12, pyasn1 and ndg-httpsclient are no longer
needed to inject pyopenssl into urllib3. This change allows us to
determine whether or not these dependencies are required at install
time. If an older version of requests is used, these packages are
still installed. If a new version of requests is used, they are not
reducing the number of dependencies we have.

* Bump requests version in certbot-auto

* Use pkg_resources in activate test

Due to pip's lack of dependency resolution, the change to use
requests[extras] causes errors in acme.util_test because pkg_resources
accurately detects the "missing" dependency.

There isn't a real problem here. The problem comes from a brand new
requests and ancient pyopenssl as well as a unit test for
functionality we plan to remove in our next release. I modified
the unit test to fix the problem for now.

* Use six instead of pkg_resources for test

* Require requests<=2.11.1 in py27-oldest test

If we don't do this, we get test failures for the certbot package
which is actually a good thing! pkg_resources is catching the
unlikely but possible problem I describe in #3803 and erroring out
saying it is missing the necessary dependencies to run certbot.
Good job package resources.

* Undo changes to acme.util_test
2016-12-01 10:47:08 -08:00
acme Take advantage of urllib3 pyopenssl rewrite (#3805) 2016-12-01 10:47:08 -08:00
certbot Warn early if a selected enhancement is unsupported by the current plugin (#3688) 2016-11-30 10:50:16 -08:00
certbot-apache Remove get_all_certs_keys() from Apache and Nginx (#3768) 2016-11-08 17:19:05 -08:00
certbot-compatibility-test No doc,dev depedencies for compatibility-test (#3722) 2016-10-31 18:30:02 -07:00
certbot-nginx Remove get_all_certs_keys() from Apache and Nginx (#3768) 2016-11-08 17:19:05 -08:00
docs Remove the sphinxcontrib.programout [docs]dependency (#3830) 2016-11-30 10:47:10 -08:00
examples Rename misc files 2016-04-14 10:20:23 -07:00
letsencrypt-auto-source Take advantage of urllib3 pyopenssl rewrite (#3805) 2016-12-01 10:47:08 -08:00
letshelp-certbot Bump version to 0.7.0 2016-05-11 18:04:27 -07:00
tests Testing the output of build.py against lea-source/lea (#3460) 2016-10-28 10:50:07 -07:00
tools Remove the sphinxcontrib.programout [docs]dependency (#3830) 2016-11-30 10:47:10 -08:00
.coveragerc Show lines missing test coverage in test output 2016-06-17 10:48:54 -07:00
.dockerignore Update ignore files to remove shared tox.venv 2015-07-12 15:30:51 +00:00
.gitattributes Merge pull request #2136 from tboegi/gitattributes_eol_overrideses_auto 2016-06-16 14:29:39 -07:00
.gitignore Add rope directory to gitignore (#3554) 2016-09-28 10:42:00 -07:00
.pep8 nit: fix missing EOF newline 2015-09-06 09:27:39 +00:00
.pylintrc Fight with cyclic lint 2016-03-10 18:54:03 -08:00
.travis.yml Expanding tests for le-auto, adding CentOS test suite (#2671) 2016-11-10 15:05:03 -08:00
certbot-auto Release 0.9.3 Option 2 (see #3634) (#3635) 2016-10-15 10:10:01 -07:00
CHANGES.rst Improve CHANGES.rst. (#3541) 2016-09-27 12:08:32 -07:00
CONTRIBUTING.md Update CONTRIBUTING.md to be more welcoming. (#3540) 2016-09-26 16:44:27 -07:00
docker-compose.yml Rename misc files 2016-04-14 10:20:23 -07:00
Dockerfile Error/Warning with build docker container from Dockerfile (#3004) 2016-05-18 16:35:17 -07:00
Dockerfile-dev More stray ncrypt reference cleanup 2016-04-14 17:04:23 -07:00
letsencrypt-auto Release 0.9.3 Option 2 (see #3634) (#3635) 2016-10-15 10:10:01 -07:00
LICENSE.txt More stray ncrypt reference cleanup 2016-04-14 17:04:23 -07:00
linter_plugin.py Rename misc files 2016-04-14 10:20:23 -07:00
MANIFEST.in Rename misc files 2016-04-14 10:20:23 -07:00
pep8.travis.sh Improve user experience for linting. 2016-06-04 22:53:51 -07:00
README.rst I restructured Installation and Using a bit (#3725) 2016-11-01 14:25:26 -07:00
readthedocs.org.requirements.txt RTD: install local deps for subpkgs (fixes #1086). 2015-10-23 19:01:13 +00:00
setup.cfg setup.cfg 2016-04-14 17:13:19 -07:00
setup.py Remove the sphinxcontrib.programout [docs]dependency (#3830) 2016-11-30 10:47:10 -08:00
tox.cover.sh rename letshelp-letsencrypt 2016-04-13 17:42:19 -07:00
tox.ini Take advantage of urllib3 pyopenssl rewrite (#3805) 2016-12-01 10:47:08 -08:00
Vagrantfile Remove the curses dialog, thereby deprecating the --help and --dialog command line options (#3665) 2016-10-21 15:45:57 -07:00

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

.. This file contains a series of comments that are used to include sections of this README in other files. Do not modify these comments unless you know what you are doing. tag:intro-begin

Certbot is part of EFFs effort to encrypt the entire Internet. Secure communication over the Web relies on HTTPS, which requires the use of a digital certificate that lets browsers verify the identify of web servers (e.g., is that really google.com?). Web servers obtain their certificates from trusted third parties called certificate authorities (CAs). Certbot is an easy-to-use client that fetches a certificate from Lets Encrypt—an open certificate authority launched by the EFF, Mozilla, and others—and deploys it to a web server.

Anyone who has gone through the trouble of setting up a secure website knows what a hassle getting and maintaining a certificate is. Certbot and Lets Encrypt can automate away the pain and let you turn on and manage HTTPS with simple commands. Using Certbot and Let's Encrypt is free, so theres no need to arrange payment.

How you use Certbot depends on the configuration of your web server. The best way to get started is to use our `interactive guide <https://certbot.eff.org>`_. It generates instructions based on your configuration settings. In most cases, youll need `root or administrator access <https://certbot.eff.org/faq/#does-certbot-require-root-privileges>`_ to your web server to run Certbot.

If youre using a hosted service and dont have direct access to your web server, you might not be able to use Certbot. Check with your hosting provider for documentation about uploading certificates or using certificates issues by Lets Encrypt.

Certbot is a fully-featured, extensible client for the Let's
Encrypt CA (or any other CA that speaks the `ACME
<https://github.com/ietf-wg-acme/acme/blob/master/draft-ietf-acme-acme.md>`_
protocol) that can automate the tasks of obtaining certificates and
configuring webservers to use them. This client runs on Unix-based operating
systems.

Until May 2016, Certbot was named simply ``letsencrypt`` or ``letsencrypt-auto``,
depending on install method. Instructions on the Internet, and some pieces of the
software, may still refer to this older name.

Contributing
------------

If you'd like to contribute to this project please read `Developer Guide
<https://certbot.eff.org/docs/contributing.html>`_.

.. _installation:

Installation
------------

The easiest way to install Certbot is by visiting `certbot.eff.org`_, where you can
find the correct installation instructions for many web server and OS combinations.
For more information, see `Get Certbot <https://certbot.eff.org/docs/install.html>`_.

.. _certbot.eff.org: https://certbot.eff.org/

How to run the client
---------------------

In many cases, you can just run ``certbot-auto`` or ``certbot``, and the
client will guide you through the process of obtaining and installing certs
interactively.

For full command line help, you can type::

  ./certbot-auto --help all


You can also tell it exactly what you want it to do from the command line.
For instance, if you want to obtain a cert for ``example.com``,
``www.example.com``, and ``other.example.net``, using the Apache plugin to both
obtain and install the certs, you could do this::

  ./certbot-auto --apache -d example.com -d www.example.com -d other.example.net

(The first time you run the command, it will make an account, and ask for an
email and agreement to the Let's Encrypt Subscriber Agreement; you can
automate those with ``--email`` and ``--agree-tos``)

If you want to use a webserver that doesn't have full plugin support yet, you
can still use "standalone" or "webroot" plugins to obtain a certificate::

  ./certbot-auto certonly --standalone --email admin@example.com -d example.com -d www.example.com -d other.example.net


Understanding the client in more depth
--------------------------------------

To understand what the client is doing in detail, it's important to
understand the way it uses plugins.  Please see the `explanation of
plugins <https://certbot.eff.org/docs/using.html#plugins>`_ in
the User Guide.

Links
=====

.. Do not modify this comment unless you know what you're doing. tag:links-begin

Documentation: https://certbot.eff.org/docs

Software project: https://github.com/certbot/certbot

Notes for developers: https://certbot.eff.org/docs/contributing.html

Main Website: https://certbot.eff.org

Let's Encrypt Website: https://letsencrypt.org

IRC Channel: #letsencrypt on `Freenode`_ or #certbot on `OFTC`_

Community: https://community.letsencrypt.org

ACME spec: http://ietf-wg-acme.github.io/acme/

ACME working area in github: https://github.com/ietf-wg-acme/acme


Mailing list: `client-dev`_ (to subscribe without a Google account, send an
email to client-dev+subscribe@letsencrypt.org)

|build-status| |coverage| |docs| |container|

.. _Freenode: https://webchat.freenode.net?channels=%23letsencrypt

.. _OFTC: https://webchat.oftc.net?channels=%23certbot

.. _client-dev: https://groups.google.com/a/letsencrypt.org/forum/#!forum/client-dev

.. |build-status| image:: https://travis-ci.org/certbot/certbot.svg?branch=master
   :target: https://travis-ci.org/certbot/certbot
   :alt: Travis CI status

.. |coverage| image:: https://coveralls.io/repos/certbot/certbot/badge.svg?branch=master
   :target: https://coveralls.io/r/certbot/certbot
   :alt: Coverage status

.. |docs| image:: https://readthedocs.org/projects/letsencrypt/badge/
   :target: https://readthedocs.org/projects/letsencrypt/
   :alt: Documentation status

.. |container| image:: https://quay.io/repository/letsencrypt/letsencrypt/status
   :target: https://quay.io/repository/letsencrypt/letsencrypt
   :alt: Docker Repository on Quay.io

.. Do not modify this comment unless you know what you're doing. tag:links-end

System Requirements
===================

The Let's Encrypt Client presently only runs on Unix-ish OSes that include
Python 2.6 or 2.7; Python 3.x support will hopefully be added in the future. The
client requires root access in order to write to ``/etc/letsencrypt``,
``/var/log/letsencrypt``, ``/var/lib/letsencrypt``; to bind to ports 80 and 443
(if you use the ``standalone`` plugin) and to read and modify webserver
configurations (if you use the ``apache`` or ``nginx`` plugins).  If none of
these apply to you, it is theoretically possible to run without root privileges,
but for most users who want to avoid running an ACME client as root, either
`letsencrypt-nosudo <https://github.com/diafygi/letsencrypt-nosudo>`_ or
`simp_le <https://github.com/kuba/simp_le>`_ are more appropriate choices.

The Apache plugin currently requires a Debian-based OS with augeas version
1.0; this includes Ubuntu 12.04+ and Debian 7+.

.. Do not modify this comment unless you know what you're doing. tag:intro-end

.. Do not modify this comment unless you know what you're doing. tag:features-begin

Current Features
=====================

* Supports multiple web servers:

  - apache/2.x (beta support for auto-configuration)
  - nginx/0.8.48+ (alpha support for auto-configuration)
  - 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 via `third party plugins <https://certbot.eff.org/docs/using.html#third-party-plugins>`_

* The 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 ncurses and text (-t) UI, or can be driven entirely from the
  command line.
* Free and Open Source Software, made with Python.

.. Do not modify this comment unless you know what you're doing. tag:features-end

For extensive documentation on using and contributing to Certbot, go to https://certbot.eff.org/docs. If you would like to contribute to the project or run the latest code from git, you should read our `developer guide <https://certbot.eff.org/docs/contributing.html>`_.