On Sep 12, 2005, at 15:23 PM, Hirmke Michael wrote:
still results in
No SASL mechanism found
at c:/Programme/Perl/site/lib/Authen/SASL.pm line 73
Do you have a $SIG{__DIE__} handler installed ??
If you don't, then ignore me :-)
ignored :)
No I haven't, but there is one in Authen::SASL -
Hi,
[...]
> > still results in
> >
> > No SASL mechanism found
> > at c:/Programme/Perl/site/lib/Authen/SASL.pm line 73
>
> Do you have a $SIG{__DIE__} handler installed ??
>
> If you don't, then ignore me :-)
ignored :)
No I haven't, but there is one in Authen::SASL - this can't cause
the pro
On 12/9/05 7:25, Graham Barr <[EMAIL PROTECTED]> wrote:
> On Sun, September 11, 2005 10:40 am, Chris Ridd wrote:
>> On 11/9/05 4:32, Peter Marschall <[EMAIL PROTECTED]> wrote:
>>
>>> The selection of the mech used for authentication does not happen in the
>>> client (i.e. Authen::SASL does not de
On Mon, September 12, 2005 1:28 pm, Hirmke Michael wrote:
>> The eval should have caught the die. However I would personally
>> have placed the assignment outside the eval
>>
>> $oSASL = eval { Authen::SASL->new(
>> mechanism => "GSSAPI",
>> ca
--On Monday, September 12, 2005 7:19 PM +0100 Simon Wilkinson
<[EMAIL PROTECTED]> wrote:
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 'wor
Hi,
[...]
thx for your answer, but:
>
> The eval should have caught the die. However I would personally
> have placed the assignment outside the eval
>
> $oSASL = eval { Authen::SASL->new(
> mechanism => "GSSAPI",
> callback => {
>
On Mon, September 12, 2005 1:19 pm, Simon Wilkinson wrote:
> 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
On Sun, September 11, 2005 10:40 am, Chris Ridd wrote:
> On 11/9/05 4:32, Peter Marschall <[EMAIL PROTECTED]> wrote:
>
>> The selection of the mech used for authentication does not happen in the
>> client (i.e. Authen::SASL does not decide)
>> The mach gets selected when the connection is made to t
On Mon, September 12, 2005 11:59 am, Hirmke Michael wrote:
>> You may use eval { ... } around the above piece of code to
>> catch the error.
>
> I already tried it - didn't help in any way.
>
>
> eval { $oSASL = Authen::SASL->new(
>mechanism => "GSSAPI",
>
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
Hi,
[...]
>
> Wow 150.000 !!!
> May I ask for the company/institution you create this installation ?
look at my email address :)
It is the German Labour Office (Bundesagentur fuer Arbeit).
[...]
> >
> > No SASL mechanism found
> > at /usr/lib/perl5/site_perl/5.8.1/Authen/SASL.pm line 73
[...]
Hi,
On Monday, 12. September 2005 11:09, Hirmke Michael wrote:
> > What do you mean exactly by "my installation" ?
>
> my scripts have to run on about 150.000 computers. Normally they should
> have the same software and same versions installed - but who knows 8-<
> So I'd like to check within the
In a process of deep contemplation, Prabu Uthirapathi carefully
constucted the following missive on 9/9/2005 9:40 AM:
I would like to use Net::LDAP module to authenticate web user against active
directory.
I have done the following steps.
a) Created the LDAP connection
b) Bind the LDAP using ad
Hi,
[...]
> > 1. Is there any way to find out in a Perl script, what SASL
> mechanisms
> >are supported in my installation?
>
> What do you mean exactly by "my installation" ?
my scripts have to run on about 150.000 computers. Normally they should
have the same software and same versions in
14 matches
Mail list logo
