Enforce path traversal validation and deterministic user listing - #414
Enforce path traversal validation and deterministic user listing#414Cylae wants to merge 1 commit into
Conversation
|
👋 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 New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
Enforced validate_safe_path in atomic_write, ProcessLock::acquire, and Journal::open_or_create to prevent path traversal vulnerabilities. Optimized and sorted user listing deterministically in UserManager::list_users. Added contract tests for all changes.
PR created automatically by Jules for task 1430597682708282895 started by @Cylae