🛡️ Sentinel: [HIGH] Harden SSH security in build workflow#226
🛡️ Sentinel: [HIGH] Harden SSH security in build workflow#226christopherfoxjr wants to merge 2 commits into
Conversation
- Replace insecure `sshpass -p` with `sshpass -e` and environment variable mapping to prevent secret leakage in process lists. - Implement host key verification with `ssh-keyscan` and remove `StrictHostKeyChecking=no` to prevent MitM attacks. - Initialize Sentinel security journal in `.Jules/sentinel.md`. Co-authored-by: christopherfoxjr <213370400+christopherfoxjr@users.noreply.github.com>
|
👋 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. |

🚨 Severity: HIGH
💡 Vulnerability: The main build workflow used insecure SSH practices:
sshpass -p(leaking credentials in process list) andStrictHostKeyChecking=no(vulnerable to Man-in-the-Middle attacks).🎯 Impact: Secrets could be exposed to local users/processes, and deployment could be hijacked via MitM.
🔧 Fix: Switched to
sshpass -ewith environment variable mapping and implemented mandatory host key verification usingssh-keyscan.✅ Verification: Confirmed that the workflow no longer triggers the repository's own security audits and passed manual syntax and formatting checks.
PR created automatically by Jules for task 1392331929799934917 started by @christopherfoxjr