-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 01/31/07 20:00, Paul Lambert wrote:
> Mark Walker wrote:
>> One other thing. Another approach to this problem would be to have
>> some sort of code signing/authentication capabilities for the
>> postgresql server. For instance, you login as an administrator (some
>> sort of enhanced privs), you get to look at the databases you have
>> permission for. Otherwise, postgresql has to recognize the
>> application. Has this ever been discussed?
>
> I don't think it would be feasible for any RDBMS to recognise the
> connecting application, certainly in my view the effort it would take to
> alter the postmaster/odbc driver and others would be a lot more than the
> apparent gain from having that functionality.
I think that capability is already part of the ODBC spec. Well, at
least, the ODBC driver for Rdb (http://www.oracle.com/rdb) and it's
remote-access framework (SQL/Services) knows the name of the apps
that attach.
$ MCR SQLSRV_MANAGE71
SQLSRV> CONNECT SERVER;
Connecting to server ...
Connected
SQLSRV> SHOW CLIENT;
Service: VECTOR_REF
Connect Client Executor
Username Node State PID Application
PROC_RPT 138.69.183.166 RUNNING BOUND 2025a062 Winsql
PROC_RPT 138.69.183.216 RUNNING BOUND 202864f7 erdpro
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFFwUzAS9HxQb37XmcRAhc9AJ9QBUaSIWi7zNXaViGPE1CfgiG8qQCgump0
Ys78nYGFPzNjKrlnu/CfU0M=
=0OCA
-----END PGP SIGNATURE-----
