🚀 go-pugleaf

Microsoft SQL Server 6.0 (and 4.21a) can be configured to operate in
three login security modes:

     Standard security mode:  is the default where SQL Server validates
the login connection through a nontrusted connection.  The user enters
a login id and password which are checked against the master..syslogins
table.  Passwords are stored in encrypted form in SQL 6.0.

     Integrated Security mode:  allows SQL Server to use Windows NT
authentication to validate logins for all connections.  This is through
trusted connections.  The user does not need to enter a SQL Server
login ID or password to connect to the SQL Server if he or she is
logged into an NT account that SQL Server already has registered.

     Mixed Security mode: allows login requests to be validated using
either integrated (trusted connection)
or standard (non-trusted connections) security.  Integrated security is
tried first and if that fails the SQL Server Login ID and Password
entered by the user are tried (Standard security).

I hope this helps answer your questions.

Christopher Sorensen
----------
From:  <mfv@ORNL.GOV>
To: Multiple recipients of list MSSQL-L
<netmail!MSSQL-L%DUKEFSB.BITNET@VTBIT.CC.VT.EDU>
Subject: SQL, NT 3.5, and passwords
Date: Monday, May 01, 1995 8:33AM

Let me preface my question by saying that I know absolutely nothing about
MS SQL Server.  I have been asked to find out how SQL running on NT 3.5
handles passwords.  I was told that SQL used to store passwords in clear
text, has that changed?  If SQL is running under NT 3.5, does it rely on the
NT authentication process?

If there are any books or an FAQ source, I would appreciate knowing where to
look.

Thanks,

Marty Davidson
mfv@ornl.gov