Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1W34pQ-0001uV-Qm for pgsql-admin@arkaria.postgresql.org; Tue, 14 Jan 2014 14:18:53 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1W34pQ-0006Eq-Ah for pgsql-admin@arkaria.postgresql.org; Tue, 14 Jan 2014 14:18:52 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1W34pP-0006Ek-H7 for pgsql-admin@postgresql.org; Tue, 14 Jan 2014 14:18:51 +0000 Received: from mail-wg0-x22a.google.com ([2a00:1450:400c:c00::22a]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1W34pM-0007Im-VN for pgsql-admin@postgresql.org; Tue, 14 Jan 2014 14:18:50 +0000 Received: by mail-wg0-f42.google.com with SMTP id l18so3998420wgh.5 for ; Tue, 14 Jan 2014 06:18:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:subject:from:reply-to:to:cc:date:in-reply-to:references :content-type:mime-version:content-transfer-encoding; bh=kzCZEZzE9qkBXHRF2p/dPFvvD/j5HML0Kad0SgK/+Fc=; b=TNGLI248qntkfWk2oanf0djHXyWIvZIYWsogpbKn31+98mmUNi5QtQvJPIa0aIfANQ 2/+2cHW3C28NsovulqJeWCiH4HDi9/J3dg0OCcj08vYRiWeXbm+p3+YgxOhsskbsGoKx b744v7S0bqxWi6nKF/SD2YtMwhSG2ywft6/ziTKlXTyLJ/YlxhkCLI7VAInyaAKSs9cB 8RXTK0XE2haz7ze1J1It7zVqfrFK5XaWmaZChj7IGcj9HHNuo4zot05jCCf8t4E3Mybp OhLDlZtLYmKCp9PzvuO/OU206CRxeMEry1FUEDFgAl7KK9rNl7pA1MhD1fSuDynJzLdy pklg== X-Received: by 10.194.234.65 with SMTP id uc1mr27887221wjc.39.1389709126631; Tue, 14 Jan 2014 06:18:46 -0800 (PST) Received: from [192.168.0.20] (89.141.101.243.dyn.user.ono.com. [89.141.101.243]) by mx.google.com with ESMTPSA id dm2sm1678468wib.8.2014.01.14.06.18.45 for (version=SSLv3 cipher=RC4-SHA bits=128/128); Tue, 14 Jan 2014 06:18:45 -0800 (PST) Message-ID: <1389709125.9086.61.camel@turing> Subject: Re: GSSAPI auth issue with windows 7 client, postgresql 9.2.3 linux server From: jaime soler Reply-To: jaime.soler@gmail.com To: Stephen Frost Cc: pgsql-admin@postgresql.org Date: Tue, 14 Jan 2014 15:18:45 +0100 In-Reply-To: <20140114131936.GU2686@tamriel.snowman.net> References: <1389702744.9086.55.camel@turing> <20140114131936.GU2686@tamriel.snowman.net> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.6.4-0ubuntu1 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-Pg-Spam-Score: -2.0 (--) 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 El mar, 14-01-2014 a las 08:19 -0500, Stephen Frost escribió: > * jaime soler (jaime.soler@gmail.com) wrote: > > psql: SSPI continuation error: The encryption type requested is not > > supported by the KDC. (80090342) > > [...] > > > ktpass -out postgres.keytab -princ > > postgres/hostname@domain -mapUser postgres -pass > > XXX -crypto DES-CBC-MD5 > > Not 100% sure this is it, but it looks like you're using an ancient > encryption algo which is no longer supported by MIT Kerberos (very > intentionally...). Why aren't you using AES256 instead? So, should I use ALL as argument to -crypto option as it follows ? ktpass -out postgres.keytab -princ postgres/hostname@domain -mapUser postgres -pass XXX -crypto ALL Thanks, Jaime > > Thanks, > > Stephen -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin