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.

Sign up for GitHub

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

Jump to bottom

Document the dangers of allowing read-only access #26

Open
toolness opened this issue Mar 6, 2019 · 0 comments
Open

Document the dangers of allowing read-only access #26

toolness opened this issue Mar 6, 2019 · 0 comments

Comments

@toolness
Copy link
Contributor

toolness commented Mar 6, 2019

Based on the Postgres Exercises About Page, it looks like statement_timeout ought to be set for read-only connections to prevent DoS attacks (either intended or accidental). I'm not sure if it's possible to set this on a per-user basis or not.

The aforementioned about page contains other details on possible attacks.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@toolness