maindavfs2 - Support: sr #107908, box.com, https, segmentation...

 
 

sr #107908: box.com, https, segmentation fault, and their wildcard cert

Submitter:  None
Submitted:  Mon 12 Dec 2011 03:44:26 PM UTC
   
 
Category:  None Priority:  5 - Normal
Severity:  3 - Normal Status:  Need Info
Privacy:  Public Assigned to:  _71007
Originator Email:  -email is unavailable- Open/Closed:  Closed
Operating System:  GNU/Linux
* Mandatory Fields

Add a New Comment Rich Markup
   

Thu 22 Dec 2011 02:40:30 PM UTC, comment #2: 

Thanks Werner. 

I am now in the process of trying to get my neon library compiled from the latest source release. I am going to try gnutls and openssl, in that order, to see if it resolves my issue.  If that doesn't do the trick, I will try running the debug options in the conf file.  Dan.

Anonymous
Sun 18 Dec 2011 04:54:08 PM UTC, comment #1: 

Sorry for the delay.

I have a free box account for testing but rarely use it. So I didn't notice the changes. Thanks for the information.

Unfortunately connecting to the new address with SSL works without problems on my system. Even the certificate is verified with the system's CA-files. I'm using gnutls instead of OpenSSL but I don't think this makes the difference.

First: davfs2's configure script does not know the --with-ssl option. All calls to the SSL-library are done by neon.

Most probably the error is caused by some problem with your neon-library. Please look at neon's './configure --help' for how to properly compile against the OpenSSL library.

I'm not familiar with arm and don't know what special requirements are there. But as far as I know Debian has a working arm-port. So looking at Debian's Neon source package might help.

If your system has a working log facility you may add options 'debug most' and 'debug ssl' to oyur davfs2.conf file and you will get a lot of debug information in your log files. This may help to find where the error occurs. If you can configure your system to print a backtrace this might help too.

Werner


- <_71007>
Mon 12 Dec 2011 03:44:26 PM UTC, original submission:  

Since I have read through the ticket history I know you have a bit of disdain for how box.net handles webdav, but I hope you might be able to provide me some insight on my issue.

Until the past week, I was able to mount my box.net account using their non-ssl link http://box.net/dav.  All was well until they cut over to their box.com rebranding.  They now force https on all of their connections, include webdav.  At first I was getting a 302 come back when I issued the mount command.  Once I found the correct url, https://www.box.com/dav, entered my authentication, I was greeted with the 'do you accept this cert' dialog y/N (it appears Box uses a wildcard cert, which I think could be an issue).  When I select 'y', I simple get 'segmentation fault' and pushed back to the prompt.  I had originally tried using their https link before resorting to the http version.  I was using my 50gb box account as an offsite backup for my qnap nas.

I am running neon_0.29.3-1_arm.ipk, openssl_0.9.8p-1_arm.ipk, and davfs 1.4.6 compiled from source with the following configuration:
./configure --prefix=/opt --with-neon=/opt --with-ssl=openssl

I am a developer by trade, albeit windows.  My linux experience is relegated to configuration, running make files, and general scripting but I will try/run anything you need to get you more details.

I did request they re-enable their non-ssl link for while but I don't think it will happen.

Thanks, Dan.

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 _71007 (Posted a comment)
  •  

    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 4 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2014-04-20 _71007 StatusIn Progress Need Info
        Open/ClosedOpen Closed
    2011-12-18 _71007 StatusNone In Progress
        Assigned toNone _71007

    Back to the top

    Powered by Savane 3.13-758e.
    Corresponding source code