chore(deps): update terraform aws to v6.55.0 - #367
Merged
Conversation
| datasource | package | from | to | | ------------------ | ------------- | ------ | ------ | | terraform-provider | hashicorp/aws | 6.54.0 | 6.55.0 |
l50
added a commit
to l50/DreadGOAD
that referenced
this pull request
Jul 30, 2026
…e fix **Changed:** - Moved `printnightmare` from `uncreditableCategories` to `creditableCategories`, allowing it to score as an exploit now that ares-cli dreadnode#367 rebuilt the detection gate on a single "exploit completed" marker the PoC actually prints - `transport_ares.go` - Rewrote the doc comment to scope the remaining refusal to `zerologon` only and explain the corrected rationale for `printnightmare`, whose old gate matched markers that never fired and thus scored zero rather than over-crediting - `transport_ares.go` - Updated tests to assert `printnightmare` now credits under its own technique ID and split the "refusals never credit" case to isolate `zerologon` from the newly credited `printnightmare` - `transport_ares_test.go`
l50
added a commit
to l50/DreadGOAD
that referenced
this pull request
Jul 30, 2026
…te fix (#32) **Key Changes:** - Enabled crediting of the `printnightmare` category now that ares-cli dreadnode#367 rebuilt its detection gate on a marker the PoC actually prints - Moved `printnightmare` from the uncreditable refusal list to the creditable categories map - Updated tests and documentation to reflect the corrected classification and rationale **Added:** - Creditable `printnightmare` category - Added `printnightmare` to `creditableCategories` so the technique is scored like any other exploit - `transport_ares.go` - Test coverage for crediting - Added test cases verifying `printnightmare` credits after ares dreadnode#367, including a dedicated `printnightmare credits after ares gate fix` token coverage case - `transport_ares_test.go` **Changed:** - Refusal rationale documentation - Rewrote the doc comment to explain that the original `printnightmare` refusal was based on a faulty mechanism (a gate matching markers the PoC never printed), corrected by ares-cli dreadnode#367, and narrowed the remaining refusal rationale to `zerologon` alone - `transport_ares.go` - Refusal test expectations - Updated `TestUncreditableCategoriesAreDeliberate`, `TestDetectTokenCoverageDrift`, and the `AresCategoryToTechniqueID` refusal cases to expect only `zerologon` (plus `other` and `golden_ticket`) as deliberate refusals - `transport_ares_test.go` **Removed:** - `printnightmare` refusal entry - Removed `printnightmare` from the `uncreditableCategories` map and its associated refusal test assertions, since the category now credits correctly - `transport_ares.go`, `transport_ares_test.go`
l50
added a commit
to l50/DreadGOAD
that referenced
this pull request
Jul 30, 2026
**Key Changes:** - Documented that the ares#366/dreadnode#367 fixes are fork-only (l50/ares) and absent from dreadnode/ares - Added caveats explaining over-crediting and silent under-crediting risks against a stock ares build - Updated all issue references from generic "ares-cli"/"ares" to fully-qualified "l50/ares" repo paths **Changed:** - Corrected upstream issue references throughout `transport_ares.go` and `transport_ares_test.go`, replacing ambiguous "ares-cli dreadnode#366"/"ares dreadnode#367" mentions with fully-qualified "l50/ares#366" and "l50/ares#367" identifiers - Expanded the `aresTokenBucket` doc comment to explain that the exploited-count fix relies on fork-only changes to `build_token_coverage_json` and `state/reader.rs`, warning that stock builds lack `KEY_SUPERSEDED` and will over-credit back-credited techniques - Extended the `uncreditableCategories` documentation to clarify the category promotion is fork-only, detailing how zerologon, nopac, and printnightmare collapse back to "other" against dreadnode/ares and cause silent crediting failures for nopac and printnightmare
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.
This PR contains the following updates:
6.54.0→6.55.0~> 6.54.0→~> 6.55.0Release Notes
hashicorp/terraform-provider-aws (aws)
v6.55.0Compare Source
FEATURES:
aws_elasticache_service_updates(#44608)aws_autoscaling_group(#48928)aws_cloudwatch_log_stream(#48878)aws_kinesis_firehose_delivery_stream(#48946)aws_network_interface(#48887)aws_rds_cluster(#48948)aws_sfn_state_machine(#48840)ENHANCEMENTS:
updated_atattribute (#48881)allowed_workload_configuration,private_endpoint, andprivate_endpoint_overridesconfiguration blocks toauthorizer_configuration.custom_jwt_authorizer, and the read-onlyrequire_service_s3_endpointattribute tonetwork_configuration.network_mode_config(#48654)allowed_workload_configuration,private_endpoint, andprivate_endpoint_overridesconfiguration blocks toauthorizer_configuration.custom_jwt_authorizer(#48654)allowed_workload_configuration,private_endpoint, andprivate_endpoint_overridesconfiguration blocks toauthorizer_configuration.custom_jwt_authorizer(#48654)require_service_s3_endpointargument tonetwork_configuration.network_mode_config(#48654)allowed_workload_configuration,private_endpoint, andprivate_endpoint_overridesconfiguration blocks toauthorizer_configuration.custom_jwt_authorizer(#48654)consumer_group_offset_sync_modeattribute toconsumer_group_replicationblock (#47670)BUG FIXES:
Unsupported Typeerrors when nomemoryis configured (#48654)interface conversion: interface {} is nil, not *configservice.DescribeOrganizationConfigRuleStatusesOutputpanics on delete (#48845)Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Mend Renovate.