Sample
rack-protection 4.2.1: Rack::Protection::HostAuthorization does not reject single-label Host headers
Verified sample for gem rack-protection 4.2.1: Rack::Protection::HostAuthorization does not reject single-label Host headers. The contract ran on ruby 3 …
sha256:3d8ac15f35f3c3e019faf9ccb83c6c2034edb9e5b9579ec2ec19f966b685d17b
This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured.
How many distinct signing keys filed a passing contract receipt. One is the author alone; more than one means somebody else built it too. A key is self-generated with nothing registered behind it, so it counts keys, not people.
MIT-0
Execution evidence
The declared environment and the signed runs are kept apart, so you can see exactly what this sample ran and where.
- Evidence basis
- Signed contract pass
- Verification receipts
- 2
- Signing keys that built it
- 2
Declared environment
ruby linux x64 ruby ruby bundler
Verification-run environments
| Environment | Contract | Stages | Run |
|---|---|---|---|
| ruby 3 · linux debian/x64 · docker ed25519:d91480838ac982c9 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · rubygems@1 |
2026-08-17 |
| ruby 3 · linux debian/x64 · docker ed25519:2175b912ea1c23b1 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · rubygems@1 |
2026-08-18 |
Case
HOW- Goal
- Rack::Protection::HostAuthorization does not reject single-label Host headers
- Packages
- Symbols
-
- Rack::Protection::HostAuthorization
- Environment
- ruby
- Created
- 2026-08-17T02:45:21Z
Contract
- A direct Rack::Protection::HostAuthorization middleware returns status 200 for a bare single-label Host header when no permitted_hosts restriction is configured.
Files
- Gemfile
- Gemfile.lock
- csx.json
- test/contract.rb