Req #14564 [Opn->Wfx]: Trusted Connections Not Supported
| From: | kalle@php.net | Date: | Sat, 15 Oct 2016 23:06:31 +0000 |
| Subject: | Req #14564 [Opn->Wfx]: Trusted Connections Not Supported | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-204788@lists.php.net to get a copy of this message | ||
Edit report at https://bugs.php.net/bug.php?id=14564&edit=1
ID: 14564
Updated by: kalle@php.net
Reported by: parkins dot graham at ppc-consulting dot co dot uk
Summary: Trusted Connections Not Supported
-Status: Open
+Status: Wont fix
Type: Feature/Change Request
Package: MSSQL related
Operating System: Windows NT 4/SQL Server 7
PHP Version: 4.1.0
Block user comment: N
Private report: N
New Comment:
With MSSQL being removed from PHP as of PHP7.0, and ext/mssql not having a maintainer, I'm
gonna close this report as a Won't fix, until maybe one day it will find a new maintainer.
Alternatively you can use sqlsrv from Microsoft if you are on Windows, or pdo_dblib if you are on
Unix.
Previous Comments:
------------------------------------------------------------------------
[2002-03-12 04:58:14] g dot sollis at syntegra dot nl
This would be great, as i too think it is a potential security risk to have usernames and passwords
in the source-code. But instead of keeping it in MS-SQL functions i suggest it is also available for
ODBC connections.
Just another small suggestion i thought of; maybe it's a good idea to implement a second (form
of)
[dbtype]_connect() function, which will accept something like an ODBC Connection String. This way it
would be possible to either use the following:
1. DSN connection with specified user & password
2. DSN connection with trusted connection to db-server
3. DSN-less connection with connection string
The only way it is available now is by using the COM functionality. Which is OK if you want to go
that way, but that does mean rewriting a lot of code if there is no db-abstraction layer in use.
------------------------------------------------------------------------
[2001-12-17 11:12:07] parkins dot graham at ppc-consulting dot co dot uk
I consider the inclusion of database usernames and passwords in scripts to be a security risk.
In a Windows environment it is possible to access SQL Server via a trusted connection. This uses
the context of the current logged in user.
Furthermore it is possible to configure IIS and presumably Apache to use a particular user account
to service requests.
It is therefore possible (for example under ASP) to open a database connection without specifying a
username or password in the script because the context of the current user account has permission to
access the SQL Server.
I would be happy if this functionality could be implmented in the MS SQL Server extension.
------------------------------------------------------------------------
--
Edit this bug report at https://bugs.php.net/bug.php?id=14564&edit=1