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.
Bug 853074 - authconfig backup/restore does not work for --enableshadow and --disableshadow
Summary: authconfig backup/restore does not work for --enableshadow and --disableshadow
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: authconfig
Version: 7.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Tomas Mraz
QA Contact: David Spurek
URL:
Whiteboard:
Depends On: 852997
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-30 12:53 UTC by Patrik Kis
Modified: 2015-03-02 05:27 UTC (History)
2 users (show)

Fixed In Version: authconfig-6.2.4-2.el7
Doc Type: Bug Fix
Doc Text:
Clone Of: 852997
Environment:
Last Closed: 2014-06-13 12:05:04 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Patrik Kis 2012-08-30 12:53:32 UTC 
+++ This bug was initially created as a clone of Bug #852997 +++

Description of problem:
Authconfig backup/restore does not work for --enableshadow and --disableshadow.
Neither --restorelastbackup nor --savebackup/--restorebackup do their job.
Not all options were tested but --enablenis seems working.
The man page says nothing about exceptions in backup/restore.

Version-Release number of selected component (if applicable):
authconfig-6.1.12-10.el6.x86_64

How reproducible:
always

Steps to Reproduce:
1. Do a backup
# authconfig --savebackup testback
# sum /etc/shadow* /etc/passwd*
36542     2 /etc/shadow
61955     2 /etc/shadow-
23868     2 /etc/passwd
08119     3 /etc/passwd-

2. Change the shadow configuration
# authconfig --disableshadow --update
# sum /etc/shadow* /etc/passwd*
61955     2 /etc/shadow-
08119     3 /etc/passwd
23868     2 /etc/passwd-

3. Try to restore
# authconfig --restorelastbackup
# echo $?
0
# sum /etc/shadow* /etc/passwd*
61955     2 /etc/shadow-
08119     3 /etc/passwd
23868     2 /etc/passwd-
# 
# authconfig --restorebackup testback
# sum /etc/shadow* /etc/passwd*
61955     2 /etc/shadow-
08119     3 /etc/passwd
23868     2 /etc/passwd-

Actual results:
The original configuration is not restored.

Expected results:
All changes are restored.

Workaround:
# authconfig --enableshadow --update
# sum /etc/shadow* /etc/passwd*
36542     2 /etc/shadow
61955     2 /etc/shadow-
23868     2 /etc/passwd
08119     3 /etc/passwd-
Comment 1 Patrik Kis 2012-08-30 13:22:09 UTC 
The symptoms and the reproducer is the same as above, just the component version changed:
authconfig-6.2.3-1.el7.x86_64
Comment 4 Ludek Smid 2014-06-13 12:05:04 UTC 
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.
Note You need to log in before you can comment on or make changes to this bug.