Content-Type: text/plain
Content-Disposition: inline
Content-Transfer-Encoding: binary
MIME-Version: 1.0
X-Mailer: MIME-tools 5.427 (Entity 5.427)
X-RT-Original-Encoding: iso-8859-1
Content-Length: 3364

From krb5-bugs-incoming-bounces@PCH.mit.edu  Wed May 26 15:00:47 2010
Return-Path: <krb5-bugs-incoming-bounces@PCH.mit.edu>
Received: from pch.mit.edu (PCH.MIT.EDU [18.7.21.90])
	by krbdev.mit.edu (Postfix) with ESMTP id 027DD3E716;
	Wed, 26 May 2010 15:00:46 -0400 (EDT)
Received: from pch.mit.edu (pch.mit.edu [127.0.0.1])
	by pch.mit.edu (8.13.6/8.12.8) with ESMTP id o4QJ0kfD016158;
	Wed, 26 May 2010 15:00:46 -0400
Received: from mailhub-dmz-2.mit.edu (MAILHUB-DMZ-2.MIT.EDU [18.7.62.37])
	by pch.mit.edu (8.13.6/8.12.8) with ESMTP id o4QIxSAQ015949
	for <krb5-bugs-incoming@PCH.mit.edu>; Wed, 26 May 2010 14:59:28 -0400
Received: from dmz-mailsec-scanner-8.mit.edu (DMZ-MAILSEC-SCANNER-8.MIT.EDU
	[18.7.68.37])
	by mailhub-dmz-2.mit.edu (8.13.8/8.9.2) with ESMTP id o4QIwuLv013971
	for <krb5-bugs@mit.edu>; Wed, 26 May 2010 14:59:27 -0400
X-AuditID: 12074425-b7d00ae000002295-44-4bfd6f8f92ec
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28])
	by dmz-mailsec-scanner-8.mit.edu (Symantec Brightmail Gateway) with
	SMTP id 6F.22.08853.F8F6DFB4; Wed, 26 May 2010 14:59:27 -0400 (EDT)
Received: from int-mx04.intmail.prod.int.phx2.redhat.com
	(int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.17])
	by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id o4QIxQ7p020490
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK)
	for <krb5-bugs@mit.edu>; Wed, 26 May 2010 14:59:26 -0400
Received: from blade.bos.redhat.com (blade.bos.redhat.com [10.16.0.23])
	by int-mx04.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP
	id o4QIxPhh022769
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <krb5-bugs@mit.edu>; Wed, 26 May 2010 14:59:26 -0400
Received: from blade.bos.redhat.com (blade.bos.redhat.com [127.0.0.1])
	by blade.bos.redhat.com (8.14.4/8.14.3) with ESMTP id o4QIxPDW007550
	for <krb5-bugs@mit.edu>; Wed, 26 May 2010 14:59:25 -0400
Received: (from nalin@localhost)
	by blade.bos.redhat.com (8.14.4/8.14.4/Submit) id o4QIxOOe007548;
	Wed, 26 May 2010 14:59:24 -0400
Date: Wed, 26 May 2010 14:59:24 -0400
Message-Id: <201005261859.o4QIxOOe007548@blade.bos.redhat.com>
To: krb5-bugs@mit.edu
Subject: kprop and kpropd don't support IPv6
From: nalin@redhat.com
X-send-pr-version: 3.99
X-Scanned-By: MIMEDefang 2.67 on 10.5.11.17
X-Brightmail-Tracker: AAAAARRkZHk=
X-Mailman-Approved-At: Wed, 26 May 2010 15:00:45 -0400
X-BeenThere: krb5-bugs-incoming@mailman.mit.edu
X-Mailman-Version: 2.1.6
Precedence: list
Sender: krb5-bugs-incoming-bounces@PCH.mit.edu
Errors-To: krb5-bugs-incoming-bounces@PCH.mit.edu

>Submitter-Id:	net
>Originator:	
>Organization:
>Confidential:	no
>Synopsis:	kprop and kpropd don't support IPv6
>Severity:	non-critical
>Priority:	medium
>Category:	krb5-admin
>Class:		change-request
>Release:	1.8.1
>Environment:
	
System: Linux blade.bos.redhat.com 2.6.33.3-85.fc13.x86_64 #1 SMP Thu May 6 18:09:49 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux
Architecture: x86_64

>Description:
	The kprop client uses IPv4-only APIs when contacting a kprop server,
	and kpropd only expects IPv4 sockets when run either via inetd or in
	standalone mode.
>How-To-Repeat:
	Set up kpropd on an IPv6-capable host and make sure that the only
	address the client can find is an IPv6 address.  The client will fail
	to resolve the address, and the server will only bind to an IPv4
	socket in standalone mode.