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

Use secure authentication for TimescaleDB #1739

Closed
steven-sheehy opened this issue Mar 22, 2021 · 0 comments · Fixed by #1795
Closed

Use secure authentication for TimescaleDB #1739

steven-sheehy opened this issue Mar 22, 2021 · 0 comments · Fixed by #1795
Assignees
Labels
database Area: Database enhancement Type: New feature P2
Milestone

Comments

@steven-sheehy
Copy link
Member

Problem
The default authentication for PostgreSQL is the insecure md5. Since our TimescaleDB is new we have a chance to improve the security of our database authentication without causing breaking changes.

Solution
Use a secure form of authentication like SCRAM-SHA-256 password authentication or if we're using TLS anyway we can utilize certificate authentication.

Alternatives

Additional Context

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
database Area: Database enhancement Type: New feature P2
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants