1Authen::SASL::Perl(3) User Contributed Perl DocumentationAuthen::SASL::Perl(3)
2
3
4
6 Authen::SASL::Perl -- Perl implementation of the SASL Authentication
7 framework
8
10 use Authen::SASL qw(Perl);
11
12 $sasl = Authen::SASL->new(
13 mechanism => 'CRAM-MD5 PLAIN ANONYMOUS',
14 callback => {
15 user => $user,
16 pass => \&fetch_password
17 }
18 );
19
21 Authen::SASL::Perl is the pure Perl implementation of SASL mechanisms
22 in the Authen::SASL framework.
23
24 At the time of this writing it provides the client part implementation
25 for the following SASL mechanisms:
26
27 ANONYMOUS
28 The Anonymous SASL Mechanism as defined in RFC 2245 resp. in IETF
29 Draft draft-ietf-sasl-anon-03.txt from February 2004 provides a
30 method to anonymously access internet services.
31
32 Since it does no authentication it does not need to send any confi‐
33 dential information such as passwords in plain text over the net‐
34 work.
35
36 CRAM-MD5
37 The CRAM-MD5 SASL Mechanism as defined in RFC2195 resp. in IETF
38 Draft draft-ietf-sasl-crammd5-02.txt from January 2004 offers a
39 simple challenge-response authentication mechanism.
40
41 Since it is a challenge-response authentication mechanism no pass‐
42 words are transferred in clear-text over the wire.
43
44 Due to the simplicity of the protocol CRAM-MD5 is susceptible to
45 replay and dictionary attacks, so DIGEST-MD5 should be used in pre‐
46 ferrence.
47
48 DIGEST-MD5
49 The DIGEST-MD5 SASL Mechanism as defined in RFC 2831 resp. in IETF
50 Draft draft-ietf-sasl-rfc2831bis-03.txt from February 2004 offers
51 the HTTP Digest Access Authentication as SASL mechanism.
52
53 Like CRAM-MD5 it is a challenge-response authentication method that
54 does not send plain text passwords over the network.
55
56 Compared to CRAM-MD5, DIGEST-MD5 prevents chosen plaintext attacks,
57 and permits the use of third party authentication servers, so that
58 it is recommended to use DIGEST-MD5 instead of CRAM-MD5 when possi‐
59 ble.
60
61 EXTERNAL
62 The EXTERNAL SASL mechanism as defined in RFC 2222 allows the use
63 of external authentication systems as SASL mechanisms.
64
65 LOGIN
66 The LOGIN SASL Mechanism as defined in IETF Draft draft-murchi‐
67 son-sasl-login-00.txt from August 2003 allows the combination of
68 username and clear-text password to be used in a SASL mechanism.
69
70 It does does not provide a security layer and sends the credentials
71 in clear over the wire. Thus this mechanism should not be used
72 without adequate security protection.
73
74 PLAIN
75 The Plain SASL Mechanism as defined in RFC 2595 resp. IETF Draft
76 draft-ietf-sasl-plain-04.txt from February 2004 is another SASL
77 mechanism that allows username and clear-text password combinations
78 in SASL environments.
79
80 Like LOGIN it sends the credentials in clear over the network and
81 should not be used without sufficient security protection.
82
84 Authen::SASL, Authen::SASL::Cyrus::ANONYMOUS,
85 Authen::SASL::Cyrus::CRAM_MD5, Authen::SASL::Cyrus::DIGEST_MD5,
86 Authen::SASL::Cyrus::EXTERNAL, Authen::SASL::Cyrus::LOGIN,
87 Authen::SASL::Cyrus::PLAIN
88
90 Peter Marschall <peter@adpm.de>
91
92 Please report any bugs, or post any suggestions, to the perl-ldap mail‐
93 ing list <perl-ldap@perl.org>
94
96 Copyright (c) 2004 Peter Marschall. All rights reserved. This document
97 is distributed, and may be redistributed, under the same terms as Perl
98 itself.
99
100
101
102perl v5.8.8 2006-03-25 Authen::SASL::Perl(3)