User: Password:
|
|
Subscribe / Log in / New account

A serious PostgreSQL security fix

A serious PostgreSQL security fix

Posted Apr 7, 2013 9:32 UTC (Sun) by cortana (subscriber, #24596)
In reply to: A serious PostgreSQL security fix by gdt
Parent article: A serious PostgreSQL security fix

It doesn't?


(Log in to post comments)

A serious PostgreSQL security fix

Posted Apr 7, 2013 12:53 UTC (Sun) by gdt (subscriber, #6284) [Link]

I didn't mean "support" so much as "requires". My apologies for not expressing my thought more clearly.

A serious PostgreSQL security fix

Posted Apr 7, 2013 13:59 UTC (Sun) by cesarb (subscriber, #6266) [Link]

AFAIK, the authentication is per-database, which means it has to read the database name from the client before authenticating, even if you are using certificates.

The bug in question involved the client sending an invalid database name.

Oops.

A serious PostgreSQL security fix

Posted Apr 7, 2013 22:40 UTC (Sun) by hummassa (subscriber, #307) [Link]

IIRC correctly my SSL/TLS, the authentication (and the start of encrypting the whole session) comes before anything else. I suppose when the client asks for connection to a database, he is already autheticated via his cert (and the dbms can check if he can effectively connect to *that* particular db).

TLS authorization

Posted Apr 8, 2013 12:44 UTC (Mon) by tialaramex (subscriber, #21167) [Link]

I don't know specifically about PostgreSQL but generally when you have a single SSL endpoint you make all the "authorization" decisions later, after the SSL handshake is done and you're "secure".

So very likely you can connect to any TLS-supporting PostgreSQL server with proof that you're "A Badman <evil@example.com>" and the server will go try to access the database to determine whether this "A Badman" person is authorized. With this particular bug, that's already too late.

In principle the server _could_ round up all the rules for authorization for all the databases, and then do early reject for connections that don't match, but that would be a lot of extra work to handle a slow path case, and (unless you know about this bug) there's no reason to approach it that way.

A serious PostgreSQL security fix

Posted Apr 7, 2013 23:31 UTC (Sun) by dlang (subscriber, #313) [Link]

SSL/TLS authentication has a very high overhead. Postgresql supports SSL/TLS authentication, but it also supports many other types of authentication so that you can choose what one is the best fit for your needs.


Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds