Dual-Engine Runtime with E2EE IPC and Global Bindings#13
Conversation
Redesigned the AlloyScript architecture to utilize a secure dual-engine model: - Implemented JS_BindGlobal in MicroQuickJS for dynamic C function binding. - Implemented webview_bind_global in WebView for globalThis bindings. - Established a transparent E2EE IPC channel using X25519 and AES-256-GCM. - Isolated logic execution in MicroQuickJS while restricting WebView to browser APIs. - Reorganized codebase into deps/ (MIT) and src/ (CC0) with proper licensing. - Fixed memory leaks in cryptographic primitives. - Updated documentation to reflect the new security model. Co-authored-by: yumin-chen <10954839+yumin-chen@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. |
This submission implements a secure dual-engine architecture for AlloyScript.
Key changes:
JS_BindGlobalto MicroQuickJS andwebview_bind_globalto the WebView core, enabling runtime C-to-JS function mapping.deps/under MIT licenses and moved primary engine logic tosrc/under CC0.ReadMe.mdto detail the new architecture and security principles.PR created automatically by Jules for task 13422048934489669311 started by @yumin-chen