Skip to content
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

Migrate to CUID2 #9

Open
wgordon17 opened this issue Jan 22, 2023 · 2 comments · May be fixed by #10
Open

Migrate to CUID2 #9

wgordon17 opened this issue Jan 22, 2023 · 2 comments · May be fixed by #10

Comments

@wgordon17
Copy link

CUID has been marked as deprecated and insecure: https://github.com/paralleldrive/cuid

They recommend migrating to CUID2: https://github.com/paralleldrive/cuid2

There is a CUID2 python port available here: https://github.com/overflowdigital/cuid2.py

@wgordon17
Copy link
Author

Heh, guess I should've read the README a bit better

It can utilise cuid, ksuid, ulid or any other string-based UID generation systems.

So this is just a fix for the README table to point to the CUID2 python port 😉

wgordon17 added a commit to wgordon17/django-charid-field that referenced this issue Jan 22, 2023
@djm
Copy link
Contributor

djm commented Jan 25, 2023

@wgordon17 Nice, I appreciate the heads-up on this as that seems to be a relatively new revelation (21 days ago). We'll update the README shortly.

For us, thankfully we use them only as identifiers and are not using them in any kind of secure context (such as token based password reset, etc).

wgordon17 added a commit to wgordon17/django-charid-field that referenced this issue May 21, 2023
@wgordon17 wgordon17 linked a pull request May 21, 2023 that will close this issue
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 a pull request may close this issue.

2 participants