Gewild: Data bygewerk 27 Oktober 2026

Kategorieë

Internet1 356
Kommunikasie321
Klank en video898
Grafika en ontwerp539
Kantoor en produktiwiteit1 124
Ontwikkelaarsgereedskap3 134
KI-gereedskap529
Sekuriteit en privaatheid385
Stelselgereedskap3 114
Speletjies523
Onderwys en wetenskap239
Netwerk en IT284

openapi-oathkeeper: alle weergawes en ouer weergawes

Generate Ory Oathkeeper access rules from an OpenAPI 3 contract.

Hier is 4 weergawes van openapi-oathkeeper gelys, van 19 Maart 2026 tot die huidige 0.8.0. Elkeen skakel na die uitgewer se eie installeerlêers.

2026: 4 4 26
WeergaweDatumGrootteLêers
0.8.0Nuutste 09 September 2026 — 64-bis ZIP32-bis ZIP
Vrystellingsnotas
## 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 07 September 2026 — 64-bis ZIP32-bis ZIP
Vrystellingsnotas
## 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 Augustus 2026 — 64-bis ZIP32-bis ZIP
0.7.15 19 Maart 2026 — 64-bis ZIP32-bis ZIP

Gewildste in Tale en SDK’s

Sien alles
  1. LLVMTale en SDK’s · LLVM
  2. DenoTale en SDK’s · Deno Land Inc.
  3. CMakeTale en SDK’s · Kitware
  4. YarnTale en SDK’s · Yarn Contributors
  5. CcacheTale en SDK’s · Joel Rosdahl
  6. sbtTale en SDK’s · Lightbend, Inc.
  7. BOINCTale en SDK’s · Space Sciences Laboratory, U.C. Berkeley
  8. Dart SDKTale en SDK’s · Google
  9. NVM for WindowsTale en SDK’s · Ecor Ventures LLC

Meer van CerberAuth

Sien alles
  • jwtopTale en SDK’s · CerberAuth

Deel