Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
I don't see that kadmin makes any guarantees about its exit status. Its implementation appears to discard any errors encountered while processing commands, so we're potentially talking about much more than just these two commands and the -e flag.
(In reply to Nalin Dahyabhai from comment #1)
> I don't see that kadmin makes any guarantees about its exit status. Its
> implementation appears to discard any errors encountered while processing
> commands, so we're potentially talking about much more than just these two
> commands and the -e flag.
Just for the log: One idea I had was to implement kadminsh, a kadmin version based on AT&T AST's libshell (which provides a POSIX shell (ksh93) as shared library) and implement the kadmin subcommands as shell builtins... that would allow getting the proper return status for each subcommand and even add control over the code flow when multiple kadmin subcommands are used.
Problem is getting time allocated for this project... implementing it is easy but getting the neccesary infrastructure into Fedora is a man-week of work.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHSA-2016-2591.html
Description of problem: kadmin.local -q with wrong value in -e option doesn't return nonzero return code [test]kadmin.local -r EXAMPLE.COM -q "addprinc -randkey -e aes256-cts,aes128-cts kvnoprinc" Authenticating as principal root/admin with password. add_principal: Invalid argument while parsing keysalts aes256-cts,aes128-cts usage: add_principal [options] principal options are: [-x db_princ_args]* [-expire expdate] [-pwexpire pwexpdate] [-maxlife maxtixlife] [-kvno kvno] [-policy policy] [-clearpolicy] [-randkey] [-pw password] [-maxrenewlife maxrenewlife] [-e keysaltlist] [{+|-}attribute] attributes are: allow_postdated allow_forwardable allow_tgs_req allow_renewable allow_proxiable allow_dup_skey allow_tix requires_preauth requires_hwauth needchange allow_svr password_changing_service ok_as_delegate ok_to_auth_as_delegate no_auth_data_required where, [-x db_princ_args]* - any number of database specific arguments. Look at each database documentation for supported arguments [test]echo $? 0 Version-Release number of selected component (if applicable): krb5-server-1.11.3-49.el7 How reproducible: always Steps to Reproduce: 1.kadmin.local -r EXAMPLE.COM -q "addprinc -randkey -e aes256-cts,aes128-cts kvnoprinc" 2.echo $? 3. Actual results: 0 Expected results: nonzero Additional info: cpw has incorrect behavior as well kadmin.local -r EXAMPLE.COM -q "cpw -randkey -keepold -e aes256-cts,aes128-cts kvnoprinc" Authenticating as principal root/admin with password. change_password: Invalid argument while parsing keysalts aes256