Hello:
We have a SecUsers table that contains "Password" column, can SQL server
encrypt that column within that table? Please explain. If not, do we have
to buy a software that will encrypt single column in DB?
Thank you for your help.
Chai W.Is it possible for you not to store the password in the first place?
Try storing a hash (MD5 or SHA1 etc) of the password instead.
It has the benefit also, that the password is never transmitted over
the network (it must be hashed by the client application).
"Chai" <chai@.trs.state.il.us> wrote in message
news:OzJJtR7RDHA.3880@.tk2msftngp13.phx.gbl...
> Hello:
> We have a SecUsers table that contains "Password" column, can SQL server
> encrypt that column within that table? Please explain. If not, do we have
> to buy a software that will encrypt single column in DB?
> Thank you for your help.
> Chai W.
>
Showing posts with label password. Show all posts
Showing posts with label password. Show all posts
Thursday, March 8, 2012
Thursday, February 16, 2012
can Password change affecting replication
Hi all,
Wew have a need to change the sa password of all our servers. How can change
in the sa password affect the replication.
RegarDs,
JerriN
It all depends
It will have an impact if you are using SQL authentication
for any of the agents. If it is a typical setup, the replication agents will
run under the impersonation of the SQL Server agent's login, which is
typically the same login that SQL Server itself uses, so there should be no
impact at all.
HTH,
Paul Ibison
Wew have a need to change the sa password of all our servers. How can change
in the sa password affect the replication.
RegarDs,
JerriN
It all depends
It will have an impact if you are using SQL authenticationfor any of the agents. If it is a typical setup, the replication agents will
run under the impersonation of the SQL Server agent's login, which is
typically the same login that SQL Server itself uses, so there should be no
impact at all.
HTH,
Paul Ibison
can Password be hacked?
Can password be hacked? Because my friend ever say, there is a software can
hack SQL Server. Is it true? If yes, how to avoid from hacker? and What name
program that can do it?
which is more secure, use login with "Windows authentication" or "SQL
authentication"?Hi
Any server may be open to a brute force attack, and therefore ensuring
strong passwords is essential. Auditing login failures therefore important.
The main problem in the past has been that passwords have not been mandatory
,
therefore making it easy for someone to obtain access.
Windows authentication is more secure.
This may help:
http://www.microsoft.com/technet/pr...n/sp3sec01.mspx
John
"Bpk. Adi Wira Kusuma" wrote:
> Can password be hacked? Because my friend ever say, there is a software ca
n
> hack SQL Server. Is it true? If yes, how to avoid from hacker? and What na
me
> program that can do it?
> which is more secure, use login with "Windows authentication" or "SQL
> authentication"?
>
>|||Windows Authentication is recognized as the more secure option and is
recommended wherever possible. It's as secure as Windows is but there's no
such thing as absolute security.
David Portas
SQL Server MVP
--|||> Can password be hacked? Because my friend ever say, there is a software can
> hack SQL Server. Is it true? If yes, how to avoid from hacker? and What na
me
> program that can do it?
In theory, all passwords of any kind can be hacked. The real question "Can t
he
password be hacked in a timely fashion such that it is still useful?" What m
akes
SQL users weaker as a security structure than Windows Authentication has not
hing
to do with the encryption scheme. It has to do with other featuers like
disabling passwords after a specified number of attempts, requiring password
periodic password changes, logging failed password attempts and most
importantly, not sending the username and password in the clear to authentic
ate.
Some of these issues have been addressed in SQL 2005.
> which is more secure, use login with "Windows authentication" or "SQL
> authentication"?
Windows authentication is far more secure than SQL authentication.
Thomas
hack SQL Server. Is it true? If yes, how to avoid from hacker? and What name
program that can do it?
which is more secure, use login with "Windows authentication" or "SQL
authentication"?Hi
Any server may be open to a brute force attack, and therefore ensuring
strong passwords is essential. Auditing login failures therefore important.
The main problem in the past has been that passwords have not been mandatory
,
therefore making it easy for someone to obtain access.
Windows authentication is more secure.
This may help:
http://www.microsoft.com/technet/pr...n/sp3sec01.mspx
John
"Bpk. Adi Wira Kusuma" wrote:
> Can password be hacked? Because my friend ever say, there is a software ca
n
> hack SQL Server. Is it true? If yes, how to avoid from hacker? and What na
me
> program that can do it?
> which is more secure, use login with "Windows authentication" or "SQL
> authentication"?
>
>|||Windows Authentication is recognized as the more secure option and is
recommended wherever possible. It's as secure as Windows is but there's no
such thing as absolute security.
David Portas
SQL Server MVP
--|||> Can password be hacked? Because my friend ever say, there is a software can
> hack SQL Server. Is it true? If yes, how to avoid from hacker? and What na
me
> program that can do it?
In theory, all passwords of any kind can be hacked. The real question "Can t
he
password be hacked in a timely fashion such that it is still useful?" What m
akes
SQL users weaker as a security structure than Windows Authentication has not
hing
to do with the encryption scheme. It has to do with other featuers like
disabling passwords after a specified number of attempts, requiring password
periodic password changes, logging failed password attempts and most
importantly, not sending the username and password in the clear to authentic
ate.
Some of these issues have been addressed in SQL 2005.
> which is more secure, use login with "Windows authentication" or "SQL
> authentication"?
Windows authentication is far more secure than SQL authentication.
Thomas
Tuesday, February 14, 2012
can objects in sql server change your nt login password
hi guys,
i was wondering if there is a bug in sql server 2000 that upon changing settings in the sqlserver agent or sqlserver services that it will actually change your nt user password.
a strange occurence happened to me i switched the sqlmail to a different outlook profile that is MAPI compliant i had to stop and start the sql server agent upon restart it said it could not log me in b/c my nt logon failed (i guess you can figure out by now that i have authentication as NT in my set up of sql server agent). well me knowing microsoft products i was like ah i will just reboot the machine) well upon reboot my administrator password which is empty "null value"no longer is valid.
now noone in the company said that they changed the administrator password and it is not logged into a domain so the machine is not on our companys network. we log in local to the machine as the administrator. the last things that i played around in with sql server was replication setting it up as a publisher and deleteing it and changing a mapi profile. is there anywhere in sql 2000 that messing with any setting that it will actually affect your windows nt user login?? i know i cant be loosing my mind here and i hope someone at my company wouldnt sabotage my machine. right now i have two options i can reinstall win 2000 and choose repair hoping that i will not lose my sql 2000 info or i can try a password cracker. any suggestions that might of cause this to happen?
regards,
Robertof course Microsoft is always providing use with new features, but I doubt this unlikely. What you described sounds exactly as if the user password had been changed at the OS level. The password could have been changed by mistake.
i was wondering if there is a bug in sql server 2000 that upon changing settings in the sqlserver agent or sqlserver services that it will actually change your nt user password.
a strange occurence happened to me i switched the sqlmail to a different outlook profile that is MAPI compliant i had to stop and start the sql server agent upon restart it said it could not log me in b/c my nt logon failed (i guess you can figure out by now that i have authentication as NT in my set up of sql server agent). well me knowing microsoft products i was like ah i will just reboot the machine) well upon reboot my administrator password which is empty "null value"no longer is valid.
now noone in the company said that they changed the administrator password and it is not logged into a domain so the machine is not on our companys network. we log in local to the machine as the administrator. the last things that i played around in with sql server was replication setting it up as a publisher and deleteing it and changing a mapi profile. is there anywhere in sql 2000 that messing with any setting that it will actually affect your windows nt user login?? i know i cant be loosing my mind here and i hope someone at my company wouldnt sabotage my machine. right now i have two options i can reinstall win 2000 and choose repair hoping that i will not lose my sql 2000 info or i can try a password cracker. any suggestions that might of cause this to happen?
regards,
Robertof course Microsoft is always providing use with new features, but I doubt this unlikely. What you described sounds exactly as if the user password had been changed at the OS level. The password could have been changed by mistake.
Subscribe to:
Posts (Atom)