-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does it make sense to support a binary encoding? #7
Comments
Yes, totally makes sense IMO. I've wished for this myself once or twice. |
How would you go about doing it while keeping Fernet's format self-describing? Use of the "version" byte (more like "variant" in this case?) |
My first thought is to have two separate entry points and require |
I guess that would be sort of against the "you can't do it wrong" spirit |
I'm weakly opposed to adding it as an option, mostly to prevent option bloat. @alex - I'm more strongly opposed if pyca isn't going to add it as well. |
I'd have to think about it, but probably we'd add it as well /cc @dreid. |
I'm +1 on supporting the pre-base64 encoded form. I assume this would just be for tokens and not affect keys? |
Yeah: tokens only. |
Though this has crossed my mind, I've never wanted it enough Note that one can do it oneself as a workaround. It's not hard |
How about this: Before making any detailed decisions, I do have a specific application and lightweight benchmark. I'll hack in binary (aka "does less") fernet and see how much it matters, and post my result. |
@fdr any results from your performance tests? |
On Tue, Sep 2, 2014 at 1:10 AM, Keith Rarick [email protected]
|
Hi all. I'm interested in using binary bitstream communication using Fernet. How is the status binary encoding support in Fernet? |
I've noticed that encrypted payloads are base64 coded. Does it make any sense to have a binary mode? I'd like to use Fernet in a high-volume way (maybe that's against design ethos, I am not sure) and avoid paying for base64 in size blowup if possible.
The text was updated successfully, but these errors were encountered: