Permalink
Browse files

Rename as Authen::SASL::XS

  • Loading branch information...
1 parent c1a4bb1 commit 3db4d4b3c238cea1cf3f12eb7d4f18bf11531fd8 @gbarr committed Jan 16, 2009
Showing with 100 additions and 85 deletions.
  1. +15 −0 .gitignore
  2. +4 −4 MANIFEST
  3. +7 −7 Makefile.PL
  4. +4 −4 README
  5. +7 −7 Cyrus.pm → XS.pm
  6. +12 −12 Cyrus.pod → XS.pod
  7. +44 −44 Cyrus.xs → XS.xs
  8. +1 −1 lib/Authen/SASL/{Cyrus → XS}/Security.pm
  9. +2 −2 t/gssapiskel.pl
  10. +3 −3 t/plain.t
  11. +1 −1 typemap
View
@@ -0,0 +1,15 @@
+blib*
+Makefile
+Makefile.old
+Build
+_build*
+pm_to_blib*
+*.tar.gz
+Authen-SASL-XS*
+cover_db
+*~
+*.bak
+XS.bs
+XS.c
+XS.o
+
View
@@ -1,11 +1,11 @@
-Cyrus.pm
-Cyrus.xs
-Cyrus.pod
+XS.pm
+XS.xs
+XS.pod
MANIFEST
CHANGES
Makefile.PL
typemap
-lib/Authen/SASL/Cyrus/Security.pm
+lib/Authen/SASL/XS/Security.pm
t/plain.t
t/common.pl
t/gssapiskel.pl
View
@@ -4,8 +4,8 @@ use ExtUtils::MakeMaker;
# See lib/ExtUtils/MakeMaker.pm for details of how to influence
# the contents of the Makefile that is written.
WriteMakefile(
- 'NAME' => 'Authen::SASL::Cyrus',
- 'VERSION_FROM' => 'Cyrus.pm',
+ 'NAME' => 'Authen::SASL::XS',
+ 'VERSION_FROM' => 'XS.pm',
'PREREQ_PM' => {
Test::Simple => 0,
Test::More => 0,
@@ -17,11 +17,11 @@ package MY;
sub manifypods
{
return <<'POD';
-manifypods: Cyrus.pod
+manifypods: XS.pod
-Cyrus.pod: Cyrus.xs
- @echo "!!! Developers: Do not edit the Cyrus.pod, edit the Cyrus.xs instead. !!!"
- @echo "Make will overwrite Cyrus.pod."
- podselect Cyrus.xs > Cyrus.pod
+XS.pod: XS.xs
+ @echo "!!! Developers: Do not edit the XS.pod, edit the XS.xs instead. !!!"
+ @echo "Make will overwrite XS.pod."
+ podselect XS.xs > XS.pod
POD
}
View
8 README
@@ -1,6 +1,6 @@
-Authen::SASL::Cyrus - XS code to glue Perl SASL to Cyrus SASL
+Authen::SASL::XS - XS code to glue Perl SASL to Cyrus SASL
-1. Build Authen::SASL::Cyrus
+1. Build Authen::SASL::XS
First of all you need Authen::SASL installed at least in version 2.06 (with
server patch or higher).
@@ -44,10 +44,10 @@ If you want to test gssapi functionality, copy the gssapiskel.pl to gssapi.t
and edit the file correctly. Don't forget the create keytabfiles. Then
rerun make test and see what happens.
-2. Use Authen::SASL::Cyrus with GSSAPI for LDAP
+2. Use Authen::SASL::XS with GSSAPI for LDAP
If you are able to use the ldap* tools with GSSAPI and now you want to use Perl
-for this LDAP work, then you need Authen::SASL::Cyrus 0.11 or later. Please try
+for this LDAP work, then you need Authen::SASL::XS 1.00 or later. Please try
this script before reporting any bugs or problems:
#!/usr/bin/perl -w
View
@@ -1,13 +1,13 @@
-package Authen::SASL::Cyrus;
+package Authen::SASL::XS;
require DynaLoader;
-require Authen::SASL::Cyrus::Security;
+require Authen::SASL::XS::Security;
require Exporter;
-@ISA = qw(DynaLoader);# Exporter);
+@ISA = qw(DynaLoader);
-$VERSION = "0.13-server";
+$VERSION = "1.00";
-bootstrap Authen::SASL::Cyrus $VERSION;
+bootstrap Authen::SASL::XS $VERSION;
#
# Take a client filehandle and tie it to the Security subclass to
@@ -16,7 +16,7 @@ bootstrap Authen::SASL::Cyrus $VERSION;
sub tiesocket {
my($sasl, $fh) = @_;
- new Authen::SASL::Cyrus::Security($fh, $sasl);
+ new Authen::SASL::XS::Security($fh, $sasl);
}
@@ -26,7 +26,7 @@ sub tiesocket {
sub securesocket {
my ($sasl, $fh) = @_;
my $glob = \do { local *GLOB; };
- tie(*$glob, "Authen::SASL::Cyrus::Security", $fh, $sasl);
+ tie(*$glob, "Authen::SASL::XS::Security", $fh, $sasl);
$glob;
}
View
24 Cyrus.pod → XS.pod 100755 → 100644
@@ -1,6 +1,6 @@
=head1 NAME
-Authen::SASL::Cyrus - XS code to glue Perl SASL to Cyrus SASL
+Authen::SASL::XS - XS code to glue Perl SASL to Cyrus SASL
=head1 SYNOPSIS
@@ -18,7 +18,7 @@ Authen::SASL::Cyrus - XS code to glue Perl SASL to Cyrus SASL
=head1 DESCRIPTION
SASL is a generic mechanism for authentication used by several
-network protocols. B<Authen::SASL::Cyrus> provides an implementation
+network protocols. B<Authen::SASL::XS> provides an implementation
framework that all protocols should be able to share.
The XS framework makes calls into the existing libsasl.so resp. libsasl2
@@ -48,10 +48,10 @@ The Cyrus-SASL library uses callbacks when the application
needs some information. Common reasons are getting
usernames and passwords.
-Authen::SASL::Cyrus allows Cyrus-SASL to use perl-variables and perl-subs
+Authen::SASL::XS allows Cyrus-SASL to use perl-variables and perl-subs
as callback-targets.
-Currently Authen::SASL::Cyrus supports the following Callback types:
+Currently Authen::SASL::XS supports the following Callback types:
(for a more detailed description on what the callback type is used for
see the respective man pages)
@@ -131,7 +131,7 @@ C<Type of principal> is "AUTHID" for Authentication ID or "AUTHZID"
for Authorisation ID.
B<Remark>: This callback is ideal to get the username of the user using your service.
-If C<Authen::SASL::Cyrus> is linked to Cyrus SASL v1, which doesn't have a canonuser callback,
+If C<Authen::SASL::XS> is linked to Cyrus SASL v1, which doesn't have a canonuser callback,
it will simulate this callback by using the authorize callback internally. Don't worry, the
authorize callback is available anyway.
@@ -157,7 +157,7 @@ Out: true or false
=head2 Ways to pass a callback
-Authen::SASL::Cyrus supports three different ways to pass a callback
+Authen::SASL::XS supports three different ways to pass a callback
=over 4
@@ -206,15 +206,15 @@ sub canon
return $user;
}
-=head1 Authen::SASL::Cyrus METHODS
+=head1 Authen::SASL::XS METHODS
=over 4
=item server_new ( SERVICE , HOST = "" , IPLOCALPORT , IPREMOTEPORT )
Constructor for creating server-side sasl contexts.
-Creates and returns a new connection object blessed into Authen::SASL::Cyrus.
+Creates and returns a new connection object blessed into Authen::SASL::XS.
It is on that returned reference that the following methods are available.
The SERVICE is the name of the service being implemented, which may be used
by the underlying mechanism. An example service therefore is "ldap".
@@ -225,7 +225,7 @@ by the underlying mechanism. An example service therefore is "ldap".
Constructor for creating server-side sasl contexts.
-Creates and returns a new connection object blessed into Authen::SASL::Cyrus.
+Creates and returns a new connection object blessed into Authen::SASL::XS.
It is on that returned reference that the following methods are available.
The SERVICE is the name of the service being implemented, which may be used
by the underlying mechanism. An example service is "ldap". The HOST is the
@@ -345,7 +345,7 @@ It depends on the used mechanism how secure the encryption will be.
C<error> returns an array with all known error messages.
Basicly the sasl_errstring function is called with the current error_code.
When using Cyrus-SASL 2.x library also the string returned by sasl_errdetail
-is given back. Additionally the special Authen::SASL::Cyrus advise is
+is given back. Additionally the special Authen::SASL::XS advise is
returned if set.
After calling the C<error> function, the error code and the special advice
are thrown away.
@@ -392,7 +392,7 @@ That's why we all using perl, eh?
}
);
- # Creating the Authen::SASL::Cyrus object
+ # Creating the Authen::SASL::XS object
my $conn = $sasl->server_new("service","","ip;port local","ip;port remote");
# Clients first string (maybe "", depends on mechanism)
@@ -425,7 +425,7 @@ That's why we all using perl, eh?
}
);
- # Creating the Authen::SASL::Cyrus object
+ # Creating the Authen::SASL::XS object
my $conn = $sasl->client_new("service", "hostname.domain.tld");
# Client begins always
Oops, something went wrong.

0 comments on commit 3db4d4b

Please sign in to comment.