Bug 595411

Summary:	krb5-appl 1.0 can't allocate ptys
Product:	Red Hat Enterprise Linux 6	Reporter:	Nalin Dahyabhai <nalin>
Component:	krb5-appl	Assignee:	Nalin Dahyabhai <nalin>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Zbysek MRAZ <zmraz>
Severity:	medium	Docs Contact:
Priority:	low
Version:	6.0	CC:	dpal, ebenes
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	krb5-appl-1.0.1-1.el6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-07-02 19:22:22 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	556115

Description Nalin Dahyabhai 2010-05-24 14:40:14 UTC

Description of problem:
At build-time, krb5-appl doesn't detect openpty(), so it doesn't know how to allocate pseudo-terminals for clients of remote login services.

Version-Release number of selected component (if applicable):
1.0-1

How reproducible:
Always

Steps to Reproduce:
1. Get a "host" key.
2. Turn on the eklogin service.
3. Try to use /usr/kerberos/bin/rlogin to log in.
  
Actual results:
Authentication succeeds, but the connection is closed immediately.

Expected results:
Shell prompt.

Additional info:
Found internally by Zbysek Mraz, filed as RT#6732, fixed in the upstream 1.0.1 release.

Comment 1 RHEL Program Management 2010-05-24 14:46:25 UTC

This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 2 Nalin Dahyabhai 2010-05-25 17:20:32 UTC

Testing will likely require selinux-policy-3.7.19-21.el6, which fixes bug #594833.

Comment 5 releng-rhel@redhat.com 2010-07-02 19:22:22 UTC

Red Hat Enterprise Linux Beta 2 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.