Skip to content

Use of a Broken or Risky Cryptographic Algorithm #245

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

Closed
j10i2 opened this issue Dec 7, 2022 · 2 comments
Closed

Use of a Broken or Risky Cryptographic Algorithm #245

j10i2 opened this issue Dec 7, 2022 · 2 comments

Comments

@j10i2
Copy link

j10i2 commented Dec 7, 2022

Hello, Dear Community!

I mentioned, that in Auth.go code we use a SHA-1 hash function for Authentification purposes.
image

Is it suitable to change this hash function to newer such as SHA-2 or SHA-3? SHA-1 is cryptographically broken and should not be used for secure applications.

Thank you!

@R-omk
Copy link

R-omk commented Dec 7, 2022

tarantool/tarantool#7770

@oleg-jukovec
Copy link
Collaborator

Hello, thank you for the issue! At the moment Tarantool does not support any other authentification method.

There are plans to add another authorization mechanism to Tarantool EE, but it won't be available in Tarantool Community Edition:
#243

If you want any other authorization method, then you could to open an issue in Tarantool:
https://github.com/tarantool/tarantool/

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

No branches or pull requests

3 participants