Maarufu: Data ilisasishwa 27 Oktoba 2026

Kategoria

Intaneti1,356
Mawasiliano321
Sauti na video898
Michoro na usanifu539
Ofisi na tija1,124
Zana za wasanidi3,134
Zana za AI529
Usalama na faragha385
Zana za mfumo3,114
Michezo523
Elimu na sayansi239
Mtandao na TEHAMA284

openapi-oathkeeper: matoleo yote na matoleo ya zamani

Generate Ory Oathkeeper access rules from an OpenAPI 3 contract.

Hapa yameorodheshwa matoleo 4 ya openapi-oathkeeper, kuanzia 19 Machi 2026 hadi toleo la sasa 0.8.0. Kila moja lina kiungo cha faili za kisakinishi za mchapishaji mwenyewe.

2026: 4 4 26
ToleoTareheUkubwaFaili
0.8.0Toleo jipya zaidi 9 Septemba 2026 — 64-bit ZIP32-bit ZIP
Maelezo ya toleo
## What's Changed

• Add integration tests by @emmanuelgautier in https://github.com/cerberauth/openapi-oathkeeper/pull/143
• feat:update dependencies and image version by @emmanuelgautier in https://github.com/cerberauth/openapi-oathkeeper/pull/144
• Capture array and object path params as explicit types by @emmanuelgautier in https://github.com/cerberauth/openapi-oathkeeper/pull/145

**Full Changelog**:https://github.com/cerberauth/openapi-oathkeeper/compare/v0.7.19...v0.8.0
0.7.19 7 Septemba 2026 — 64-bit ZIP32-bit ZIP
Maelezo ya toleo
## Security fix

**High severity:** Overbroad path-parameter regex in generated Ory Oathkeeper access rules could cause an authentication/authorization bypass.

Previously, every OpenAPI `string` path parameter (and any parameter type the generator couldn't classify) was compiled to the unanchored regex token `<.+>`. Because `.` matches `/` in Go's regexp engine — and in Ory Oathkeeper's `regexp` matching strategy — a rule generated for a single path segment (e.g. `/public/{slug}`) also matched deeper, unrelated paths under the same prefix (e.g. `/public/admin/delete-all-users`). If those deeper paths weren't defined as their own, more specific OpenAPI operations, the broader (often unauthenticated `noop`) rule would match and proxy them instead of being rejected.

Generated rules for `string` and unclassified path parameters now use `<[^/]+>`, anchored to a single URL segment, matching the behavior already documented for numeric parameters.

**Action required:** Regenerate your Ory Oathkeeper access rules with this version and redeploy them. Rules generated by earlier versions using `string` path parameters may be broader than intended.

See [GHSA-9f3w-vm54-7gfc](https://github.com/cerberauth/openapi-oathkeeper/security/advisories/GHSA-9f3w-vm54-7gfc) for full details. Thanks to @EQSTLab for the responsible disclosure.

## What's Changed

• fix(generator):anchor string path-parameter regex to a single URL segment by @emmanuelgautier in https://github.com/cerberauth/openapi-oathkeeper/pull/142

**Full Changelog**:https://github.com/cerberauth/openapi-oathkeeper/compare/v0.7.18...v0.7.19
0.7.18 13 Agosti 2026 — 64-bit ZIP32-bit ZIP
0.7.15 19 Machi 2026 — 64-bit ZIP32-bit ZIP

Maarufu zaidi katika Lugha na SDK

Ona zote
  1. LLVMLugha na SDK · LLVM
  2. DenoLugha na SDK · Deno Land Inc.
  3. CMakeLugha na SDK · Kitware
  4. YarnLugha na SDK · Yarn Contributors
  5. CcacheLugha na SDK · Joel Rosdahl
  6. sbtLugha na SDK · Lightbend, Inc.
  7. BOINCLugha na SDK · Space Sciences Laboratory, U.C. Berkeley
  8. Dart SDKLugha na SDK · Google
  9. NVM for WindowsLugha na SDK · Ecor Ventures LLC

Zaidi kutoka CerberAuth

Ona zote
  • jwtopLugha na SDK · CerberAuth

Shiriki