Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UK9Lt-0003Bp-T0 for pgsql-admin@arkaria.postgresql.org; Mon, 25 Mar 2013 15:30:26 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1UK9Lt-00072b-DN for pgsql-admin@arkaria.postgresql.org; Mon, 25 Mar 2013 15:30:25 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UK9Ls-00072W-LU for pgsql-admin@postgresql.org; Mon, 25 Mar 2013 15:30:24 +0000 Received: from mail-db8lp0185.outbound.messaging.microsoft.com ([213.199.154.185] helo=db8outboundpool.messaging.microsoft.com) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UK9Lm-0003d7-U1 for pgsql-admin@postgresql.org; Mon, 25 Mar 2013 15:30:24 +0000 Received: from mail92-db8-R.bigfish.com (10.174.8.235) by DB8EHSOBE002.bigfish.com (10.174.4.65) with Microsoft SMTP Server id 14.1.225.23; Mon, 25 Mar 2013 15:30:16 +0000 Received: from mail92-db8 (localhost [127.0.0.1]) by mail92-db8-R.bigfish.com (Postfix) with ESMTP id CA74D4014F; Mon, 25 Mar 2013 15:30:16 +0000 (UTC) X-Forefront-Antispam-Report: CIP:157.56.248.133; KIP:(null); UIP:(null); IPV:NLI; H:AMXPRD0310HT004.eurprd03.prod.outlook.com; RD:none; EFVD:NLI X-SpamScore: 0 X-BigFish: PS0(zzbb2dI98dI1432Ic8kzz1f42h1ee6h1de0h1d18h1202h1e76h1d1ah1d2ahzz8275ch17326ahz2dh2a8h668h839h947hd25he5bhf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h1765h18e1h190ch1946h19b4h19c3h19ceh1ad9h1b0ah1155h) Received: from mail92-db8 (localhost.localdomain [127.0.0.1]) by mail92-db8 (MessageSwitch) id 1364225414527340_1067; Mon, 25 Mar 2013 15:30:14 +0000 (UTC) Received: from DB8EHSMHS020.bigfish.com (unknown [10.174.8.232]) by mail92-db8.bigfish.com (Postfix) with ESMTP id 73F8B24004B; Mon, 25 Mar 2013 15:30:14 +0000 (UTC) Received: from AMXPRD0310HT004.eurprd03.prod.outlook.com (157.56.248.133) by DB8EHSMHS020.bigfish.com (10.174.4.30) with Microsoft SMTP Server (TLS) id 14.1.225.23; Mon, 25 Mar 2013 15:30:11 +0000 Received: from [137.73.122.214] (137.73.122.214) by pod51013.outlook.com (10.255.55.39) with Microsoft SMTP Server (TLS) id 14.16.275.6; Mon, 25 Mar 2013 15:30:07 +0000 Message-ID: <51506D7D.5090105@kcl.ac.uk> Date: Mon, 25 Mar 2013 15:30:05 +0000 From: Tim Watts User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130308 Thunderbird/17.0.4 MIME-Version: 1.0 To: Stephen Frost CC: Tom Lane , "pgsql-admin@postgresql.org" Subject: Re: Postgresql 8.4 GSSAPI auth with fallback to password prompting? References: <514AFB73.6050300@kcl.ac.uk> <5c910ac4f9fa4dc78f1ba6747182b671@DBXPRD0310HT003.eurprd03.prod.outlook.com> <51502949.6000903@kcl.ac.uk> <20130325132557.GM4361@tamriel.snowman.net> <8661258abad94cca91cc7bd4d3d84b26@DBXPRD0310HT002.eurprd03.prod.outlook.com> <5150659E.8070401@kcl.ac.uk> In-Reply-To: Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [137.73.122.214] X-OriginatorOrg: kcl.ac.uk X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org On 25/03/13 15:17, Stephen Frost wrote: > Tim, > > * Tim Watts (tim.j.watts@kcl.ac.uk) wrote: >> I presume the protocol does not allow the server to send a succession of >> "Type: Authentication request" packets with different Authentication >> types until it deems that one is acceptable? > > Even if it did, existing clients would very likely be confused by it.. > > To be honest, I don't have a solution in mind for how to make this > happen, I was really just pointing out that there's a difference between > "we won't do that because we don't trust the sysadmin" and "that's not > an option due to how the system works today". No no - fully understood :) I appreciate the candid and reasoned arguments :) I wish I could help - but I more of a sysamdin and less of a developer. But it is *very* helpful to know that something *is not possible* and *is likely to not be possible for a long time, if ever*. That allows me as a humble user of the software to plan deployment :) > Perhaps one option would > be to look at the Negotiate protocol which mod_auth_kerb and friends use > and perhaps have that as an explicitly new auth mechanism. A server set > up to provide that would, of course, have to consider if its users > supported it or not but that's true already- you can have situation > already though, a given client might not support gssapi, for example. A "negotiate" option would be very cool. I will expect nothing (on the basis it's free software, I have no rights ;-> ). Save to say I think Postgresql is very cool already and has been for the last 12 years I've been using it... All the best, Tim -- Tim Watts Tel (VOIP): +44 (0)1580 848360 Systems Manager Digital Humanities, King's College London Systems Messages and Notifications: https://systemsblog.cch.kcl.ac.uk/ Personal Blog: http://squiddy.blog.dionic.net/ "She got her looks from her father. He's a plastic surgeon." -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin