示例
rack-protection 4.2.1: Require explicit opt-in to enable session hijacking protection in Rack::Protection 4.x rather than relying on default middleware inclusion.
已验证示例 — gem rack-protection 4.2.1: Require explicit opt-in to enable session hijacking protection in Rack::Protection 4.x rather than relying on default…
sha256:211d7395fda74de66490b727f70e99004de2ff33d235445d7c9a625f290745c2
本网络只提供一件事：能构建的样本。它在沙箱中运行并保留签名回执。它不评级、不担保——同样的代码能否在你的环境构建，它没有测量过。
提交了通过的契约回执的不同签名密钥数量。为 1 表示只有作者；大于 1 表示还有其他人构建过。密钥是自行生成的，背后没有注册身份，因此计的是密钥而非人。
MIT-0
执行证据
声明的环境与签名的运行分开呈现，你可以看到这个样本究竟运行了什么、在哪里运行。
- 证据依据
- 签名契约通过
- 验证回执
- 2
- 构建过它的签名密钥
- 1
声明的环境
ruby linux x64 ruby ruby rubygems
验证运行环境
| 环境 | 契约 | 阶段 | 运行日期 |
|---|---|---|---|
| ruby 3 · linux alpine/x64 · docker ed25519:d91480838ac982c9 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · rubygems@1 |
2026-08-16 |
| ruby 3 · linux debian/x64 · docker ed25519:2175b912ea1c23b1 | SKIPPED | compile:SKIPPED · contract:SKIPPED · load:SKIPPED · resolve:FAIL CONTAINER_RUN · rubygems@1 |
2026-08-18 |
案例
HOW- 目标
- Require explicit opt-in to enable session hijacking protection in Rack::Protection 4.x rather than relying on default middleware inclusion.
- 符号
-
- Rack::Protection
- Rack::Protection::SessionHijacking
- 环境
- ruby
- 创建时间
- 2026-08-16T16:38:09Z
契约
- Rack::Protection.new with default options retains session payload and omits tracking state across requests with altered user agents, leaving session hijacking defense disabled until session_hijacking is explicitly passed via use.
- Passing use: :session_hijacking to Rack::Protection.new tracks user agent headers in session tracking state and drops the session when the user agent changes on subsequent requests.
文件
- Gemfile
- NOTES.md
- csx.json
- test/contract.rb