maindavfs2 - Support: sr #110446, Unable to authenticate with NTLMv2

 
 

sr #110446: Unable to authenticate with NTLMv2

Submitter:  None
Submitted:  Wed 17 Feb 2021 03:38:37 AM UTC
   
 
Category:  None Priority:  5 - Normal
Severity:  5 - Blocker Status:  Done
Privacy:  Public Assigned to:  _71007
Originator Email:  -email is unavailable- Open/Closed:  Open
Operating System:  GNU/Linux
* Mandatory Fields

Add a New Comment Rich Markup
   

Sat 15 May 2021 09:10:32 AM UTC, comment #3: 

You don't need option --with-ssl. The configure script of davfs2 does not use it.

What you need is a Neon library that is compiled against OpenSSL and the development files for this version of Neon and for no other Neon version.

I am not familiar with centOS. It seems to me that they have no Neon library that is compiled against OpenSSL, but I am not sure. I also don't know how they package the development files.

You should contact some centOS help desk to get information about that.

If your new davfs2 program crashes after the password prompt without any error message then the build process was seriously broken.

Werner

- <_71007>
Thu 01 Apr 2021 10:34:23 PM UTC, comment #2: 

I am on a centOS system, i tried to build the neon package from src using "./configure --with-ssl=openssl" and then linking the davfs2 to the newly build neon lib(verified with ldd) but this does not seem to do the trick. Still facing the same mount errors.

  • LDD o/p of davfs:


# ldd /sbin/mount.davfs
linux-vdso.so.1 =>  (0x00007ffe093b5000)
libneon.so.27 => /usr/lib64/libneon.so.27 (0x00007fd075f53000)
libgcc_s.so.1 => /usr/lib64/libgcc_s.so.1 (0x00007fd075d3d000)
libc.so.6 => /usr/lib64/libc.so.6 (0x00007fd07597d000)
libz.so.1 => /usr/lib64/libz.so.1 (0x00007fd075767000)
libssl.so.10 => /usr/lib64/libssl.so.10 (0x00007fd0754f9000)
libcrypto.so.10 => /usr/lib64/libcrypto.so.10 (0x00007fd07510e000)
libpakchois.so.0 => /usr/lib64/libpakchois.so.0 (0x00007fd074f07000)
libgssapi_krb5.so.2 => /usr/lib64/libgssapi_krb5.so.2 (0x00007fd074cbb000)
libkrb5.so.3 => /usr/lib64/libkrb5.so.3 (0x00007fd0749d6000)
libk5crypto.so.3 => /usr/lib64/libk5crypto.so.3 (0x00007fd0747a4000)
libcom_err.so.2 => /usr/lib64/libcom_err.so.2 (0x00007fd0745a0000)
libproxy.so.1 => /usr/lib64/libproxy.so.1 (0x00007fd07437f000)
libexpat.so.1 => /usr/lib64/libexpat.so.1 (0x00007fd074155000)
/lib64/ld-linux-x86-64.so.2 (0x00007fd07639e000)
libresolv.so.2 => /usr/lib64/libresolv.so.2 (0x00007fd073f3b000)
libdl.so.2 => /usr/lib64/libdl.so.2 (0x00007fd073d37000)
libpthread.so.0 => /usr/lib64/libpthread.so.0 (0x00007fd073b1b000)
libkrb5support.so.0 => /usr/lib64/libkrb5support.so.0 (0x00007fd07390c000)
libkeyutils.so.1 => /usr/lib64/libkeyutils.so.1 (0x00007fd073708000)
libmodman.so.1 => /usr/lib64/libmodman.so.1 (0x00007fd073500000)
libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007fd0731f8000)
libm.so.6 => /usr/lib64/libm.so.6 (0x00007fd072ef6000)
libselinux.so.1 => /usr/lib64/libselinux.so.1 (0x00007fd072cd1000)
libpcre.so.1 => /usr/lib64/libpcre.so.1 (0x00007fd072a70000)
liblzma.so.5 => /usr/lib64/liblzma.so.5 (0x00007fd07284b000)

  • LDD o/p of libneon:

# ldd /usr/lib64/libneon.so.27
linux-vdso.so.1 =>  (0x00007ffda1de8000)
libz.so.1 => /usr/lib64/libz.so.1 (0x00007f62c1610000)
libssl.so.10 => /usr/lib64/libssl.so.10 (0x00007f62c13a2000)
libcrypto.so.10 => /usr/lib64/libcrypto.so.10 (0x00007f62c0fb7000)
libpakchois.so.0 => /usr/lib64/libpakchois.so.0 (0x00007f62c0db0000)
libgssapi_krb5.so.2 => /usr/lib64/libgssapi_krb5.so.2 (0x00007f62c0b64000)
libkrb5.so.3 => /usr/lib64/libkrb5.so.3 (0x00007f62c087f000)
libk5crypto.so.3 => /usr/lib64/libk5crypto.so.3 (0x00007f62c064d000)
libcom_err.so.2 => /usr/lib64/libcom_err.so.2 (0x00007f62c0449000)
libproxy.so.1 => /usr/lib64/libproxy.so.1 (0x00007f62c0228000)
libexpat.so.1 => /usr/lib64/libexpat.so.1 (0x00007f62bfffe000)
libc.so.6 => /usr/lib64/libc.so.6 (0x00007f62bfc3e000)
libresolv.so.2 => /usr/lib64/libresolv.so.2 (0x00007f62bfa24000)
libdl.so.2 => /usr/lib64/libdl.so.2 (0x00007f62bf820000)
libpthread.so.0 => /usr/lib64/libpthread.so.0 (0x00007f62bf604000)
libkrb5support.so.0 => /usr/lib64/libkrb5support.so.0 (0x00007f62bf3f5000)
libkeyutils.so.1 => /usr/lib64/libkeyutils.so.1 (0x00007f62bf1f1000)
/lib64/ld-linux-x86-64.so.2 (0x00007f62c1a51000)
libmodman.so.1 => /usr/lib64/libmodman.so.1 (0x00007f62befe9000)
libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007f62bece1000)
libm.so.6 => /usr/lib64/libm.so.6 (0x00007f62be9df000)
libgcc_s.so.1 => /usr/lib64/libgcc_s.so.1 (0x00007f62be7c9000)
libselinux.so.1 => /usr/lib64/libselinux.so.1 (0x00007f62be5a4000)
libpcre.so.1 => /usr/lib64/libpcre.so.1 (0x00007f62be343000)
liblzma.so.5 => /usr/lib64/liblzma.so.5 (0x00007f62be11e000)

Also, right now i am not able to go past the initial username/password user input
i.e.
_Please enter the username to authenticate with server
http://10.X.X.X/Shared Documents or hit enter for none.
  Username: administrator
Please enter the password to authenticate user administrator with server
http://10.X.X.X/Shared Documents or hit enter for none.
  Password:
_

My initial concern right now is i am not going past this login details, i am not trying to mount a webdav on https so it should not be an ssl cert issue, but not sure.


Shubham Pachpute <pachputeshubham>
Tue 09 Mar 2021 05:14:21 PM UTC, comment #1: 

NTML is only supported by a Neon library that is compiled against OpenSSL. If compiled against GnuTLS then NTLM will not work.

You can use "ldd /sbin/mount.davfs" to check the libraries that are used.

What you can do:

  • If you compile davfs2 from the sources: You need a neon library installed that uses Open SSL (this should be the case on almost all systems). You need the headers of that neon version installed. The headers of a neon version that uses GnuTLS must not be installed (they would interfere with the build process).


  • You can try to install a package that uses Neon with OpenSSL. Debian 10 and newer do this (because of NTLM).


Werner

- <_71007>
Wed 17 Feb 2021 03:38:37 AM UTC, original submission:  

I have lost ways in trying to get this work. Can someone please guide me with the exact steps of installing davfs2 and the neon libraries. Currently I have neon 0.31.2 and davfs 1.6 installed.
I am unable to authenticate with ntlmv2 and failing with "could not parse challenge" error.

If anyone has any documentation on what exact options are required for ntlmv2 to work during installation or mounting, it would be great.

Thanking in anticipation

 Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by pachputeshubham (Posted a comment)
  • -email is unavailable- added by _71007 (Posted a comment)
  • -email is unavailable- added by None (Submitted the item)

    •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follow 3 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2021-05-15 _71007 StatusIn Progress Done
    2021-03-09 _71007 StatusNone In Progress
        Assigned toNone _71007

    Back to the top

    Copyright © 2024 Free Software Foundation, Inc.
    Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved.
    The Levitating, Meditating, Flute-playing Gnu logo is a GNU GPL'ed image provided by the Nevrax Design Team.
    Page source code

    Powered by Savane 3.13-397b.
    Corresponding source code