-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
Why we need user and permissions? #4334
Comments
database is an independent system, it can be accessed with or without applications, regardless of on-premises/off-premises, security is high on the priority list in the corporate infrastructure. |
I think database is neerly impossible to be set on a public enviroment. |
one has permission on OS doesn't mean one should have permission on db, they are different roles. "Nothing worse than a familiar enemy" |
I didn't mean we use ssh to connect the database. I mean just use a way like ssh to connect the database rather than using username and password. Well, there are two dimensions: user system and permission system. |
SSH, especially SSL/TLS are supported by many dbms, they're optional and have no conflict with user/password. |
Why not just put user and permissions all at application level rather than database level?
Database can act as a ssh server and application can act as a ssh client.
Database can just set
host, port, and ssh public key
.Application just link to the database.
That's all.
Why we need a system for user and permissions?
The text was updated successfully, but these errors were encountered: