Skip to content

Conversation

@tknarr
Copy link

@tknarr tknarr commented Jun 4, 2016

Add AES192 and AES256 as supported encryption methods.
Add version bytes to distinguish between AES128, AES192 and AES256 encryption in tokens.

@tknarr
Copy link
Author

tknarr commented Jun 4, 2016

Associated changes to the Ruby implementation are in closed pull requests tknarr/fernet-rb#1 and tknarr/fernet-cli#1 in my forks.

@tuupola
Copy link

tuupola commented May 8, 2017

Any news about this?

@brianorwhatever
Copy link

It's unfortunate this isn't getting looked at. AES128 is not good enough for modern applications and I'm sure many people would like to see this enhancement merged in.

@tknarr
Copy link
Author

tknarr commented Mar 9, 2018

I'm wondering if the spec's even maintained.

@kennyp
Copy link
Member

kennyp commented Dec 8, 2021

@tknarr I'll take a look at this and the related fernet-rb PR. Thanks!

@bitkeks
Copy link

bitkeks commented Mar 13, 2024

Given the spec is currently pinned to AES128, will this PR move forward in the future?

It'd be good to know if Fernet keeps up with comparable specs (comparable algorithms) in regards to levels of encryption.

@clach04
Copy link

clach04 commented Nov 21, 2024

@tknarr From comments it seems like there is interest in this, but not from the official project.

Have you considered hard forking and renaming (e.g. to Anise, or something) and documenting it a superset of Fernet and thus backward compatible with the Fernet spec?

I realize your focus and goals may have changed in the last 8 year 😉

From what I read your proposed spec and Ruby code changes, look good 👍 .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants