Skip to content

fix: update registry guardrail to parse full path including hive#2108

Draft
hulto wants to merge 1 commit intomainfrom
fix-registry-guardrail-path-parsing-3908199613466224958
Draft

fix: update registry guardrail to parse full path including hive#2108
hulto wants to merge 1 commit intomainfrom
fix-registry-guardrail-path-parsing-3908199613466224958

Conversation

@hulto
Copy link
Collaborator

@hulto hulto commented Mar 18, 2026

This PR updates the registry guardrail to use a full path string instead of separating the subkey and checking both HKEY_LOCAL_MACHINE and HKEY_CURRENT_USER blindly.

It imports path-splitting logic to determine the correct root hive directly from the path prefix (e.g., HKLM\SOFTWARE\...), ensuring the behavior aligns with how Eldritch scripts natively reference registry keys.

Also includes a backwards-compatibility alias for the Serde configuration to prevent breaking previously built implants. Tests have been updated and run locally.


PR created automatically by Jules for task 3908199613466224958 started by @hulto

Updated the `Registry` guardrail struct and `check()` logic to accept a
single `path` value, matching the syntax used by Eldritch's registry
read function.

The guardrail now parses the root hive (e.g., HKLM, HKCU) and subkey
from the given path string, instead of attempting to blindly check both
local machine and current user hives. The parsing ignores case for
maximum robustness and aligns with typical Windows behavior.

Additionally, renamed the field `subkey` to `path` with a Serde alias to
preserve backwards compatibility, and updated the inline tests to
validate full paths.

Co-authored-by: hulto <7121375+hulto@users.noreply.github.com>
@google-labs-jules
Copy link
Contributor

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@github-actions
Copy link
Contributor

Summary

Tests 📝 Passed ✅ Failed ❌ Skipped ⏭️ Other ❓ Flaky 🍂 Duration ⏱️
2833    ±0 2833    ±0 0    ±0 0    ±0 0    ±0 0    ±0 1ms    ±0

Previous Results

Build 🏗️ Result 🧪 Tests 📝 Passed ✅ Failed ❌ Skipped ⏭️ Other ❓ Flaky 🍂 Duration ⏱️
#1789 2833 2833 0 0 0 0 37.3s

Insights

Average Tests per Run Total Flaky Tests Total Failed Slowest Test (p95)
2833 0 0 6.3s

Slowest Tests

Test 📝 Results 📊 Duration (avg) ⏱️ Duration (p95) ⏱️
TestDockerExecutor_Build_ContextCancellation 1 6.3s 6.3s
eldritch-libsys: std::dll_inject_impl::tests::test_dll_inject_simple 1 5.1s 5.1s
TestInteractiveShell 1 5.0s 5.0s
TestOtherStreamOutput 1 5.0s 5.0s
imix::bin/imix: install::tests::test_install_execution 3 1.8s 5.0s
imix::bin/imix: install::tests::test_install_execution 3 1.8s 5.0s
imix::bin/imix: install::tests::test_install_execution 3 1.8s 5.0s
TestDockerExecutor_Build_SimpleEcho 1 4.0s 4.0s
imix::bin/imix: tests::task_tests::test_task_streaming_output 3 3.0s 3.0s
imix::bin/imix: tests::task_tests::test_task_streaming_output 3 3.0s 3.0s

🎉 No failed tests in this run. | 🍂 No flaky tests in this run.

Github Test Reporter by CTRF 💚

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant