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

 
 

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

Submitted by:  None
Submitted on:  Mon 12 Dec 2011 03:44:26 PM UTC  
 
Category: NonePriority: 5 - Normal
Severity: 3 - NormalStatus: Need Info
Privacy: PublicAssigned to: Werner Baumann <wbaumann>
Originator Email: -unavailable-Open/Closed: Closed
Operating System: GNU/Linux

Add a New Comment (Rich MarkupRich Markup):
   

You are not logged in

Please log in, so followups can be emailed to you.

 

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

Werner Baumann <wbaumann>
Project AdministratorIn charge of this item.
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 File(s):
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by wbaumann (Posted a comment)
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 4 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Sun 20 Apr 2014 06:03:27 PM UTCwbaumannStatusIn Progress=>Need Info
      Open/ClosedOpen=>Closed
    Sun 18 Dec 2011 04:54:08 PM UTCwbaumannStatusNone=>In Progress
      Assigned toNone=>wbaumann

    Back to the top


    Powered by Savane 3.1-cleanup