httpie-http-message-signatures
An authentication plugin for HTTPie, implementing the IETF HTTP Message Signatures draft specification.
This is an incompatible replacement for and not to be confused with the "Cavage" HTTP Signatures draft.
Installation
The preferred installation method is via the httpie cli plugins utility:
$ httpie cli plugins install httpie-http-message-signatures
You may also download this repository and install from a local source:
$ cd httpie-http-message-signatures
$ httpie cli plugins install .
Last but not least, you can install via pip as well:
$ pip install --upgrade httpie-http-message-signatures
Usage
Use message-signature as the auth-type:
http -A message-signature ...
The HTTP Message Signature draft allows for a whole bunch of parameters to influence the signature. Because this can get somewhat overwhelming quickly, this plugin allows the parameters to be passed in two different ways:
-
-a/--authcommand line parameterThis allows passing arguments inline, in the following format:
key_id ":" key [":" covered_component_ids]In other words, the key id, followed by a
:, followed by the private key as base 64 encoded string, optionally followed by another:and a list of comma-separated covered component ids. For example:$ http -A message-signature -a foobar:cDf/J30Q7EtXmZZ91j4OLg== example.com $ http -A message-signature -a foobar:cDf/J30Q7EtXmZZ91j4OLg==:@authority,@method example.com -
~/.httpmessagesignaturesrcfileIf no parameters are passed via
-a/--auth, the plugin will look for a file called.httpmessagesignaturesrcin the home directory. This file is a simple INI-like file format, which contains sections for different hosts, each with their own settings. A[DEFAULT]section can be used to set defaults for all hosts. For example:[DEFAULT] covered_component_ids = @method,@authority,@target-uri,content-digest [example.com] key_id = foobar key = cDf/J30Q7EtXmZZ91j4OLg== [*.example.com] key_id = uydnfpw0xnegmpx2op3rhw2qm key = nkAFfoSEN/rXWu6PrqsmntUeeSZ+aEoGD9YmxIxwjNxdlHPO4QYcSS+4aRroRHl92vEEipRCsr+j2tFVlPimfA== covered_component_ids = @method,@authority,@path,@query-params,content-digestHost names allow for wildcard patterns.
Covered component ids
Different parts of the HTTP request can be included in the signature. By default, these components are included:
@method@authority@target-uri
You can override this default list via the optional third command line argument or the covered_component_ids value
in the ~/.httpmessagesignaturesrc file. The plugin recognizes two special component ids:
-
content-digestWhen specifying
content-digestas a covered component, and the request has a request body, the plugin will add aContent-Digestheader to the request and include it in the signature. This allows easy signing of request bodies. -
@query-paramsThe default
@target-uricomponent signs the entire URI, including query parameters. Depending on your use case, you may need to sign the request path and query parameters separately. For this case the specification requires for every signed query parameter to be listed separately as its own component. E.g. a request tohttp://example.com/foo/?bar=baz&quux=42would have to look like this:$ http -A message-signature \ -a 'foobar:cDf/J30Q7EtXmZZ91j4OLg==:"@query-params";name="bar","@query-params";name="quux"' \ example.com bar==baz quux==42Since this is of course highly inconvenient, the special component id
@query-paramswill automatically be expanded to include all passed query parameters. So the above request can be shortened to:$ http -A message-signature -a foobar:cDf/J30Q7EtXmZZ91j4OLg==:@query-params example.com bar==baz quux==42
See the specification for a complete list of derived component names, but an incomplete list is presented here:
@method@target-uri@authority@scheme@request-target@path@query@query-param
Implementation
This plugin is a wrapper around http-message-signatures.
Metadata
Release files for httpie-http-message-signatures 0.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| httpie_http_message_signatures-0.0.2.tar.gz | 5.3 kB | Without provenance | Details for httpie_http_message_signatures-0.0.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| httpie_http_message_signatures-0.0.2-py3-none-any.whl | Python 3 | none | any | Details for httpie_http_message_signatures-0.0.2-py3-none-any.whl |
Total release size: 11.4 kB
Release files / httpie_http_message_signatures-0.0.2.tar.gz
| Download URL | httpie_http_message_signatures-0.0.2.tar.gz |
|---|---|
| Size | 5.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8ee82ba4296ac5edfee6cf7db549d5cf03cd71813d09988a72a2d6cede629a74
|
|
BLAKE2b-256 checksum How to use checksums |
4beef57dee3787844771ee7229dca65e43deaf6863078cd65fbb0cc84ba726ae
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.4.2 CPython/3.11.3 Darwin/22.5.0
|
Release files / httpie_http_message_signatures-0.0.2-py3-none-any.whl
| Download URL | httpie_http_message_signatures-0.0.2-py3-none-any.whl |
|---|---|
| Size | 6.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c47a89a9bd6558d418df9fd160a90b0e40300feb53ae0ca5b696f3bb2ec48cd1
|
|
BLAKE2b-256 checksum How to use checksums |
0768a8e274241be88af56f2d3ff249948b36944c1419f9a6b1e57fa94453df11
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.4.2 CPython/3.11.3 Darwin/22.5.0
|
Security for httpie-http-message-signatures 0.0.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.