crossbario / crossbario/autobahn-python
Cryptobox serializer should be configurable
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.5k
- Forks
- 768
- PR merge metrics
- No merged PRs in 30d
Description
WAMP-cryptobox should allow for different serializers to be used when serializing the application payload that is to be end-to-end encrypted. See here and here.
The hooks to allow use of a configurable serializer are there, but it is hard-coded to "json" currently.
We should support all serializers that we support at the transport level.
Another question is what default cryptobox serializer to use when none was specified. And also how to let the user configure the cryptobox serializer if it shouldn't use the default one.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in autobahn/wamp/cryptobox.py at the referenced lines and inspect how serializers are selected at the transport level. Identify the serializers supported there and how cryptobox configuration is passed through. Done means application payload encryption can use the supported serializers and the default and user-configuration behavior are defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend-api-design, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100