Nope - I got distracted by the start of term. At the moment we're
just telling users not to use such characters in their passwords which
is a bit lame :-<. I did have a go at doing the necessary
transformation in the pam module we're using but it didn't seem to
help.
Paul
On Wed, 26 Sep 2001, Mayers, Philip J wrote:
> Did you ever get this to work - I've just run into the same problem myself,
> and am trying to use Python2's unicode conversion stuff to do the
> transformation...
>
> >>> import codecs
> >>> a = 'test?'
>
> That's "test<ukpoundsign>"
>
> >>> a
> 'test\xa3'
>
> Above is what comes over the network (HTTP basic auth, base64 encoded).
>
> >>> codecs.latin_1_decode(a)
> (u'test\xa3', 5)
> >>> codecs.utf_8_encode(u'test\xa3')
> ('test\xc2\xa3', 5)
>
> However, passing the 'text\xc2\xa3' string to the PAM module that comes with
> RedHat 7.0 certainly doesn't work (which is odd).
>
> Regards,
> Phil
>
> +------------------------------------------+
> | Phil Mayers |
> | Network & Infrastructure Group |
> | Information & Communication Technologies |
> | Imperial College |
> +------------------------------------------+
>
> -----Original Message-----
> From: Paul Haldane [mailto:[EMAIL PROTECTED]]
> Sent: 23 August 2001 16:16
> To: [EMAIL PROTECTED]
> Subject: Re: kerberos auth against w2k server with 8 bit chars in
> password
>
>
> That was my thought when I saw Jeffrey Altman's reply. The IMAP server is
> usig PAM to authenticate against the W2K Kerberos server so I thought
> I could put a quick transformation of the password to utf-8 before it
> gets passed to the Kerberos routines. I did that and I can see from
> debug statements that the encoding is happening but I still can't login
> to an account with a pound sign in the password :-<. At least I haven't
> broken things compeletely - passwords containing only standard ascii
> still work.
>
> Would you expect this to work? It may be that my encoding routine is
> wrong.
>
> Paul
> --
>
