cvs: peardoc /peardoc2/en/pecl radius.xml

From: Date: Thu, 23 Jan 2003 21:04:48 +0000
Subject: cvs: peardoc /peardoc2/en/pecl radius.xml
Groups: php.pear.doc 
Request: Send a blank email to pear-doc+get-307@lists.php.net to get a copy of this message
mbretter Thu Jan 23 16:04:48 2003 EDT Modified files: /peardoc/peardoc2/en/pecl radius.xml Log: added 2 new functions Index: peardoc/peardoc2/en/pecl/radius.xml diff -u peardoc/peardoc2/en/pecl/radius.xml:1.4 peardoc/peardoc2/en/pecl/radius.xml:1.5 --- peardoc/peardoc2/en/pecl/radius.xml:1.4 Thu Jan 2 19:32:31 2003 +++ peardoc/peardoc2/en/pecl/radius.xml Thu Jan 23 16:04:48 2003 @@ -1,5 +1,5 @@ <?xml version="1.0" encoding="iso-8859-1"?> -<!-- $Revision: 1.4 $ --> +<!-- $Revision: 1.5 $ --> <reference id="pecl.radius"> <title>Radius</title> <titleabbrev>radius</titleabbrev> @@ -74,7 +74,8 @@ authenticate with MSoft Servers you have to use MS-CHAPv1 or MS-CHAPv2, but its more complicated, because you need md4, sha1 and des to generate the right data. The enclosed examples demonstrate all authentication-methods, including MS-CHAPv1 and - MS-CHAPv2. To get the MS-CHAP to work you need the mcrypt and the mhash extension. + MS-CHAPv2. To get the MS-CHAP to work you need the mcrypt and the mhash extension, starting + with version 1.2 of the package, the mcrypt extension is no longer needed. </para> </sect2> </sect1> @@ -845,6 +846,53 @@ </para> <para> The shared secret is needed as salt for demangling mangled data like passwords and encryption-keys. + </para> + </refsect1> + </refentry> + + <refentry id="pecl.radius.radius_demangle"> + <refnamediv> + <refname>radius_demangle</refname> + <refpurpose>Demangles data</refpurpose> + </refnamediv> + <refsect1> + <title>Description</title> + <funcsynopsis> + <funcprototype> + <funcdef>string <function>radius_demangle</function></funcdef> + <paramdef>string <parameter>mangled</parameter></paramdef> + </funcprototype> + </funcsynopsis> + <para> + Returns: string, &false; on error. + </para> + <para> + Some data (Passwords, MS-CHAPv1 MPPE-Keys) is mangled for security reasons, and must be demangled + before you can use them. + </para> + </refsect1> + </refentry> + + <refentry id="pecl.radius.radius_demangle_mppe_key"> + <refnamediv> + <refname>radius_demangle_mppe_key</refname> + <refpurpose>Derives mppe-keys from mangled data</refpurpose> + </refnamediv> + <refsect1> + <title>Description</title> + <funcsynopsis> + <funcprototype> + <funcdef>string <function>radius_demangle_mppe_key</function></funcdef> + <paramdef>resource <parameter>radius_handle</parameter></paramdef> + <paramdef>string <parameter>mangled</parameter></paramdef> + </funcprototype> + </funcsynopsis> + <para> + Returns: string, &false; on error. + </para> + <para> + When using MPPE with MS-CHAPv2, the send- and recv-keys are mangled (see RFC2548), however this function is + useless, because I don't hink that there is and will be a PPTP-MPPE implementation in PHP. </para> </refsect1> </refentry>

« previous php.pear.doc (#307) next »