Hot answers tagged security
You could create a domain group that you could use to create as login and user on your SQL Server and YourDatabase. After creating the domain group, you could do something like: USE [master] GO CREATE LOGIN [DOMAIN\AllUsersForYourDatabase] FROM WINDOWS GO USE [YourDatabase] GO CREATE USER [DOMAIN\AllUsersForYourDatabase] FOR LOGIN ...
If your MySQL client/server version is a 5.6.x a way to avoid the WARNING message or putting a password in command line, you can use the mysql_config_editor tools: mysql_config_editor set --login-path=local --host=localhost --user=username --password Then you can use in your shell script: mysql --login-path=local -e "statement" Instead of: ...
Turns out the answer is actually to use the -p -- the long version allows you to set it to empty, like so: mysql --port=3307 --host=127.0.0.1 -uroot --password=
HeavenCore's reply answers the question. However there is another way to get around this without security flaws. Return output to a table, query the table with DBmail.
I was going to just comment the link to the SQL Server 2012 Best Practice security white paper...but found out Microsoft took it off the Internet for some reason. You might be able to find a cached version of it some where online, but I will paste in the contents of contained database section of the document here. There is also a BOL article for Security ...
A user must have a security context to access the ReplData database. That can be their own account, an AD group of which they are a member, or the guest user (if the guest user is enabled in the ReplData database). No permission need be granted on the ReplData.dbo.refData table as long as the ownership chain is unbroken. Since the refData table is owned ...
Only top voted, non community-wiki answers of a minimum length are eligible