Bug 462890 - typo in "ksu: Server not found in Kerberos database while geting credentials from kdc"
typo in "ksu: Server not found in Kerberos database while geting credentials ...
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: krb5 (Show other bugs)
5.2
All Linux
medium Severity low
: rc
: ---
Assigned To: Nalin Dahyabhai
BaseOS QE
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-09-19 10:31 EDT by Marek Mahut
Modified: 2009-09-02 07:48 EDT (History)
3 users (show)

See Also:
Fixed In Version: 1.6.1-33.el5
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-09-02 07:48:50 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Marek Mahut 2008-09-19 10:31:59 EDT
Description of problem:

I think there is a typo in error message below, "geting".

 -bash-3.2$ ksu
 ksu: Server not found in Kerberos database while geting credentials from kdc
 Authentication failed.
 -bash-3.2$ 


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

krb5-workstation-1.6.1-25.el5


How reproducible:

Execute "ksu" with an invalid server.


Steps to Reproduce:
1. ksu :)
  
Actual results:

 -bash-3.2$ ksu
 ksu: Server not found in Kerberos database while geting credentials from kdc
 Authentication failed.
 -bash-3.2$ 

Expected results:

 -bash-3.2$ ksu
 ksu: Server not found in Kerberos database while getting credentials from kdc
 Authentication failed.
 -bash-3.2$
Comment 1 Nalin Dahyabhai 2008-09-19 11:59:55 EDT
Good eye!
Comment 6 errata-xmlrpc 2009-09-02 07:48:50 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2009-1378.html

Note You need to log in before you can comment on or make changes to this bug.