pylego 0.1.0__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- pylego-0.1.0/LICENSE +201 -0
- pylego-0.1.0/PKG-INFO +76 -0
- pylego-0.1.0/README.md +61 -0
- pylego-0.1.0/pyproject.toml +66 -0
- pylego-0.1.0/setup.cfg +4 -0
- pylego-0.1.0/setup.py +26 -0
- pylego-0.1.0/src/pylego/__init__.py +1 -0
- pylego-0.1.0/src/pylego/lego.so +0 -0
- pylego-0.1.0/src/pylego/pylego.py +68 -0
- pylego-0.1.0/src/pylego.egg-info/PKG-INFO +76 -0
- pylego-0.1.0/src/pylego.egg-info/SOURCES.txt +12 -0
- pylego-0.1.0/src/pylego.egg-info/dependency_links.txt +1 -0
- pylego-0.1.0/src/pylego.egg-info/requires.txt +4 -0
- pylego-0.1.0/src/pylego.egg-info/top_level.txt +1 -0
pylego-0.1.0/LICENSE
ADDED
|
@@ -0,0 +1,201 @@
|
|
|
1
|
+
Apache License
|
|
2
|
+
Version 2.0, January 2004
|
|
3
|
+
http://www.apache.org/licenses/
|
|
4
|
+
|
|
5
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
6
|
+
|
|
7
|
+
1. Definitions.
|
|
8
|
+
|
|
9
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
10
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
11
|
+
|
|
12
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
13
|
+
the copyright owner that is granting the License.
|
|
14
|
+
|
|
15
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
16
|
+
other entities that control, are controlled by, or are under common
|
|
17
|
+
control with that entity. For the purposes of this definition,
|
|
18
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
19
|
+
direction or management of such entity, whether by contract or
|
|
20
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
21
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
22
|
+
|
|
23
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
24
|
+
exercising permissions granted by this License.
|
|
25
|
+
|
|
26
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
27
|
+
including but not limited to software source code, documentation
|
|
28
|
+
source, and configuration files.
|
|
29
|
+
|
|
30
|
+
"Object" form shall mean any form resulting from mechanical
|
|
31
|
+
transformation or translation of a Source form, including but
|
|
32
|
+
not limited to compiled object code, generated documentation,
|
|
33
|
+
and conversions to other media types.
|
|
34
|
+
|
|
35
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
36
|
+
Object form, made available under the License, as indicated by a
|
|
37
|
+
copyright notice that is included in or attached to the work
|
|
38
|
+
(an example is provided in the Appendix below).
|
|
39
|
+
|
|
40
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
41
|
+
form, that is based on (or derived from) the Work and for which the
|
|
42
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
43
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
44
|
+
of this License, Derivative Works shall not include works that remain
|
|
45
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
46
|
+
the Work and Derivative Works thereof.
|
|
47
|
+
|
|
48
|
+
"Contribution" shall mean any work of authorship, including
|
|
49
|
+
the original version of the Work and any modifications or additions
|
|
50
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
51
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
52
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
53
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
54
|
+
means any form of electronic, verbal, or written communication sent
|
|
55
|
+
to the Licensor or its representatives, including but not limited to
|
|
56
|
+
communication on electronic mailing lists, source code control systems,
|
|
57
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
58
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
59
|
+
excluding communication that is conspicuously marked or otherwise
|
|
60
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
61
|
+
|
|
62
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
63
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
64
|
+
subsequently incorporated within the Work.
|
|
65
|
+
|
|
66
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
67
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
68
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
69
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
70
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
71
|
+
Work and such Derivative Works in Source or Object form.
|
|
72
|
+
|
|
73
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
74
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
75
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
76
|
+
(except as stated in this section) patent license to make, have made,
|
|
77
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
78
|
+
where such license applies only to those patent claims licensable
|
|
79
|
+
by such Contributor that are necessarily infringed by their
|
|
80
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
81
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
82
|
+
institute patent litigation against any entity (including a
|
|
83
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
84
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
85
|
+
or contributory patent infringement, then any patent licenses
|
|
86
|
+
granted to You under this License for that Work shall terminate
|
|
87
|
+
as of the date such litigation is filed.
|
|
88
|
+
|
|
89
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
90
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
91
|
+
modifications, and in Source or Object form, provided that You
|
|
92
|
+
meet the following conditions:
|
|
93
|
+
|
|
94
|
+
(a) You must give any other recipients of the Work or
|
|
95
|
+
Derivative Works a copy of this License; and
|
|
96
|
+
|
|
97
|
+
(b) You must cause any modified files to carry prominent notices
|
|
98
|
+
stating that You changed the files; and
|
|
99
|
+
|
|
100
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
101
|
+
that You distribute, all copyright, patent, trademark, and
|
|
102
|
+
attribution notices from the Source form of the Work,
|
|
103
|
+
excluding those notices that do not pertain to any part of
|
|
104
|
+
the Derivative Works; and
|
|
105
|
+
|
|
106
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
107
|
+
distribution, then any Derivative Works that You distribute must
|
|
108
|
+
include a readable copy of the attribution notices contained
|
|
109
|
+
within such NOTICE file, excluding those notices that do not
|
|
110
|
+
pertain to any part of the Derivative Works, in at least one
|
|
111
|
+
of the following places: within a NOTICE text file distributed
|
|
112
|
+
as part of the Derivative Works; within the Source form or
|
|
113
|
+
documentation, if provided along with the Derivative Works; or,
|
|
114
|
+
within a display generated by the Derivative Works, if and
|
|
115
|
+
wherever such third-party notices normally appear. The contents
|
|
116
|
+
of the NOTICE file are for informational purposes only and
|
|
117
|
+
do not modify the License. You may add Your own attribution
|
|
118
|
+
notices within Derivative Works that You distribute, alongside
|
|
119
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
120
|
+
that such additional attribution notices cannot be construed
|
|
121
|
+
as modifying the License.
|
|
122
|
+
|
|
123
|
+
You may add Your own copyright statement to Your modifications and
|
|
124
|
+
may provide additional or different license terms and conditions
|
|
125
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
126
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
127
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
128
|
+
the conditions stated in this License.
|
|
129
|
+
|
|
130
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
131
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
132
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
133
|
+
this License, without any additional terms or conditions.
|
|
134
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
135
|
+
the terms of any separate license agreement you may have executed
|
|
136
|
+
with Licensor regarding such Contributions.
|
|
137
|
+
|
|
138
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
139
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
140
|
+
except as required for reasonable and customary use in describing the
|
|
141
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
142
|
+
|
|
143
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
144
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
145
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
146
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
147
|
+
implied, including, without limitation, any warranties or conditions
|
|
148
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
149
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
150
|
+
appropriateness of using or redistributing the Work and assume any
|
|
151
|
+
risks associated with Your exercise of permissions under this License.
|
|
152
|
+
|
|
153
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
154
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
155
|
+
unless required by applicable law (such as deliberate and grossly
|
|
156
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
157
|
+
liable to You for damages, including any direct, indirect, special,
|
|
158
|
+
incidental, or consequential damages of any character arising as a
|
|
159
|
+
result of this License or out of the use or inability to use the
|
|
160
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
161
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
162
|
+
other commercial damages or losses), even if such Contributor
|
|
163
|
+
has been advised of the possibility of such damages.
|
|
164
|
+
|
|
165
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
166
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
167
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
168
|
+
or other liability obligations and/or rights consistent with this
|
|
169
|
+
License. However, in accepting such obligations, You may act only
|
|
170
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
171
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
172
|
+
defend, and hold each Contributor harmless for any liability
|
|
173
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
174
|
+
of your accepting any such warranty or additional liability.
|
|
175
|
+
|
|
176
|
+
END OF TERMS AND CONDITIONS
|
|
177
|
+
|
|
178
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
179
|
+
|
|
180
|
+
To apply the Apache License to your work, attach the following
|
|
181
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
182
|
+
replaced with your own identifying information. (Don't include
|
|
183
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
184
|
+
comment syntax for the file format. We also recommend that a
|
|
185
|
+
file or class name and description of purpose be included on the
|
|
186
|
+
same "printed page" as the copyright notice for easier
|
|
187
|
+
identification within third-party archives.
|
|
188
|
+
|
|
189
|
+
Copyright 2024 Canonical Ltd.
|
|
190
|
+
|
|
191
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
192
|
+
you may not use this file except in compliance with the License.
|
|
193
|
+
You may obtain a copy of the License at
|
|
194
|
+
|
|
195
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
196
|
+
|
|
197
|
+
Unless required by applicable law or agreed to in writing, software
|
|
198
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
199
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
200
|
+
See the License for the specific language governing permissions and
|
|
201
|
+
limitations under the License.
|
pylego-0.1.0/PKG-INFO
ADDED
|
@@ -0,0 +1,76 @@
|
|
|
1
|
+
Metadata-Version: 2.1
|
|
2
|
+
Name: pylego
|
|
3
|
+
Version: 0.1.0
|
|
4
|
+
Summary: A python wrapper package for the lego application written in Golang
|
|
5
|
+
Author-email: Ghislain Bourgeois <ghislain.bourgeois@canonical.com>, Kayra Gemalmaz <kayra.gemalmaz@canonical.com>, Daniel Arndt <daniel.arndt@canonical.com>, Guillaume Belanger <guillaume.belanger@canonical.com>, Yazan Salti <yazan.salti@canonical.com>
|
|
6
|
+
Project-URL: Homepage, https://github.com/canonical/pylego
|
|
7
|
+
Project-URL: Issues, https://github.com/canonical/pylego/issues
|
|
8
|
+
Classifier: Programming Language :: Python :: 3
|
|
9
|
+
Classifier: License :: OSI Approved :: Apache Software License
|
|
10
|
+
Classifier: Operating System :: OS Independent
|
|
11
|
+
Requires-Python: >=3.8
|
|
12
|
+
Description-Content-Type: text/markdown
|
|
13
|
+
Provides-Extra: test
|
|
14
|
+
License-File: LICENSE
|
|
15
|
+
|
|
16
|
+
# pylego
|
|
17
|
+
|
|
18
|
+
pylego is a python extension package to utilize the certificate management application [Lego](https://github.com/go-acme/lego) written in Golang in python.
|
|
19
|
+
|
|
20
|
+
## Installation
|
|
21
|
+
|
|
22
|
+
To install this package, all you need to do is run
|
|
23
|
+
|
|
24
|
+
```
|
|
25
|
+
pip install .
|
|
26
|
+
```
|
|
27
|
+
|
|
28
|
+
in your preferred Python venv.
|
|
29
|
+
|
|
30
|
+
## Usage
|
|
31
|
+
|
|
32
|
+
You can import the lego command and run any function that you can run from the CLI:
|
|
33
|
+
|
|
34
|
+
```python
|
|
35
|
+
from pylego import run_lego_command
|
|
36
|
+
test_env = {"NAMECHEAP_API_USER": "user", "NAMECHEAP_API_KEY": "key"}
|
|
37
|
+
run_lego_command("something@gmail.com", "https://localhost/directory", "-----BEGIN CERTIFICATE REQUEST----- ...", "namecheap", test_env)
|
|
38
|
+
```
|
|
39
|
+
|
|
40
|
+
| Argument | Description |
|
|
41
|
+
| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
|
|
42
|
+
| `email` | The provided email will be registered to LetsEncrypt. It may receive some emails notifying the user about certificate expiry. |
|
|
43
|
+
| `server` | This is the full URL of a server that implements the ACME protocol. While letsencrypt is the most common one, there are other programs that provide this facility like Vault. |
|
|
44
|
+
| `csr` | This must be a PEM string in bytes that is user generated and valid as according to the ACME server that is being provided above. Many providers have different requirements for what is allowed to be in the fields of the CSR. |
|
|
45
|
+
| `plugin` | The plugin is a string that's supported by LEGO. The full list is located [here](https://go-acme.github.io/lego/dns/). On top of the LEGO provided ones, we have an extra plugin called `http` that will allow users to use HTTP01 and TLSALPN01 challenges. |
|
|
46
|
+
| `env` | The env is a dictionary mapping of strings to strings that will be loaded into the environment for LEGO to use. All plugins require some configuration values loaded into the environment. You can find them [here](https://go-acme.github.io/lego/dns/) |
|
|
47
|
+
|
|
48
|
+
On top of the environment variables that LEGO supports, we have some extra ones that we use to configure the library:
|
|
49
|
+
|
|
50
|
+
| Key | Description |
|
|
51
|
+
| ----------------- | ----------------------------------------------------------------------------------------------------------------------------- |
|
|
52
|
+
| `SSL_CERT_FILE` | Path to a CA certificate file for pylego to trust. This can be used for trusting the certificate of the ACME server provided. |
|
|
53
|
+
| `HTTP01_IFACE` | The interface to be used for the HTTP01 challenge if the plugin is chosen. Any interface by default. |
|
|
54
|
+
| `HTTP01_PORT` | The port to be used for the HTTP01 challenge if the plugin is chosen. 80 by default. |
|
|
55
|
+
| `TLSALPN01_IFACE` | The interface to be used for the TLSALPN01 challenge if the plugin is chosen. Any interface by default. |
|
|
56
|
+
| `TLSALPN01_PORT` | The port to be used for the TLSALPN01 challenge if the plugin is chosen. 443 by default. |
|
|
57
|
+
|
|
58
|
+
## How does it work?
|
|
59
|
+
|
|
60
|
+
Golang supports building a shared c library from its CLI build tool. We import and use the LEGO application from GoLang, and provide a stub with C bindings so that the shared C binary we produce exposes a C API for other programs to import and utilize. pylego then uses the [ctypes](https://docs.python.org/3/library/ctypes.html) standard library in python to load this binary, and make calls to its methods.
|
|
61
|
+
|
|
62
|
+
The output binary, `lego.so`, is installed alongside pylego, and pylego exposes a python function called run_lego_command that will convert the arguments into a JSON message, and send it to LEGO.
|
|
63
|
+
|
|
64
|
+
On `pip install`, setuptools attempts to build this binary by running the command
|
|
65
|
+
|
|
66
|
+
```
|
|
67
|
+
go build -o lego.so -buildmode=c-shared lego.go
|
|
68
|
+
```
|
|
69
|
+
|
|
70
|
+
If we don't have a .whl that supports your environment, you will need to have Go installed and configured for Python to be able to build this binary.
|
|
71
|
+
|
|
72
|
+
## License
|
|
73
|
+
|
|
74
|
+
The `Lego` library used in this project is licensed under the [MIT License](https://github.com/go-acme/lego/blob/master/LICENSE).
|
|
75
|
+
|
|
76
|
+
`pylego` itself is licensed under the [Apache License, Version 2.0](./LICENSE).
|
pylego-0.1.0/README.md
ADDED
|
@@ -0,0 +1,61 @@
|
|
|
1
|
+
# pylego
|
|
2
|
+
|
|
3
|
+
pylego is a python extension package to utilize the certificate management application [Lego](https://github.com/go-acme/lego) written in Golang in python.
|
|
4
|
+
|
|
5
|
+
## Installation
|
|
6
|
+
|
|
7
|
+
To install this package, all you need to do is run
|
|
8
|
+
|
|
9
|
+
```
|
|
10
|
+
pip install .
|
|
11
|
+
```
|
|
12
|
+
|
|
13
|
+
in your preferred Python venv.
|
|
14
|
+
|
|
15
|
+
## Usage
|
|
16
|
+
|
|
17
|
+
You can import the lego command and run any function that you can run from the CLI:
|
|
18
|
+
|
|
19
|
+
```python
|
|
20
|
+
from pylego import run_lego_command
|
|
21
|
+
test_env = {"NAMECHEAP_API_USER": "user", "NAMECHEAP_API_KEY": "key"}
|
|
22
|
+
run_lego_command("something@gmail.com", "https://localhost/directory", "-----BEGIN CERTIFICATE REQUEST----- ...", "namecheap", test_env)
|
|
23
|
+
```
|
|
24
|
+
|
|
25
|
+
| Argument | Description |
|
|
26
|
+
| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
|
|
27
|
+
| `email` | The provided email will be registered to LetsEncrypt. It may receive some emails notifying the user about certificate expiry. |
|
|
28
|
+
| `server` | This is the full URL of a server that implements the ACME protocol. While letsencrypt is the most common one, there are other programs that provide this facility like Vault. |
|
|
29
|
+
| `csr` | This must be a PEM string in bytes that is user generated and valid as according to the ACME server that is being provided above. Many providers have different requirements for what is allowed to be in the fields of the CSR. |
|
|
30
|
+
| `plugin` | The plugin is a string that's supported by LEGO. The full list is located [here](https://go-acme.github.io/lego/dns/). On top of the LEGO provided ones, we have an extra plugin called `http` that will allow users to use HTTP01 and TLSALPN01 challenges. |
|
|
31
|
+
| `env` | The env is a dictionary mapping of strings to strings that will be loaded into the environment for LEGO to use. All plugins require some configuration values loaded into the environment. You can find them [here](https://go-acme.github.io/lego/dns/) |
|
|
32
|
+
|
|
33
|
+
On top of the environment variables that LEGO supports, we have some extra ones that we use to configure the library:
|
|
34
|
+
|
|
35
|
+
| Key | Description |
|
|
36
|
+
| ----------------- | ----------------------------------------------------------------------------------------------------------------------------- |
|
|
37
|
+
| `SSL_CERT_FILE` | Path to a CA certificate file for pylego to trust. This can be used for trusting the certificate of the ACME server provided. |
|
|
38
|
+
| `HTTP01_IFACE` | The interface to be used for the HTTP01 challenge if the plugin is chosen. Any interface by default. |
|
|
39
|
+
| `HTTP01_PORT` | The port to be used for the HTTP01 challenge if the plugin is chosen. 80 by default. |
|
|
40
|
+
| `TLSALPN01_IFACE` | The interface to be used for the TLSALPN01 challenge if the plugin is chosen. Any interface by default. |
|
|
41
|
+
| `TLSALPN01_PORT` | The port to be used for the TLSALPN01 challenge if the plugin is chosen. 443 by default. |
|
|
42
|
+
|
|
43
|
+
## How does it work?
|
|
44
|
+
|
|
45
|
+
Golang supports building a shared c library from its CLI build tool. We import and use the LEGO application from GoLang, and provide a stub with C bindings so that the shared C binary we produce exposes a C API for other programs to import and utilize. pylego then uses the [ctypes](https://docs.python.org/3/library/ctypes.html) standard library in python to load this binary, and make calls to its methods.
|
|
46
|
+
|
|
47
|
+
The output binary, `lego.so`, is installed alongside pylego, and pylego exposes a python function called run_lego_command that will convert the arguments into a JSON message, and send it to LEGO.
|
|
48
|
+
|
|
49
|
+
On `pip install`, setuptools attempts to build this binary by running the command
|
|
50
|
+
|
|
51
|
+
```
|
|
52
|
+
go build -o lego.so -buildmode=c-shared lego.go
|
|
53
|
+
```
|
|
54
|
+
|
|
55
|
+
If we don't have a .whl that supports your environment, you will need to have Go installed and configured for Python to be able to build this binary.
|
|
56
|
+
|
|
57
|
+
## License
|
|
58
|
+
|
|
59
|
+
The `Lego` library used in this project is licensed under the [MIT License](https://github.com/go-acme/lego/blob/master/LICENSE).
|
|
60
|
+
|
|
61
|
+
`pylego` itself is licensed under the [Apache License, Version 2.0](./LICENSE).
|
|
@@ -0,0 +1,66 @@
|
|
|
1
|
+
[project]
|
|
2
|
+
name = "pylego"
|
|
3
|
+
version = "0.1.0"
|
|
4
|
+
authors = [
|
|
5
|
+
{ name="Ghislain Bourgeois", email="ghislain.bourgeois@canonical.com" },
|
|
6
|
+
{ name="Kayra Gemalmaz", email="kayra.gemalmaz@canonical.com" },
|
|
7
|
+
{ name="Daniel Arndt", email="daniel.arndt@canonical.com" },
|
|
8
|
+
{ name="Guillaume Belanger", email="guillaume.belanger@canonical.com" },
|
|
9
|
+
{ name="Yazan Salti", email="yazan.salti@canonical.com" },
|
|
10
|
+
]
|
|
11
|
+
description = "A python wrapper package for the lego application written in Golang"
|
|
12
|
+
readme = "README.md"
|
|
13
|
+
requires-python = ">=3.8"
|
|
14
|
+
classifiers = [
|
|
15
|
+
"Programming Language :: Python :: 3",
|
|
16
|
+
"License :: OSI Approved :: Apache Software License",
|
|
17
|
+
"Operating System :: OS Independent",
|
|
18
|
+
]
|
|
19
|
+
|
|
20
|
+
[project.optional-dependencies]
|
|
21
|
+
test = [
|
|
22
|
+
"pytest",
|
|
23
|
+
"ruff"
|
|
24
|
+
]
|
|
25
|
+
|
|
26
|
+
[project.urls]
|
|
27
|
+
Homepage = "https://github.com/canonical/pylego"
|
|
28
|
+
Issues = "https://github.com/canonical/pylego/issues"
|
|
29
|
+
|
|
30
|
+
[build-system]
|
|
31
|
+
requires = ["setuptools>=61.0"]
|
|
32
|
+
build-backend = "setuptools.build_meta"
|
|
33
|
+
|
|
34
|
+
[tool.setuptools]
|
|
35
|
+
package-dir = {"" = "src"}
|
|
36
|
+
|
|
37
|
+
[tool.setuptools.packages.find]
|
|
38
|
+
where = ["src"]
|
|
39
|
+
|
|
40
|
+
[tool.setuptools.package-data]
|
|
41
|
+
pylego = ["lego.so"]
|
|
42
|
+
|
|
43
|
+
# Linting tools configuration
|
|
44
|
+
[tool.ruff]
|
|
45
|
+
line-length = 100
|
|
46
|
+
|
|
47
|
+
[tool.ruff.lint]
|
|
48
|
+
select = ["E", "W", "F", "C", "N", "D", "I001"]
|
|
49
|
+
extend-ignore = [
|
|
50
|
+
"D203",
|
|
51
|
+
"D204",
|
|
52
|
+
"D213",
|
|
53
|
+
"D215",
|
|
54
|
+
"D400",
|
|
55
|
+
"D404",
|
|
56
|
+
"D406",
|
|
57
|
+
"D407",
|
|
58
|
+
"D408",
|
|
59
|
+
"D409",
|
|
60
|
+
"D413",
|
|
61
|
+
]
|
|
62
|
+
ignore = ["E501", "D107"]
|
|
63
|
+
per-file-ignores = {"tests/*" = ["D100","D101","D102","D103","D104"]}
|
|
64
|
+
|
|
65
|
+
[tool.ruff.lint.mccabe]
|
|
66
|
+
max-complexity = 10
|
pylego-0.1.0/setup.cfg
ADDED
pylego-0.1.0/setup.py
ADDED
|
@@ -0,0 +1,26 @@
|
|
|
1
|
+
"""Build pylego."""
|
|
2
|
+
|
|
3
|
+
import os
|
|
4
|
+
import subprocess
|
|
5
|
+
|
|
6
|
+
from setuptools import setup
|
|
7
|
+
from setuptools.command.build_py import build_py as build_py_orig
|
|
8
|
+
|
|
9
|
+
|
|
10
|
+
def build_go_library():
|
|
11
|
+
"""Build the lego application into a shared .so file."""
|
|
12
|
+
os.chdir("src/pylego")
|
|
13
|
+
subprocess.check_call(["go", "build", "-o", "lego.so", "-buildmode=c-shared", "lego.go"])
|
|
14
|
+
os.chdir("../..")
|
|
15
|
+
|
|
16
|
+
|
|
17
|
+
class BuildPy(build_py_orig):
|
|
18
|
+
"""Build requirements for the package."""
|
|
19
|
+
|
|
20
|
+
def run(self):
|
|
21
|
+
"""Build modules, packages, and copy data files to build directory."""
|
|
22
|
+
build_go_library()
|
|
23
|
+
super().run()
|
|
24
|
+
|
|
25
|
+
|
|
26
|
+
setup(cmdclass={"build_py": BuildPy})
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
from .pylego import run_lego_command # noqa: F401, D104
|
|
Binary file
|
|
@@ -0,0 +1,68 @@
|
|
|
1
|
+
"""Python interface that wraps the lego application CLI."""
|
|
2
|
+
|
|
3
|
+
import ctypes
|
|
4
|
+
import json
|
|
5
|
+
from dataclasses import dataclass
|
|
6
|
+
from pathlib import Path
|
|
7
|
+
|
|
8
|
+
here = Path(__file__).absolute().parent
|
|
9
|
+
so_file = here / ("lego.so")
|
|
10
|
+
library = ctypes.cdll.LoadLibrary(so_file)
|
|
11
|
+
|
|
12
|
+
|
|
13
|
+
@dataclass
|
|
14
|
+
class Metadata:
|
|
15
|
+
"""Extra information returned by the ACME server."""
|
|
16
|
+
|
|
17
|
+
stable_url: str
|
|
18
|
+
url: str
|
|
19
|
+
domain: str
|
|
20
|
+
|
|
21
|
+
|
|
22
|
+
@dataclass
|
|
23
|
+
class LEGOResponse:
|
|
24
|
+
"""The class that lego returns when issuing certificates correctly."""
|
|
25
|
+
|
|
26
|
+
csr: str
|
|
27
|
+
private_key: str
|
|
28
|
+
certificate: str
|
|
29
|
+
issuer_certificate: str
|
|
30
|
+
metadata: Metadata
|
|
31
|
+
|
|
32
|
+
|
|
33
|
+
class LEGOError(Exception):
|
|
34
|
+
"""Exceptions that are returned from the LEGO Go library."""
|
|
35
|
+
|
|
36
|
+
|
|
37
|
+
def run_lego_command(
|
|
38
|
+
email: str, server: str, csr: bytes, env: dict[str, str], plugin: str = ""
|
|
39
|
+
) -> LEGOResponse:
|
|
40
|
+
"""Run an arbitrary command in the Lego application. Read more at https://go-acme.github.io.
|
|
41
|
+
|
|
42
|
+
Args:
|
|
43
|
+
email: the email to be used for registration
|
|
44
|
+
server: the server to be used for requesting a certificate that implements the ACME protocol
|
|
45
|
+
csr: the csr to be signed
|
|
46
|
+
plugin: which DNS provider plugin to use for the request. Find yours at https://go-acme.github.io/lego/dns/.
|
|
47
|
+
env: the environment variables required for the chosen plugin.
|
|
48
|
+
"""
|
|
49
|
+
library.RunLegoCommand.restype = ctypes.c_char_p
|
|
50
|
+
library.RunLegoCommand.argtypes = [ctypes.c_char_p]
|
|
51
|
+
|
|
52
|
+
message = bytes(
|
|
53
|
+
json.dumps(
|
|
54
|
+
{
|
|
55
|
+
"email": email,
|
|
56
|
+
"server": server,
|
|
57
|
+
"csr": csr.decode(),
|
|
58
|
+
"plugin": plugin,
|
|
59
|
+
"env": env,
|
|
60
|
+
}
|
|
61
|
+
),
|
|
62
|
+
"utf-8",
|
|
63
|
+
)
|
|
64
|
+
result: bytes = library.RunLegoCommand(message)
|
|
65
|
+
if result.startswith(b"error:"):
|
|
66
|
+
raise LEGOError(result.decode())
|
|
67
|
+
result_dict = json.loads(result.decode("utf-8"))
|
|
68
|
+
return LEGOResponse(**{**result_dict, "metadata": Metadata(**result_dict.get("metadata"))})
|
|
@@ -0,0 +1,76 @@
|
|
|
1
|
+
Metadata-Version: 2.1
|
|
2
|
+
Name: pylego
|
|
3
|
+
Version: 0.1.0
|
|
4
|
+
Summary: A python wrapper package for the lego application written in Golang
|
|
5
|
+
Author-email: Ghislain Bourgeois <ghislain.bourgeois@canonical.com>, Kayra Gemalmaz <kayra.gemalmaz@canonical.com>, Daniel Arndt <daniel.arndt@canonical.com>, Guillaume Belanger <guillaume.belanger@canonical.com>, Yazan Salti <yazan.salti@canonical.com>
|
|
6
|
+
Project-URL: Homepage, https://github.com/canonical/pylego
|
|
7
|
+
Project-URL: Issues, https://github.com/canonical/pylego/issues
|
|
8
|
+
Classifier: Programming Language :: Python :: 3
|
|
9
|
+
Classifier: License :: OSI Approved :: Apache Software License
|
|
10
|
+
Classifier: Operating System :: OS Independent
|
|
11
|
+
Requires-Python: >=3.8
|
|
12
|
+
Description-Content-Type: text/markdown
|
|
13
|
+
Provides-Extra: test
|
|
14
|
+
License-File: LICENSE
|
|
15
|
+
|
|
16
|
+
# pylego
|
|
17
|
+
|
|
18
|
+
pylego is a python extension package to utilize the certificate management application [Lego](https://github.com/go-acme/lego) written in Golang in python.
|
|
19
|
+
|
|
20
|
+
## Installation
|
|
21
|
+
|
|
22
|
+
To install this package, all you need to do is run
|
|
23
|
+
|
|
24
|
+
```
|
|
25
|
+
pip install .
|
|
26
|
+
```
|
|
27
|
+
|
|
28
|
+
in your preferred Python venv.
|
|
29
|
+
|
|
30
|
+
## Usage
|
|
31
|
+
|
|
32
|
+
You can import the lego command and run any function that you can run from the CLI:
|
|
33
|
+
|
|
34
|
+
```python
|
|
35
|
+
from pylego import run_lego_command
|
|
36
|
+
test_env = {"NAMECHEAP_API_USER": "user", "NAMECHEAP_API_KEY": "key"}
|
|
37
|
+
run_lego_command("something@gmail.com", "https://localhost/directory", "-----BEGIN CERTIFICATE REQUEST----- ...", "namecheap", test_env)
|
|
38
|
+
```
|
|
39
|
+
|
|
40
|
+
| Argument | Description |
|
|
41
|
+
| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
|
|
42
|
+
| `email` | The provided email will be registered to LetsEncrypt. It may receive some emails notifying the user about certificate expiry. |
|
|
43
|
+
| `server` | This is the full URL of a server that implements the ACME protocol. While letsencrypt is the most common one, there are other programs that provide this facility like Vault. |
|
|
44
|
+
| `csr` | This must be a PEM string in bytes that is user generated and valid as according to the ACME server that is being provided above. Many providers have different requirements for what is allowed to be in the fields of the CSR. |
|
|
45
|
+
| `plugin` | The plugin is a string that's supported by LEGO. The full list is located [here](https://go-acme.github.io/lego/dns/). On top of the LEGO provided ones, we have an extra plugin called `http` that will allow users to use HTTP01 and TLSALPN01 challenges. |
|
|
46
|
+
| `env` | The env is a dictionary mapping of strings to strings that will be loaded into the environment for LEGO to use. All plugins require some configuration values loaded into the environment. You can find them [here](https://go-acme.github.io/lego/dns/) |
|
|
47
|
+
|
|
48
|
+
On top of the environment variables that LEGO supports, we have some extra ones that we use to configure the library:
|
|
49
|
+
|
|
50
|
+
| Key | Description |
|
|
51
|
+
| ----------------- | ----------------------------------------------------------------------------------------------------------------------------- |
|
|
52
|
+
| `SSL_CERT_FILE` | Path to a CA certificate file for pylego to trust. This can be used for trusting the certificate of the ACME server provided. |
|
|
53
|
+
| `HTTP01_IFACE` | The interface to be used for the HTTP01 challenge if the plugin is chosen. Any interface by default. |
|
|
54
|
+
| `HTTP01_PORT` | The port to be used for the HTTP01 challenge if the plugin is chosen. 80 by default. |
|
|
55
|
+
| `TLSALPN01_IFACE` | The interface to be used for the TLSALPN01 challenge if the plugin is chosen. Any interface by default. |
|
|
56
|
+
| `TLSALPN01_PORT` | The port to be used for the TLSALPN01 challenge if the plugin is chosen. 443 by default. |
|
|
57
|
+
|
|
58
|
+
## How does it work?
|
|
59
|
+
|
|
60
|
+
Golang supports building a shared c library from its CLI build tool. We import and use the LEGO application from GoLang, and provide a stub with C bindings so that the shared C binary we produce exposes a C API for other programs to import and utilize. pylego then uses the [ctypes](https://docs.python.org/3/library/ctypes.html) standard library in python to load this binary, and make calls to its methods.
|
|
61
|
+
|
|
62
|
+
The output binary, `lego.so`, is installed alongside pylego, and pylego exposes a python function called run_lego_command that will convert the arguments into a JSON message, and send it to LEGO.
|
|
63
|
+
|
|
64
|
+
On `pip install`, setuptools attempts to build this binary by running the command
|
|
65
|
+
|
|
66
|
+
```
|
|
67
|
+
go build -o lego.so -buildmode=c-shared lego.go
|
|
68
|
+
```
|
|
69
|
+
|
|
70
|
+
If we don't have a .whl that supports your environment, you will need to have Go installed and configured for Python to be able to build this binary.
|
|
71
|
+
|
|
72
|
+
## License
|
|
73
|
+
|
|
74
|
+
The `Lego` library used in this project is licensed under the [MIT License](https://github.com/go-acme/lego/blob/master/LICENSE).
|
|
75
|
+
|
|
76
|
+
`pylego` itself is licensed under the [Apache License, Version 2.0](./LICENSE).
|
|
@@ -0,0 +1,12 @@
|
|
|
1
|
+
LICENSE
|
|
2
|
+
README.md
|
|
3
|
+
pyproject.toml
|
|
4
|
+
setup.py
|
|
5
|
+
src/pylego/__init__.py
|
|
6
|
+
src/pylego/lego.so
|
|
7
|
+
src/pylego/pylego.py
|
|
8
|
+
src/pylego.egg-info/PKG-INFO
|
|
9
|
+
src/pylego.egg-info/SOURCES.txt
|
|
10
|
+
src/pylego.egg-info/dependency_links.txt
|
|
11
|
+
src/pylego.egg-info/requires.txt
|
|
12
|
+
src/pylego.egg-info/top_level.txt
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
pylego
|