2. What is the nature and description of the request?

krb telnetd doesn't output /etc/issue or /etc/issue.net. (It just outputs the
hardcoded banner including hostname, kernel version, and so on.)


3. Why does the customer need this? (List the business requirements here)

To ensure that any replacement software maintains the feature set of the
original so that applications / users don’t break when faced with an upgrade.

Having to use the old software because krb5 telnet broke something in its
coding is a problem for the future when the old software stops going. The new
krb5 telnet affects front end apps that use telnet as a transport.


4. How would the customer like to achieve this? (List the functional
requirements here)

Include a functionality to read /etc/issue and /etc/issue.net.


5. For each functional requirement listed in question 4, specify how Red Hat
and the customer can test to confirm the requirement is successfully
implemented.

Use krb5 telnet and see /etc/issue and/or /etc/issue.net


6. Is there already an existing RFE upstream or in Red Hat bugzilla?

No


7. How quickly does this need resolved? (desired target release)

RHEL5.7


8. Does this request meet the RHEL Inclusion criteria (please review)

Yes. It is a minor RFE. 

RHEL5 is still in Production 1 phase so software enhancement should be
feasible. Also this request was originally raised 8 months ago.

 
9. List the affected packages

krb5-workstation


10. Would the customer be able to assist in testing this functionality if
implemented?

Yes