Skip to main content

glovebox-hosts

The one answer to "which host is this" that every part of glovebox uses: the egress proxy's verdict service, the launcher, the WebFetch hook, the session driver and the evals.

A host is compared in one spelling: ASCII only, surrounding whitespace removed, lowercased, and an IP literal in its standard form. A name that is not ASCII, or that starts or ends with a dot, is refused with HostError rather than folded, so two readers can never disagree about it.

>>> from glovebox_hosts import canonical_host, split_authority, granting_entries
>>> split_authority("[2001:DB8::1]:443")
('2001:db8::1', 443)
>>> granting_entries("API.example.com", ["example.com"])
['example.com']
>>> granting_entries("a.b.example.com", ["example.com"])
[]

A grant on a name reaches that host alone, and a *.S grant every name below S. A bar (constraining_entries) reaches any depth. A grant may not name a *. wildcard over a public suffix, or over a name with one below it (suffix_below): grant_name_refusal says why, reading the Public Suffix List that tldextract bundles. A grant on a public suffix itself is allowed, since it reaches that one host. That is the package's one dependency, and it is imported only when a grant name is judged.

pod_grants reads a Kata pod's glovebox.dev/egress-grants annotation as every node reads it, so an admission webhook can refuse a pod at submission for the same reason the node would refuse it later. It returns the granted hosts at their tiers, the address grants and the port grants, and raises GrantRefused with the node's own message for the first entry the node refuses. How wide an address grant may be is each node's own setting, so it is not checked here.

A host with a port, such as {"host": "git.example.com:22", "rw": true}, is a port grant. The node relays a raw stream to that port on the name's public addresses, so it needs "rw": true. A host without a port keeps its plain host meaning.

>>> from glovebox_hosts import GrantRefused, pod_grants
>>> granted = pod_grants('["httpbin.org", {"host": "git.example.com:22", "rw": true}]')
>>> granted.hosts
{'httpbin.org': 'ro'}
>>> granted.ports
[PortGrant(host='git.example.com', port=22)]
>>> pod_grants('["*.amazonaws.com"]')
Traceback (most recent call last):
...
glovebox_hosts.GrantRefused: glovebox.dev/egress-grants: '*.amazonaws.com' is a wildcard over a name with the public suffix ...

glovebox_hosts.flock holds an exclusive file lock: held for a block, or acquire and release when the hold spans two calls. It lives here because the host tools and the monitor package can both import it.

Metadata

Release files for glovebox-hosts 0.6.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for glovebox-hosts 0.6.1
File Size Uploaded Provenance
glovebox_hosts-0.6.1.tar.gz 15.1 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for glovebox-hosts 0.6.1
File Interpreter ABI Platform
glovebox_hosts-0.6.1-py3-none-any.whl Python 3 none any Details

Total release size: 28.1 kB

Release files / glovebox_hosts-0.6.1.tar.gz

Download URL glovebox_hosts-0.6.1.tar.gz
Size 15.1 kB
Tags Source
SHA-256 checksum
How to use checksums
056b5269b204ab74e7f64e8d466714226e80e5c3b5c0c822ffd5fba281a3c768
BLAKE2b-256 checksum
How to use checksums
e64b294d6e6cb7c62b6ec556f2f76bfa9405bf1d7a447af78a7a7d1d63701dd0
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.4 {"installer":{"name":"uv","version":"0.13.4","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / glovebox_hosts-0.6.1-py3-none-any.whl

Download URL glovebox_hosts-0.6.1-py3-none-any.whl
Size 13.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
eed6ee0f0ca777a6a19316a8120a81f04ff1b9400c1da9dd63f89eb09152a4b0
BLAKE2b-256 checksum
How to use checksums
f7b5c3516af0cec58d84a9f2e50b5421d4f739c5159bfcf7017b8b0e82920586
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.4 {"installer":{"name":"uv","version":"0.13.4","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Security for glovebox-hosts 0.6.1

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page