Skip to content

🛡️ Sentinel: Harden timing-safe equality and protect Telegram from sensitive content leaks#67

Open
SuvenSeo wants to merge 1 commit into
masterfrom
sentinel-harden-auth-and-telegram-security-14722682176424050829
Open

🛡️ Sentinel: Harden timing-safe equality and protect Telegram from sensitive content leaks#67
SuvenSeo wants to merge 1 commit into
masterfrom
sentinel-harden-auth-and-telegram-security-14722682176424050829

Conversation

@SuvenSeo

Copy link
Copy Markdown
Owner

🛡️ Sentinel Security Hardening

This PR addresses two critical security concerns:

  1. Timing Attack Resistance:

    • Improved safeEqual (Node.js runtime) and safeEqualText (Edge Runtime) to hash both input strings with SHA-256 before performing constant-time comparisons. This prevents length-based side-channel leaks, which could allow an attacker to guess secret lengths.
    • Updated proxy.js to await the now-asynchronous safeEqualText.
  2. Telegram Ingestion Protection:

    • Integrated hasSensitiveContent filtering into the Telegram handleMessage entry point.
    • Incoming Telegram messages containing patterns like API keys (sk-...), private keys, or "password=" assignments are now rejected and logged as a warning event instead of being stored in episodic_memory.
    • Users receive a clear security refusal message explaining that SEOS does not process secrets in chat.
  3. Maintenance:

    • Fixed an incorrect import in messageHandler.js.
    • Added a new test suite frontend/tests/sentinel-security.test.js covering the hardened equality logic and secret detection patterns.

All 37 tests in the frontend suite are passing.


PR created automatically by Jules for task 14722682176424050829 started by @SuvenSeo

…nsitive content leaks

- Hardened `safeEqual` and `safeEqualText` against length-based timing attacks by hashing both inputs with SHA-256 before constant-time comparison.
- Implemented sensitive content filtering in `handleMessage` (Telegram ingestion layer) to reject messages containing secrets (API keys, passwords, etc.) before persistence.
- Fixed a regression in `messageHandler.js` with an incorrect import path for `hasSensitiveContent`.
- Added `frontend/tests/sentinel-security.test.js` to verify security hardening logic.
- Updated Sentinel security journal in `.jules/sentinel.md`.

Co-authored-by: SuvenSeo <263689617+SuvenSeo@users.noreply.github.com>
@google-labs-jules

Copy link
Copy Markdown

👋 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.

@vercel

vercel Bot commented Jun 10, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
seo-os-agent Ready Ready Preview, Comment Jun 10, 2026 7:49pm

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