installer authentication

I would like to write a script for use in a school lab that will open an installer and automatically enter in the administrator name/password so that the “authentication” window does not show up.
It would also be helpful to have a script that would enter in the name/password to “unlock” the system preferences.
Paul

: I would like to write a script for use in a school lab that will open an
: installer and automatically enter in the administrator name/password so
: that the “authentication” window does not show up.
Good luck. I have yet to find an installer to be scriptable. (I had wanted to do just that in the past myself.) Your best bet for something like this is to use Apple’s Software Restore application to build a snapshot disk image.
: It would also be helpful to have a script that would enter in the
: name/password to “unlock” the system preferences.
IS this for OS X? You may be able to us the System OSAX at MacScripter’s scripting addition database to do something like this. I think it would have to be done via the terminal… don’t think System Preferences is scriptable.

: Good luck. I have yet to find an installer to be scriptable. (I had wanted to
: do just that in the past myself.) Your best bet for something like this is
: to use Apple’s Software Restore application to build a snapshot disk
: image.
: IS this for OS X? You may be able to us the System OSAX at MacScripter’s
: scripting addition database to do something like this. I think it would
: have to be done via the terminal… don’t think System Preferences is
: scriptable.
This is for OS X. There are actually scriptable installers for OS X. For example, the Windows Media Player Installer can be scripted to do things like “DoAutoInstall” and “Uninstall.” The problem is that when you script the application to open, you get that name and password field that has to be filled in manually. Now when you log at start-up as root, it doesn’t ask for a password. I tried logging on as root in the terminal, and opening the Installer from there, but it still asked for a password. I can’t make a script to log out and back on as root because there doesn’t seem to be a way to script the login screen.

: if “the perception” is equal to “Run-Only is a safe place
: to store passwords” then display dialog “No it isn’t!”
: else display dialog “OK, sorry I misunderstood.” end if
: Run-Only won’t protect the script/password from someone who is determined to
: get the info. I have a script that can suck it out in 2 seconds and then
: place it in a text document, email it or post it to a web site for all to
Not REALLY safe, but at least safer. :slight_smile:

: Not REALLY safe, but at least safer. :slight_smile:
Yup, in a casual setting, it would keep honest people honest. :slight_smile:
Rob

: This is for OS X. There are actually scriptable installers for OS X. For
: example, the Windows Media Player Installer can be scripted to do things
: like “DoAutoInstall” and “Uninstall.” The problem is
: that when you script the application to open, you get that name and
: password field that has to be filled in manually. Now when you log at
: start-up as root, it doesn’t ask for a password. I tried logging on as
: root in the terminal, and opening the Installer from there, but it still
: asked for a password. I can’t make a script to log out and back on as root
: because there doesn’t seem to be a way to script the login screen.
Is Pseudo (at VersionTracker.com) scriptable?It allows you to launch an app as root. You could so see if the following works:
sudo open ‘MyDisk:SomeFolder:InstallerName’
Of course, you’d need to echo in the password from your script, too. That means the password would be in your script, so you’d wan tto keep a regular copy on your own machine somewhere, but save the one that goes on the public machine as Run-Only.

: Is Pseudo (at VersionTracker.com) scriptable?It allows you to launch an app
: as root. You could so see if the following works: sudo open
: ‘MyDisk:SomeFolder:InstallerName’
: Of course, you’d need to echo in the password from your script, too. That
: means the password would be in your script, so you’d wan tto keep a
: regular copy on your own machine somewhere, but save the one that goes on
: the public machine as Run-Only.
Based on my experience with pre-OS X scripts…
if “the perception” is equal to “Run-Only is a safe place to store passwords” then
display dialog “No it isn’t!”
else
display dialog “OK, sorry I misunderstood.”
end if
Run-Only won’t protect the script/password from someone who is determined
to get the info. I have a script that can suck it out in 2 seconds and then place
it in a text document, email it or post it to a web site for all to see.
Rob J (who doesn’t have OS X yet)