fix(wecom): support pic_url and fix AES key base64 padding for image …#12390
Open
zogwei wants to merge 1 commit into
Open
fix(wecom): support pic_url and fix AES key base64 padding for image …#12390zogwei wants to merge 1 commit into
zogwei wants to merge 1 commit into
Conversation
…decryption WeCom AI Bot sends image URLs in the `pic_url` field (not `url`). Additionally, the `aeskey` is 43-character base64 without standard padding, causing base64.b64decode() to raise Incorrect padding. Changes: - Recognize `pic_url` in inbound media references - Add `_decode_wecom_aes_key()` to handle unpadded base64 - Use the new decoder in `_decrypt_file_bytes()` - Add `_try_decrypt_variants()` as fallback for different AES modes
Collaborator
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
…decryption
WeCom AI Bot sends image URLs in the
pic_urlfield (noturl). Additionally, theaeskeyis 43-character base64 without standard padding, causing base64.b64decode() to raise Incorrect padding.Changes:
pic_urlin inbound media references_decode_wecom_aes_key()to handle unpadded base64_decrypt_file_bytes()_try_decrypt_variants()as fallback for different AES modesWhat does this PR do?
Related Issue
Fixes #
Type of Change
Changes Made
How to Test
Checklist
Code
fix(scope):,feat(scope):, etc.)pytest tests/ -qand all tests passDocumentation & Housekeeping
docs/, docstrings) — or N/Acli-config.yaml.exampleif I added/changed config keys — or N/ACONTRIBUTING.mdorAGENTS.mdif I changed architecture or workflows — or N/AFor New Skills
hermes --toolsets skills -q "Use the X skill to do Y"Screenshots / Logs