Bump cryptography from 48.0.1 to 50.0.0 - #1856
Merged
Merged
Conversation
Bumps [cryptography](https://github.com/pyca/cryptography) from 48.0.1 to 50.0.0. - [Changelog](https://github.com/pyca/cryptography/blob/main/CHANGELOG.rst) - [Commits](pyca/cryptography@48.0.1...50.0.0) --- updated-dependencies: - dependency-name: cryptography dependency-version: 50.0.0 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
|
Hello @dependabot[bot], ✅ The new VPATCH Rule is compliant, thank you for your contribution! |
|
Hello @dependabot[bot], Scenarios/AppSec Rule are compliant with the taxonomy, thank you for your contribution! |
sabban
added a commit
that referenced
this pull request
Aug 27, 2026
* feat(sharry): add Sharry collection with parser and bruteforce detection - Add sharry-logs parser for authentication failures - Add sharry-bf scenario (5 failures in 20s -> 1m ban) - Add collection, parser, and scenario documentation - Add test log samples - Detects: Authentication attempt failure for username X from ip Y * test(sharry): add parser and scenario tests - Add sharry-logs parser tests with assertions - Add sharry-bf scenario tests with 5 authentication failures - Tests verify correct field extraction and scenario triggering * fix(sharry): fix timestamp parsing and scenario capacity - Add timezone support to parser (UTC+11 for Sharry logs) - Add StrTimeFormat with timezone offset handling - Reduce scenario capacity from 5 to 4 (5 events need capacity 4 to overflow) - Update test assertions to expect +11:00 timezone format Fixes test failures where: 1. Timestamps weren't being parsed correctly (was defaulting to 1970) 2. Scenario wasn't triggering (needed 6 events with capacity 5, only had 5) * fix(sharry): use UTC timezone instead of hardcoded +1100 Replace hardcoded +1100 timezone offset with +0000 (UTC) since Sharry logs don't include timezone information. This follows the standard approach for logs without explicit timezone data. * Update blockers meta * Update blockers meta * chore(blockers): update cs-routeros-bouncer logo (#1867) The project replaced its brand mark. The logo carried here was the original teal shield-with-a-router drawing, two designs out of date. The replacement is the current mark: four lanes meeting a rail, three crossing and one stopping at it, in CrowdSec's indigo. Rendered at 256x256 from the same source SVG and the same palette tokens as every other asset the project ships, so it cannot drift from the site and the release artwork. Also 64x smaller: 1,072 bytes against 65,239. * Update blockers meta * Bump cryptography from 48.0.1 to 50.0.0 (#1856) Bumps [cryptography](https://github.com/pyca/cryptography) from 48.0.1 to 50.0.0. - [Changelog](https://github.com/pyca/cryptography/blob/main/CHANGELOG.rst) - [Commits](pyca/cryptography@48.0.1...50.0.0) --- updated-dependencies: - dependency-name: cryptography dependency-version: 50.0.0 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * Update blockers meta --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: GitHub Action <action@github.com> Co-authored-by: José M. Requena Plens <jmrplens@gmail.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Manuel Sabban <github@sabban.eu>
sabban
added a commit
that referenced
this pull request
Aug 27, 2026
* Feat/sharry support (#1685) * feat(sharry): add Sharry collection with parser and bruteforce detection - Add sharry-logs parser for authentication failures - Add sharry-bf scenario (5 failures in 20s -> 1m ban) - Add collection, parser, and scenario documentation - Add test log samples - Detects: Authentication attempt failure for username X from ip Y * test(sharry): add parser and scenario tests - Add sharry-logs parser tests with assertions - Add sharry-bf scenario tests with 5 authentication failures - Tests verify correct field extraction and scenario triggering * fix(sharry): fix timestamp parsing and scenario capacity - Add timezone support to parser (UTC+11 for Sharry logs) - Add StrTimeFormat with timezone offset handling - Reduce scenario capacity from 5 to 4 (5 events need capacity 4 to overflow) - Update test assertions to expect +11:00 timezone format Fixes test failures where: 1. Timestamps weren't being parsed correctly (was defaulting to 1970) 2. Scenario wasn't triggering (needed 6 events with capacity 5, only had 5) * fix(sharry): use UTC timezone instead of hardcoded +1100 Replace hardcoded +1100 timezone offset with +0000 (UTC) since Sharry logs don't include timezone information. This follows the standard approach for logs without explicit timezone data. * Update blockers meta * Update blockers meta * chore(blockers): update cs-routeros-bouncer logo (#1867) The project replaced its brand mark. The logo carried here was the original teal shield-with-a-router drawing, two designs out of date. The replacement is the current mark: four lanes meeting a rail, three crossing and one stopping at it, in CrowdSec's indigo. Rendered at 256x256 from the same source SVG and the same palette tokens as every other asset the project ships, so it cannot drift from the site and the release artwork. Also 64x smaller: 1,072 bytes against 65,239. * Update blockers meta * Bump cryptography from 48.0.1 to 50.0.0 (#1856) Bumps [cryptography](https://github.com/pyca/cryptography) from 48.0.1 to 50.0.0. - [Changelog](https://github.com/pyca/cryptography/blob/main/CHANGELOG.rst) - [Commits](pyca/cryptography@48.0.1...50.0.0) --- updated-dependencies: - dependency-name: cryptography dependency-version: 50.0.0 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * Update blockers meta --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: GitHub Action <action@github.com> Co-authored-by: José M. Requena Plens <jmrplens@gmail.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Manuel Sabban <github@sabban.eu> * fix multiple stuff for sharry stuff --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: PlagueDoctor <plague-doctor@users.noreply.github.com> Co-authored-by: GitHub Action <action@github.com> Co-authored-by: José M. Requena Plens <jmrplens@gmail.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps cryptography from 48.0.1 to 50.0.0.
Changelog
Sourced from cryptography's changelog.
... (truncated)
Commits
dcb7050Prepare for 50.0.0 release (#15372)53fccd9Don't leak how PKCS#7 encryptedKey decryption failed (#15369)d472f97Addfrom __future__ import annotationsto all src/ Python files (#15371)908773dBump downstream dependencies in CI (#15368)2cc07ccBump BoringSSL, OpenSSL, AWS-LC in CI (#15367)c94ede9chore(deps): bump ruff from 0.16.0 to 0.16.1 (#15366)67a8308chore(deps): bump virtualenv from 21.7.0 to 21.7.1 (#15365)95018ffRelease the GIL in one-shot AEAD encrypt/decrypt (#15361)6954733Release the GIL during DH and DSA parameter generation (#15364)6893b94Import _serialization instead of serialization in x509/extensions (#15363)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.