From: Steve Simon <steve@quintile.net>
To: 9front@9front.org
Subject: Re: [9front] upas ntlm auth -- untested, unused?
Date: Wed, 11 Dec 2019 12:22:59 +0000 [thread overview]
Message-ID: <62CC98B0-80D2-4DC8-ADB4-27C45E29AF8E@quintile.net> (raw)
In-Reply-To: <C98E2E65F86F8C97C4C594DC15595402@eigenstate.org>
i wrote the ntlm code for webfs but i cannot remember if i pirted it to imap too.
i used imap onto exchange for many years and that might have needed it so it might have been me (if noone else claims it).
if it is my code then its untested on 9front rather than untested at all - i used the labs code at that time.
-Steve
> On 11 Dec 2019, at 7:29 am, ori@eigenstate.org wrote:
>
> The upas ntlm auth code has a comment claiming it's untested.
> I don't have an imap server that does ntlm. Is anyone is using
> the upas ntlm auth? Does anyone have access to an imap server
> that does ntlm?
>
> I'd like to remove either the code or the comment.
prev parent reply other threads:[~2019-12-11 12:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 7:28 ori
2019-12-11 12:22 ` Steve Simon [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=62CC98B0-80D2-4DC8-ADB4-27C45E29AF8E@quintile.net \
--to=steve@quintile.net \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).