Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UK8Wh-0007uF-EG for pgsql-admin@arkaria.postgresql.org; Mon, 25 Mar 2013 14:37:31 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1UK8Wg-0001xs-U5 for pgsql-admin@arkaria.postgresql.org; Mon, 25 Mar 2013 14:37:30 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UK8Wg-0001xk-5p for pgsql-admin@postgresql.org; Mon, 25 Mar 2013 14:37:30 +0000 Received: from ch1ehsobe004.messaging.microsoft.com ([216.32.181.184] helo=ch1outboundpool.messaging.microsoft.com) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UK8WZ-0005kp-Ev for pgsql-admin@postgresql.org; Mon, 25 Mar 2013 14:37:29 +0000 Received: from mail119-ch1-R.bigfish.com (10.43.68.241) by CH1EHSOBE010.bigfish.com (10.43.70.60) with Microsoft SMTP Server id 14.1.225.23; Mon, 25 Mar 2013 14:37:21 +0000 Received: from mail119-ch1 (localhost [127.0.0.1]) by mail119-ch1-R.bigfish.com (Postfix) with ESMTP id AB75DA017E; Mon, 25 Mar 2013 14:37:21 +0000 (UTC) X-Forefront-Antispam-Report: CIP:157.56.252.5; KIP:(null); UIP:(null); IPV:NLI; H:DB3PRD0310HT003.eurprd03.prod.outlook.com; RD:none; EFVD:NLI X-SpamScore: -4 X-BigFish: PS-4(zzbb2dI98dId772h1432I1418Izz1f42h1ee6h1de0h1d18h1202h1e76h1d1ah1d2ahzz8275ch17326ahz2dh2a8h668h839h947hd25he5bhf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h1765h18e1h190ch1946h19b4h19c3h19ceh1ad9h1b0ah1155h) Received: from mail119-ch1 (localhost.localdomain [127.0.0.1]) by mail119-ch1 (MessageSwitch) id 1364222227525809_22579; Mon, 25 Mar 2013 14:37:07 +0000 (UTC) Received: from CH1EHSMHS027.bigfish.com (snatpool2.int.messaging.microsoft.com [10.43.68.238]) by mail119-ch1.bigfish.com (Postfix) with ESMTP id 4C443340053; Mon, 25 Mar 2013 14:37:07 +0000 (UTC) Received: from DB3PRD0310HT003.eurprd03.prod.outlook.com (157.56.252.5) by CH1EHSMHS027.bigfish.com (10.43.70.27) with Microsoft SMTP Server (TLS) id 14.1.225.23; Mon, 25 Mar 2013 14:37:05 +0000 Received: from [137.73.122.214] (137.73.122.214) by pod51013.outlook.com (10.255.44.38) with Microsoft SMTP Server (TLS) id 14.16.275.6; Mon, 25 Mar 2013 14:37:03 +0000 Message-ID: <5150610E.3090706@kcl.ac.uk> Date: Mon, 25 Mar 2013 14:37:02 +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: "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> <41b629dc89ba459b89bd1ccc20624326@DBXPRD0310HT005.eurprd03.prod.outlook.com> In-Reply-To: <41b629dc89ba459b89bd1ccc20624326@DBXPRD0310HT005.eurprd03.prod.outlook.com> 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: -2.6 (--) 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 13:25, Stephen Frost wrote: > Tim, > > * Tim Watts (tim.j.watts@kcl.ac.uk) wrote: >> I would have to respectfully take another point of view: that that >> particular judgement is probably better placed with the sysadmin >> rather than a blanket decision by the devs. > > It's not a blanket decision by any means- the current situation is that > such an option doesn't exist. It's not "it exists, but we disabled it > because we felt like it." > > Were someone to write the code to support such an option, it's entirely > possible it'd get committed (though likely with strong caveats about its > use in the documentation). That's totally fair... Not sure if I could. I hacked an option into Samba from a cold start once. On an equal footing, OpenLDAP's source code totally defeated me ;-> I might have a look to see if it looks "trivial" or "hard". >> Reason: Whilst the argument is solid in an ideal world (all clients >> are part of the kerberos realm), in reality it means that I cannot >> gain partial security improvements and I have to leave it running >> with PAM auth which ensures that passwords are chucked around 100% >> of the time. > > The pg_hba.conf allows you to migrate users or sets of users at a time. > Having a fall-back mechanism if Kerberos doesn't work is a different > thing. My experience has been that all clients (or at least, all in a > given IP range or for a set of users) *are* part of the Kerberos realm > because they're coming from Active Directory or another entrenched > Kerberos installation. That's specifically because that's how > Kerberos is intended to work and how it provides a strong > authentication mechanism. I think that laptops[1] and "BYOD" (Bring your own device, eg *pads) are going to make that scenario less common. [1] OK - it is perfectly possible to have a managed laptop. But it's harder than a managed desktop so I've not seen it outside of very large corporations with draconian policies on using their and only their devices. >> But it would be nice to be able to use kerberos tickets *where >> available* and fallback to password-interactive login where not. > > And I continue to contend that this is a very bad idea. But less bad than not using kerberos for anything... Cheers 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