Graham Barr wrote:
So you need to hold a mapping table for the OIDs <-> Type, and a way to
define how the inner thing is embedded.
The code todo that is already in C::ASN1, you do it like
$asn->registeroid('2.5.29.17' => $asn->find('SubjectAltName'));
Take a look in t/14any.t in the distribu
Zhang Liquan wrote:
In Net::LDAP::Bind::decode, use $sasl->tiesocket replace $sasl->securesocket, then the connection
will not be closed when BIND completed.
But after BIND success, the Net::LDAP module will complain the socket handle ($ldap->socket)
not a GLOB reference when it try to w
Graham Barr wrote:
> IIRC there are two Authen::SASL::Cyrus implmentations. Someone did thier
> own becuase they had little luck with the one on CPAN.
>
> Does anyone on the list remember this?
There are three different implementations.
I produced one in the dim and distant past, which was never
Peter Marschall wrote:
> GSSAPI is currently only supported by Authen::SASL::Cyrus.
I've been thinking about this for a while now. Authen::SASL::Cyrus is a
source of much grief for many - even the 'working' version causes us the
occasional problem. Would a patch which implemented GSSAPI for
Authe
/Perl/GSSAPI.pm (revision 0)
@@ -0,0 +1,87 @@
+# Copyright (c) 2006 Simon Wilkinson
+# All rights reserved. This program is free software; you can redistribute
+# it and/or modify it under the same terms as Perl itself.
+
+package Authen::SASL::Perl::GSSAPI;
+
+use strict;
+
+use vars qw($VERSION @IS
Graham Barr wrote:
> However, I would also like to see some tests added for recent additions.
On the GSSAPI SASL mechanism front, I've been thinking about how to
write a test, and I'm not entirely convinced that it would be possible,
without stubbing out all of the GSSAPI calls. To really test th
Achim,
I'm having some trouble understanding the requirements for these
changes. Some of this may be because of changes you've made to the
GSSAPI.pm perl module, since Phillip Guenther released version 0.13 in 2005.
Also, there seem to be a lot of purely formatting changes, which make it
harder t
Graham Barr wrote:
> On Feb 22, 2006, at 4:19 AM, Simon Wilkinson wrote:
>> I've got a security layers patch for Authen::SASL which should be done
>> by the end of the week, if you could wait till then?
>
> Are these changes ready to commit ?
No - I hit upon some probl
I think I may be using the wrong callback with Authen::SASL::GSSAPI, and
I wanted some comments.
With GSSAPI, the authentication identity is determined by the contents
of the current users credential cache. However, the authorization
identity can be specified as part of the SASL handshake.
I'm cu
On 21 Sep 2006, at 08:25, Alexander Foken wrote:
Are you sure you wrote to the right mailing list? Perl-LDAP is for
LDAP problems, not for SASL or SMTP.
No, as far as I'm aware, this list is the correct place for queries
about Authen::SASL - its certainly where I've posted all
of the revi
On 19 Jun 2008, at 19:17, Dominic Hargreaves wrote:
I'm using a web single signon system (umich's cosign) that can
retrieve
a kerberos ticket for a user. As far as I can tell there isn't a
way to
specify a credential cache with Authen::SASL::Cyrus (or is there?).
If you're using cosign,
On 13 Apr 2009, at 17:23, Dale Moore wrote:
I recommend that if we are going to use Net::LDAP get the peerhost,
and use it as part of the service name, that we modify Net::LDAP to
do the reverse DNS and not expect GSSAPI to do it. Or we change our
approach in dealing with hosts with round-robin
On 1 Jul 2009, at 19:03, Quanah Gibson-Mount wrote:
--On Wednesday, July 01, 2009 7:58 PM +0200 Dieter Kluenter > wrote:
Hi,
is there anybody on this list who could prepare a paper on
'triggering
events on RFC 4533 enabled directories', based on
Net::LDAP::Intermediate::SyncInfo ? Or som
13 matches
Mail list logo
