| Port details |
- py-letsencrypt Let's Encrypt client
- 0.5.0,1 security
 =5      0.5.0,1Version of this port present on the latest quarterly branch. - Maintainer: koobs@FreeBSD.org
- Port Added: 2015-11-06 08:38:43
- Last Update: 2016-06-23 10:22:35
- SVN Revision: 417359
- People watching this port, also watch:: python27, nginx, pkg, git
- Also Listed In: python
- License: APACHE20
- WWW:
- https://github.com/letsencrypt/letsencrypt
- Description:
- In short: getting and installing SSL/TLS certificates made easy.
The Let's Encrypt Client is a tool to automatically receive and install
X.509 certificates to enable TLS on servers. The client will
interoperate with the Let's Encrypt CA which will be issuing
browser-trusted certificates for free.
It's all automated:
The tool will prove domain control to the CA and submit a CSR
(Certificate Signing Request).
If domain control has been proven, a certificate will get issued and
the tool will automatically install it.
WWW: https://github.com/letsencrypt/letsencrypt
 cgit ¦ GitHub ¦ GitHub ¦ GitLab ¦ 
- Manual pages:
- FreshPorts has no man page information for this port.
- pkg-plist: as obtained via:
make generate-plist - There is no configure plist information for this port.
- Dependency lines:
-
- ${PYTHON_PKGNAMEPREFIX}letsencrypt>0:security/py-letsencrypt@${PY_FLAVOR}
- No installation instructions:
- This port has been deleted.
- PKGNAME: py27-letsencrypt
- Flavors: there is no flavor information for this port.
- distinfo:
- There is no distinfo for this port.
No package information for this port in our database- Sometimes this happens. Not all ports have packages. Perhaps there is a build error. Check the fallout link:
- Dependencies
- NOTE: FreshPorts displays only information on required and default dependencies. Optional dependencies are not covered.
- Build dependencies:
-
- py27-setuptools27>0 : devel/py-setuptools27
- python2.7 : lang/python27
- Runtime dependencies:
-
- py27-acme==0.5.0,1 : security/py-acme
- py27-configargparse>=0.9.3 : devel/py-configargparse
- py27-configobj>0 : devel/py-configobj
- py27-cryptography>=0.7 : security/py-cryptography
- py27-parsedatetime>0 : devel/py-parsedatetime
- py27-psutil>=2.1.0 : sysutils/py-psutil
- py27-openssl>0 : security/py-openssl
- py27-pyrfc3339>0 : devel/py-pyrfc3339
- py27-python2-pythondialog>=3.2.2r1 : devel/py-python2-pythondialog
- py27-pytz>0 : devel/py-pytz
- py27-setuptools27>0 : devel/py-setuptools27
- py27-six>0 : devel/py-six
- py27-zope.component>0 : devel/py-zope.component
- py27-zope.interface>0 : devel/py-zope.interface
- py27-mock>0 : devel/py-mock
- py27-setuptools27>0 : devel/py-setuptools27
- python2.7 : lang/python27
- There are no ports dependent upon this port
Configuration Options:- No options to configure
- Options name:
- N/A
- USES:
- python:-2.7
- pkg-message:
- ===========================================================================
The Let's Encrypt Client is BETA SOFTWARE. It contains plenty of bugs and
rough edges, and should be tested thoroughly in staging environments before
use on production systems.
This port installs the "standalone" Python client only, which does not use and
is not the letsencrypt-auto bootstrap/wrapper script.
To obtain certificates, use the 'certonly' command as follows:
# sudo letsencrypt --server <server-URL> certonly
Note: The client currently requires the ability to bind on TCP port 80. If
you have a server running on this port, it will need to be temporarily stopped
so that the standalone server can listen on that port to complete
authentication.
The letsencrypt plugins to support apache and nginx certificate installation
will be made available soon in the following ports:
* Apache plugin: security/py-letsencrypt-apache
* Nginx plugin: security/py-letsencrypt-nginx
===========================================================================
- Master Sites:
|
| Commit History - (may be incomplete: for full details, see links to repositories near top of page) |
| Commit | Credits | Log message |
|---|
0.5.0,1
23 Jun 2016 10:22:35
  |
brnrd |
security/py-certbot: Rename from py-letsencrypt and update
- Move security/py-letsencrypt to security/py-certbot
- Update security/py-acme to 0.8.1
- Update security/py-certbot to 0.8.1
- Update python dependencies
PR: 209584 |
0.5.0,1
09 Jun 2016 18:13:54
|
mat |
Typo.
Github: #43
Submitted by: Attila Gyorffy
Sponsored by: Absolight |
0.5.0,1
17 May 2016 16:13:32
|
cpm |
- Fix "properly" RUN_DEPENDS on security/py-acme
Reported by: gahr
Approved by: koobs (maintainer) |
0.5.0,1
17 May 2016 16:01:31
|
cpm |
- Bump PORTEPOCH
- Fix RUN_DEPENDS on security/py-acme
Reported by: gahr
Approved by: koobs (maintainer) |
0.5.0
08 Apr 2016 04:16:07
|
cpm |
- Update to 0.5.0
Approved by: junovitch (mentor), koobs (maintainer, letsencrypt) |
0.4.2
03 Apr 2016 04:48:22
|
cpm |
security/py-{letsencrypt,acme}: Update to 0.4.2
- Update py-acme and py-letsencrypt ports.
Approved by: koobs (maintainer, letsencrypt) |
0.4.1
01 Apr 2016 14:25:18
|
mat |
Remove ${PORTSDIR}/ from dependencies, categories r, s, t, and u.
With hat: portmgr
Sponsored by: Absolight |
0.4.1
03 Mar 2016 05:42:15
|
cpm |
Common:
- Update PORTVERSION and distinfo checksum (0.4.1)
security/py-acme:
- Update MAINTAINER to my @FreeBSD.org address
PR: 207666
Approved by: junovitch (mentor), koobs (maintainer, letsencrypt) |
0.4.0
26 Feb 2016 12:41:45
|
koobs |
security/py-{acme,letsencrypt}: Update to 0.4.0
Common:
- Update PORTVERSION and distinfo checksum (0.4.0) [1]
- Update and sort RUN_DEPENDS to match setup.py:install_requires
security/py-acme:
- Update COMMENT to match setup.py:description=
- Add LICENSE_FILE
- Remove spurious USES=gmake dependency
PR: 207306 [1]
Submitted by: Piotr Kubaj <pkubaj anongoth pl> [1]
Approved by: koobs (maintainer, letsencrypt), cpm (maintainer, acme) |
0.3.0
02 Feb 2016 12:34:09
|
koobs |
security/py-{letsencrypt,acme}: Update to 0.3.0
Common:
- Update PORTVERSION and distinfo checksum (0.3.0) [1]
- Use PORTVERSION over DISTVERSION (not necessary at the moment)
- Update dependency entries to match those in setup.py
- match minimum versions, remove version if not specified there
- requests has been removed from letsencrypt, acme depends on it
py-letsecnrypt:
- Remove setup.py patch (upstreamed) [1]
py-acme:
- Enable NO_ARCH
PR: 206397
Submitted by: pkubaj@anongoth.pl [1]
Reviewed by: cpm (maintainer, acme)
Approved by: cpm (maintainer, acme) |
0.1.0
05 Dec 2015 11:08:46
|
brnrd |
security/py-letsencrypt: Update to 0.1.0
- Update py-letsencrypt to 0.1.0
- Update py-acme to 0.1.0
- Update pkg-message accordingly
This marks the first non-development release of Letsencrypt.org for the public
BETA
Reviewed by: koobs (mentor, maintainer), cpm_fbsd.es (maintainer), feld
Approved by: koobs (mentor, maintainer), cpm_fbsd.es (maintainer), feld
MFH: 2015Q4
Differential Revision: https://reviews.freebsd.org/D4360 |
0.0.0.d20151123
30 Nov 2015 13:56:54
|
brnrd |
security/py-letsencrypt: Update to 2015-11-23 version
- Update acme and letsencrypt ports
- Switch security/py-acme to PyPI download
Reviewed By: koobs (mentor, maintainer), cpm_fbsd.es (maintainer)
Approved By: koobs (mentor, maintainer), cpm_fbsd.es (maintainer)
Differential Revision: https://reviews.freebsd.org/D4313 |
0.0.0.d20151114
20 Nov 2015 09:03:43
|
sunpoet |
- Update distinfo (missing in r401990)
Approved by: portmgr (blanket) |
0.0.0.d20151114
20 Nov 2015 08:16:19
|
brnrd |
security/py-letsencrypt: Update to version 20151114
- Update py-letsencrypt and py-acme (to v0.0.0dev20151114)
- Add regression test target for py-acme
Changes:
- Turn off old/insecure challenge types[1]
[1]:
https://community.letsencrypt.org/t/turning-off-old-insecure-challenge-types/3825
Reviewed by: koobs (mentor), Carlos J Puga Medina <cpm@fbsd.es> (maintainer)
Approved by: koobs (mentor, maintainer), Carlos J Puga Medina <cpm@fbsd.es>
(maintainer)
DifferentialRevision: https://reviews.freebsd.org/D4162 |
0.0.0.d20151104
06 Nov 2015 08:38:34
|
koobs |
[NEW] security/py-letsencrypt: Welcome Let's Encrypt client!
In short: getting and installing SSL/TLS certificates made easy.
The Let's Encrypt Client is a tool to automatically receive and install
X.509 certificates to enable TLS on servers. The client will
interoperate with the Let's Encrypt CA which will be issuing
browser-trusted certificates for free.
It's all automated:
The tool will prove domain control to the CA and submit a CSR
(Certificate Signing Request).
If domain control has been proven, a certificate will get issued and
the tool will automatically install it.
WWW: https://github.com/letsencrypt/letsencrypt
PR: 203405 |
As an Amazon Associate I earn from qualifying purchases.