| |||||||||||||
A serious PostgreSQL security fixA serious PostgreSQL security fixPosted Apr 7, 2013 13:59 UTC (Sun) by cesarb (subscriber, #6266)In reply to: A serious PostgreSQL security fix by gdt Parent article: A serious PostgreSQL security fix
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.
(Log in to post comments)
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).
|
|||||||||||||