edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Adam Thompson <arthompson1990@gmail.com>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] NTLM in edbrowse
Date: Mon, 11 Aug 2014 10:41:17 +0100	[thread overview]
Message-ID: <20140811094117.GC5637@toaster.adamthompson.me.uk> (raw)

[-- Attachment #1: Type: text/plain, Size: 840 bytes --]

Hi,

At the company where I work, we use a *lot* of NTLM authenticated services.
Attempting to use these with edbrowse I noticed none of them appear to authenticate at all.
With db7 switched on, I can see no round-trip,
dispite the fact that apparently ntlm requires an auth handshake,
and we're using HTTPAUTH_ANY which should mean that libcurl checks what the web
server will do before sending the auth credentials.
I also see no evidence of any kind of auth header during the requests.

As these are internal servers, I'm not entirely sure if I can post a transcript unfortunately.

Any ideas what's going on? Having looked through the code I can't spot why this
isn't working as it looks like we do everything as per the curl docs,
unless there's some form of extra step we need to perform to get the round trip to work?

Cheers,
Adam.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

             reply	other threads:[~2014-08-11  9:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-11  9:41 Adam Thompson [this message]
2014-08-11 14:09 ` Chris Brannon
2014-08-11 15:24   ` Adam Thompson
2014-08-11 21:25     ` Adam Thompson
2014-08-11 21:46 Karl Dahlke
2014-08-11 22:04 ` Adam Thompson
2014-08-11 22:25   ` Chris Brannon
2014-08-13  8:47     ` Adam Thompson
2014-08-14 20:25       ` Adam Thompson
2014-08-11 22:14 Karl Dahlke

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=20140811094117.GC5637@toaster.adamthompson.me.uk \
    --to=arthompson1990@gmail.com \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    /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).