[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

autostep and encrypted root password



If kickstarting a RHEL 5.y system, and the kickstart file contains
   autostep
   rootpw --iscrypted $1$.....
then the kickstart will stop and ask for the root password. If using a plain text root password, it autosteps through the root password screen as expected.

See https://bugzilla.redhat.com/show_bug.cgi?id=471122#c4 for a patch for RHEL 5.3 Beta.

Below is a similar patch for anaconda-11.4.1.56-1.

Jeff


--- kickstart.py.ORIG   2008-11-11 15:35:29.000000000 -0600
+++ kickstart.py        2008-11-11 15:39:42.000000000 -0600
@@ -1185,6 +1185,11 @@
         dispatch.skipStep("installtype")
         dispatch.skipStep("bootdisk")

+    # if the root password is already encrypted, we cannot fill in
+    # the password field on the accounts screen, so skip it
+    if flags.autostep and self.id.rootPassword["isCrypted"]:
+        dispatch.skipStep("accounts")
+
     dispatch.skipStep("bootdisk")
     dispatch.skipStep("betanag")
     dispatch.skipStep("regkey")
--- kickstart.py.ORIG	2008-11-11 14:13:35.000000000 -0600
+++ kickstart.py	2008-11-11 15:26:21.000000000 -0600
@@ -936,6 +936,11 @@
             dispatch.skipStep("installtype")
             dispatch.skipStep("bootdisk")
 
+        # if the root password is already encrypted, we cannot fill in
+        # the password field on the accounts screen, so skip it
+        if flags.autostep and self.id.rootPassword["isCrypted"]:
+            dispatch.skipStep("accounts")
+
         # because these steps depend on the monitor being probed
         # properly, and will stop you if you have an unprobed monitor,
         # we should skip them for autostep

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]