featurelockdown Adobe Acrobat XI Pro plist (adobe customization wizard)

[tcandela]

creating Adobe acrobat XI pro package for distribution via casper policy
i want to combine these 2 feature lockdowns into 1, how do i do it. Not sure on the correct beginning and endings of where to put the <key></key> <dict><dict> in order to combine.

I want to control application updates with update pkgs. provided by adobe.

here is the website for the 2 feature lockdowns: (lockdown updater, and javascript api alert)
http://www.adobe.com/devnet-docs/acrobatetk/tools/MacWiz/lockdown.html

I want to combine both into the 1 plist

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>11</key> <dict> <key>FeatureLockdown</key> <dict> <key>bUpdater</key> <false/> </dict>
</dict>
</dict>
</plist>

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict> <key>11</key> <dict> <key>FeatureLockdown</key> <dict> <key>cJavaScriptPerms</key> <dict> <key>tBlackList</key> <string>App.alert</string> </dict> </dict> </dict>
</dict>
</plist>

[mm2270 · Accepted solution]

This is not tested, so test, test and test some more, but I believe it should look like the following-

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
  <dict>
    <key>11</key>
    <dict>
      <key>FeatureLockdown</key>
      <dict>
        <key>bUpdater</key>
        <false/>
        <key>cJavaScriptPerms</key>
        <dict>
          <key>tBlackList</key>
          <string>App.alert</string>
        </dict>
      </dict>
    </dict>
  </dict>
</plist>

So here's an interesting tip that can help you when working with xml files. You can check if an xml file is properly formatted with xmllint. Here's how you would check a file once saved to disk:

xmllint /path/to/settings.xml

If you get an error that looks something like:

/path/to/settings.xml:10: parser error : Opening and ending tag mismatch: dict line 4 and plist
</plist>
        ^
/path/to/settings.xml:10: parser error : Premature end of data in tag plist line 3
</plist>
        ^

its basically malformed, and it tells you more or less where the problem lies. You will need to make changes until the xmllint command just returns the xml file itself as its output and no parser errors.
Also, you can use xmllint to see the xml file with all the pretty indenting, even if the file itself is one long string of run-on tags, by doing:

xmllint --format /path/to/settings.xml

You get output similar to what I posted above.

Hope that helps.

[tcandela]

from CL I ended up using plutil ./path to plist and it kicked back that the plist is OK.

adobe customization time, then test time