Make WordPress Core

Changeset 18645


Ignore:
Timestamp:
09/06/2011 10:22:36 PM (14 years ago)
Author:
nacin
Message:

Update parameters.xml, removing secret keys. These are now generated via WebPI without user intervention. props Chris Sfanos.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • branches/iis/parameters.xml

    r16585 r18645  
    225225<!-- WordPress specific parameters -->
    226226
    227 <!-- There were a number of parameters which relied on the
    228     TextFilePosition parameterEntry type to define the section of a
    229     file to be replaced.  The TextFilePosition type is considered
    230     fragile, as any change to the target file that occurs before the
    231     text to be replaced will invalidate the position.
    232 
    233     We are now using TextFile, which relies on a Regular Expression
    234     (RegEx) to identify the text to change.  There are some
    235     parameters, where the text to be replaced is not unique enough
    236     to target on it's own.  In those cases, we used  RegExes with
    237     Lookbehind constructs to uniquely identify the text segment
    238     to be replaced.
    239 -->
    240 
    241 <parameter
    242     name="Key1"
    243     friendlyName="Unique Key for Passwords"
    244     description="Unique phrase used to strengthen your password."
    245     defaultValue="put your unique phrase here"
    246     tags="NoStore"
    247     >
    248     <parameterValidation
    249     type="RegularExpression"
    250     validationString="^[^&#039;\\]+$"
    251     />
    252     <parameterEntry
    253     type="TextFile"
    254     match="(?&lt;=&#039;AUTH_KEY&#039;,[ ]+&#039;)put your unique phrase here"
    255     scope="wordpress\\wp-config.php"
    256     />
    257 </parameter>
    258 
    259 <parameter
    260     name="Key2"
    261     friendlyName="Unique Key for Secure Passwords"
    262     description="Different unique phrase used to strengthen SSL passwords."
    263     defaultValue="put your unique phrase here"
    264     tags="NoStore"
    265     >
    266     <parameterValidation
    267     type="RegularExpression"
    268     validationString="^[^&#039;\\]+$"
    269     />
    270     <parameterEntry
    271     type="TextFile"
    272     scope="wordpress\\wp-config.php"
    273     match="(?&lt;=SECURE_AUTH_KEY&#039;,[ ]+&#039;)put your unique phrase here"
    274     />
    275 </parameter>
    276 
    277 <parameter
    278     name="Key3"
    279     friendlyName="Unique Key for Authentication"
    280     description="Different unique phrase used to strengthen authentication."
    281     defaultValue="put your unique phrase here"
    282     tags="NoStore"
    283     >
    284     <parameterValidation
    285     type="RegularExpression"
    286     validationString="^[^&#039;\\]+$"
    287     />
    288     <parameterEntry
    289     type="TextFile"
    290     scope="wordpress\\wp-config.php"
    291     match="(?&lt;=LOGGED_IN_KEY&#039;,[ ]+&#039;)put your unique phrase here"
    292     />
    293 </parameter>
    294 
    295 <parameter
    296     name="Key4"
    297     friendlyName="Second Unique Key for Authentication"
    298     description="Another unique phrase used to strengthen authentication."
    299     defaultValue="put your unique phrase here"
    300     tags="NoStore"
    301     >
    302     <parameterValidation
    303     type="RegularExpression"
    304     validationString="^[^&#039;\\]+$"
    305     />
    306     <parameterEntry
    307     type="TextFile"
    308     scope="wordpress\\wp-config.php"
    309     match="(?&lt;=NONCE_KEY&#039;,[ ]+&#039;)put your unique phrase here"
    310     />
    311 </parameter>
    312 
    313227<!-- Set the correct path for the ACL based on the AppPath selected
    314228    by the user.
Note: See TracChangeset for help on using the changeset viewer.