But I'm not willing to send a cleartext password for my work account
across the internet.
Does Gnus support the "Secure Password Authentication" that Outlook
Express does? I don't think we have the ability to do SSL via our E2K
servers, though maybe the OWA/IMAP redirector thing can.
Any ideas or information would be appreciated.
-K
I should have added that I'm running Windows XP Pro with Xemacs
21.4.13 (Cygwin). I'm running Gnus 5.10.2.
-K
hi,
imap supports "Encrypted username/password".
search the gnus info files for this.
martin
>>
>> Does Gnus support the "Secure Password Authentication" that Outlook
>> Express does? I don't think we have the ability to do SSL via our E2K
>> servers, though maybe the OWA/IMAP redirector thing can.
KH>
KH> I should have added that I'm running Windows XP Pro with Xemacs
KH> 21.4.13 (Cygwin). I'm running Gnus 5.10.2.
KH>
KH> -K
KH>
--
parozusa at web dot de
Yes, I've seen that. It's not the same, I think. I don't think that
either Digest-MD5 or CRAM are what NTLM uses, which is what Outlook
Express means by "Secure Password Authentication".
I'm not giving up yet, but it sounds as if I'm stuck with Outlook
Express for now.
-K
Kathryn Huxtable <kat...@kathrynhuxtable.org> writes:
> Yes, I've seen that. It's not the same, I think. I don't think that
> either Digest-MD5 or CRAM are what NTLM uses, which is what Outlook
> Express means by "Secure Password Authentication".
NTLM is a proprietary MS protocol. The others are open protocols,
specified in regular Internet RFCs.
benny
It's proprietary, but documented. Perl has an interface in one of its
many modules. It's also lame, but it's what I have available.
-K
Gnus in CVS will support NTLM authentication in IMAP when the next
development phase starts.
Great! I'll wait until then and continue to harrass my Exchange admins
to support IMAP over SSL.
-K
> I recently checked cvs and found that ntlm is supported but I still
> can't get imap ntlm authentication to work. Am I missing some
> coniguration. please help.
The IMAP code hasn't been changed to use the new SASL library yet.
Only ManageSieve has. I'm waiting for some responses on copyright
issues before I integrate the SASL library more intimately in Gnus.
> Do you expect the issues to be resolved anytime soon. Please
> update. Thanks.
Gnus in CVS have the SASL library, so the copyright issues have been
resolved, to my knowledge. However, RMS brought up some problems with
exporting crypto software from the US, so I'm not sure how to proceed.
Most of the SASL library doesn't do encryption, so it should be fine,
but NTLM however do use encryption (DES), so I think it will have to
be removed. Other discussions suggest it might be better to use GNU
SASL for all things SASL (so we can support STARTTLS and GSSAPI),
which could work (GNU SASL support NTLM in client mode, and is
developed outside of the US).