Implement AES-IGE and MTProto package structure - #4
Conversation
Co-authored-by: SWORDIntel <117012829+SWORDIntel@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. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
Implemented AES-IGE mode in pure Python following the project's rigid constraints and structured the MTProto subpackage layout.
AES256to a generalizedAEScipher capable of 128, 192, and 256-bit encryption (based on key length), retaining perfect backward compatibility with existing AES tests.AESIGEimplementing Infinite Garble Extension via the 32-byte two-block IV recurrence standard.src/crypto_standalone/mtproto/skeleton featuringconfig.py(with dataclass limits),session.py(for the state structure and sequence bounding), and transport architectures.docs/IMPLEMENTATION.mdexplicitly capturing the cryptographic limitations (confidentiality only, non-constant-time) and examples.PR created automatically by Jules for task 16354817585876427839 started by @SWORDIntel