Diff of autodoc.git/onepage.xml (6fe21f270921eb60016a87d5885eeb709ae8e184 » 3d2f4c4006153c22ff75a970537ffd74602cdb9d)

autodoc.git/onepage.xml:1: <?xml version='1.0' encoding='utf-8'?> - <manual time-stamp='2019-11-03' version='Pike v8.1.13'> + <manual time-stamp='2019-11-05' version='Pike v8.1.13'> <dir name='./onepage'> <file name='./onepage/manual.html'> <chapter number='1' title='Control Structures'> In this chapter all the control structures in Pike will be explained. Control structures are used to control the flow of the program execution. Note that functions that make the program pause and simple function calls are not qualified as control structures. <section number='1' title='Conditions'>
autodoc.git/onepage.xml:26650: If an unsupported scheme is specified an error will be thrown. Supported schemes are: Crypt(3C)-style: <string><group><value>UNDEFINED</value><value>"crypt"</value><value>"{crypt}"</value><text>Use the strongest crypt(3C)-style hash that is supported. </text></group><group><value>"6"</value><value>"$6$"</value><text><ref resolved='predef::Nettle.Hash.crypt_hash'>SHA512.crypt_hash()</ref> with 96 bits of salt and a default of <expr>5000</expr> rounds. </text></group><group><value>"5"</value><value>"$5$"</value><text><ref resolved='predef::Nettle.Hash.crypt_hash'>SHA256.crypt_hash()</ref> with 96 bits of salt and a default of <expr>5000</expr> rounds. </text></group><group><value>"3"</value><value>"NT"</value><text>The NTLM MD4 hash. </text></group><group><value>"1"</value><value>"$1$"</value><text><ref resolved='predef::Crypto.MD5.crypt_hash'>MD5.crypt_hash()</ref> with 48 bits of salt and <expr>1000</expr> rounds. + </text></group><group><value>"P"</value><value>"$P$"</value><value>"H"</value><value>"$H$"</value><text><ref resolved='predef::__builtin.Nettle.Hash.crypt_php'>MD5.crypt_php()</ref> with 48 bits of salt and a default of + <expr>1<<19</expr> rounds. The specified number of rounds will + be rounded up to the closest power of <expr>2</expr>. + </text></group><group><value>"U$P$"</value><text>Same as <expr>"$P$"</expr>, the supplied <ref resolved='predef::Crypto.Password.hash.password'>password</ref> is assumed to + have already been passed through <ref resolved='predef::Nettle.Hash.hash'>MD5.hash()</ref> once. Typically + used to upgrade unsalted <ref resolved='predef::Crypto.MD5'>MD5</ref>-password databases. + </text></group><group><value>"Q"</value><value>"$Q$"</value><text>Same as <expr>"$P$"</expr>, but with <ref resolved='predef::__builtin.Nettle.Hash.crypt_php'>SHA1.crypt_php()</ref>. + </text></group><group><value>"S"</value><value>"$S$"</value><text>Same as <expr>"$S$"</expr>, but with <ref resolved='predef::__builtin.Nettle.Hash.crypt_php'>SHA512.crypt_php()</ref>. + </text></group><group><value>"pbkdf2"</value><value>"$pbkdf2$"</value><text><ref resolved='predef::__builtin.Nettle.Hash.pbkdf2'>SHA1.pbkdf2()</ref>. + </text></group><group><value>"pbkdf2-sha256"</value><value>"$pbkdf2-sha256$"</value><text><ref resolved='predef::__builtin.Nettle.Hash.pbkdf2'>SHA256.pbkdf2()</ref>. + </text></group><group><value>"pbkdf2-sha512"</value><value>"$pbkdf2-sha512$"</value><text><ref resolved='predef::__builtin.Nettle.Hash.pbkdf2'>SHA512.pbkdf2()</ref>. </text></group><group><value>""</value><text><ref resolved='predef::crypt'>predef::crypt()</ref> with 12 bits of salt. </text></group></string>LDAP (<rfc>2307</rfc>)-style. Don't use these if you can avoid it, since they are suspectible to attacks. In particular avoid the unsalted variants at all costs: <string><group><value>"ssha"</value><value>"{ssha}"</value><text><ref resolved='predef::Nettle.Hash.hash'>SHA1.hash()</ref> with 96 bits of salt appended to the password. </text></group><group><value>"smd5"</value><value>"{smd5}"</value><text><ref resolved='predef::Nettle.Hash.hash'>MD5.hash()</ref> with 96 bits of salt appended to the password. </text></group><group><value>"sha"</value><value>"{sha}"</value><text><ref resolved='predef::Nettle.Hash.hash'>SHA1.hash()</ref> without any salt. </text></group><group><value>"md5"</value><value>"{md5}"</value><text><ref resolved='predef::Nettle.Hash.hash'>MD5.hash()</ref> without any salt. </text></group></string> </text></group><group><param name='rounds'/><text>The number of rounds to use in parameterized schemes. If not
autodoc.git/onepage.xml:26736: <expr>1000</expr> and <expr>999999999</expr> (inclusive). Source: Unix crypt using SHA-256 and SHA-512 <url>http://www.akkadia.org/drepper/SHA-crypt.txt</url> </text></group><group><value>"$3$$XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"</value><text>This is interpreted as the NT LANMANAGER (NTLM) password hash. It is a hex representation of MD4 of the password. </text></group><group><value>"$1$SSSSSSSS$XXXXXXXXXXXXXXXXXXXXXX"</value><text>The string is interpreted according to the GNU libc2 extension of <expr>crypt(3C)</expr> where <expr>SSSSSSSS</expr> is up to 8 chars of salt and the <expr>XXX</expr> string is an <ref resolved='predef::Crypto.MD5'>MD5</ref>-based hash created from the password and the salt. Source: GNU libc <url>http://www.gnu.org/software/libtool/manual/libc/crypt.html</url>. + </text></group><group><value>"$P$RSSSSSSSSXXXXXXXXXXXXXXXXXXXXXX"</value><text>The string is interpreted as a PHPass' Portable Hash password hash, + where <expr>R</expr> is an encoding of the 2-logarithm of the number of + rounds, <expr>SSSSSSSS</expr> is a salt of 8 characters, and + <expr>XXX</expr> is similarily the <ref>MIME.encode_crypt64</ref> of running + <ref resolved='predef::Nettle.Hash.hash'>MD5.hash()</ref> repeatedly on the password and the salt. + </text></group><group><value>"$H$RSSSSSSSS.XXXXXXXXXXXXXXXXXXXXXX"</value><text>Same as expr{"$P$" above. Used by phpBB3. + </text></group><group><value>"U$P$RSSSSSSSSXXXXXXXXXXXXXXXXXXXXXX"</value><text>This is handled as a Drupal upgraded PHPass Portable Hash password. + The password is run once through <ref resolved='predef::Nettle.Hash.hash'>MD5.hash()</ref>, and then passed + along to the <expr>"$P$"</expr>-handler above. + </text></group><group><value>"$Q$RSSSSSSSSXXXXXXXXXXXXXXXXXXXXXX"</value><text>The string is interpreted as a PHPass' Portable Hash password hash, + where the base hashing alorithm has been switched to <ref resolved='predef::Crypto.SHA1'>SHA1</ref>. + This method is apparently used by some versions of Escher CMS. + </text></group><group><value>"$S$RSSSSSSSSXXXXXXXXXXXXXXXXXXXXXX"</value><text>The string is interpreted as a PHPass' Portable Hash password hash, + where the base hashing alorithm has been switched to <ref resolved='predef::Crypto.SHA256'>SHA256</ref>. + This method is apparently used by some versions of Drupal. </text></group><group><value>"XXXXXXXXXXXXX"</value><text>The <expr>XXX</expr> string (which doesn't begin with <expr>"{"</expr>) is taken to be a password hashed using the classic unix <expr>crypt(3C)</expr> function. If the string contains only chars from the set <expr>[a-zA-Z0-9./]</expr> it uses DES and the first two characters as salt, but other alternatives might be possible depending on the <expr>crypt(3C)</expr> implementation in the operating system. </text></group><group><value>""</value><text>The empty password hash matches all passwords. </text></group></string> </text><group><returns/><text>Returns <expr>1</expr> on success, and <expr>0</expr> (zero) otherwise.

autodoc.git / onepage.xml