You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(9) |
Aug
(12) |
Sep
|
Oct
(7) |
Nov
(12) |
Dec
(3) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
(1) |
Feb
(4) |
Mar
(3) |
Apr
(6) |
May
(3) |
Jun
|
Jul
(1) |
Aug
(13) |
Sep
(9) |
Oct
(56) |
Nov
(3) |
Dec
(2) |
2003 |
Jan
(1) |
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
|
Aug
(4) |
Sep
|
Oct
(8) |
Nov
(6) |
Dec
(2) |
2004 |
Jan
(1) |
Feb
(3) |
Mar
(7) |
Apr
(1) |
May
|
Jun
(9) |
Jul
|
Aug
(9) |
Sep
(1) |
Oct
(3) |
Nov
(7) |
Dec
|
2005 |
Jan
|
Feb
(8) |
Mar
(3) |
Apr
(13) |
May
(2) |
Jun
(5) |
Jul
(30) |
Aug
(7) |
Sep
(14) |
Oct
(1) |
Nov
(1) |
Dec
(14) |
2006 |
Jan
(8) |
Feb
(4) |
Mar
(2) |
Apr
(6) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(8) |
Oct
(5) |
Nov
|
Dec
(1) |
2007 |
Jan
|
Feb
|
Mar
(1) |
Apr
(2) |
May
(1) |
Jun
(13) |
Jul
|
Aug
(9) |
Sep
|
Oct
|
Nov
(7) |
Dec
|
2008 |
Jan
|
Feb
(11) |
Mar
(3) |
Apr
(7) |
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
(5) |
Oct
|
Nov
|
Dec
|
2009 |
Jan
(2) |
Feb
|
Mar
|
Apr
(1) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Werner B. <wer...@on...> - 2009-05-23 15:51:49
|
The davfs2-project moved to Savannah http://savannah.nongnu.org/projects/davfs2 This mailing list is closed. Please visit http://savannah.nongnu.org/support/?group=davfs2 for bug reports, support requests and any discussion about davfs2. Werner Project Admin |
From: José L. G. R. <jg...@gm...> - 2009-04-02 10:15:34
|
Hi! There is a way of disable completly the caching on read and puts? Many thanks in advance. -- José Luis Gordo Romero |
From: Werner B. <wer...@on...> - 2009-01-11 15:29:34
|
Hello Sung, there has been a bug report concerning SharePoint that might be related: http://sourceforge.net/tracker/index.php?func=detail&aid=1863061&group_id=26275&atid=386747 SharePoint seems to use the wrong date-format for lastmodified. I am not sure whether this SharePoint bug is the reason in this case. Catching the traffic between davfs2 and SharePoint would help. The traffic should contain a PROPFIND-request and response. Alternatively setting options "debug most" and "debug httpbody" in davfs2.conf and sending the debug messages from the log-files could show the reason of the problem too. Cheers Werner |
From: Sung K. <hu...@gm...> - 2009-01-09 00:39:33
|
FYI, - Sung ---------- Forwarded message ---------- From: Sylvester Rajasekaran <syl...@gm...> Date: Fri, Jan 9, 2009 at 5:44 AM Subject: Help on Davfs2 To: hu...@gm... Hi Sung Kim, We are trying to mount a sharepoint directory onto a RHEL 4 (2.6.9-42.ELsmp). I could able to mount the Filesystem using davfs2 (using the latest). But what happens is the filesystem of the mount point is showing year 2038 Here is the ls -l of the file system ( webmount mounted in DAVFS Filesystem format) # Webdav(davfs2) MOUNT configuration below (/etc/fstab) http://sharepoint-test:7777/s2wikidata /opt/webmount davfs rw,user,uid=oss,gid=oss,noaskauth,nolocks,auto 0 0 [root@pstemp3 opt]# ls -l total 25 drwxr-xr-x 9 oss oss 4096 Dec 18 15:39 attachments -rwxr-xr-x 1 root root 1242 Dec 22 10:26 ldap_ad_search.sh drwxr-xr-x 15 oss oss 4096 Jan 7 15:26 inform drwxr-xr-x 7 oss oss 200 Jan 18 2038 webmount [root@pstemp3 opt]# ls -l webmount/ total 3 drwxr-xr-x 3 oss oss 376 Jan 18 2038 Forms drwxr-xr-x 2 oss oss 64 Jan 18 2038 help-en drwx------ 2 oss oss 256 Jan 7 16:11 lost+found drwxr-xr-x 2 oss oss 96 Jan 18 2038 new1 drwxr-xr-x 9 oss oss 424 Jan 18 2038 test-1 The affected dates are in Blue color. Could you please let me know what is the issue here and is there any option should I have to enable in davfs2.conf file? Thanks in advance ___________________________ Sylvester ___________________________ |
From: Werner B. <wer...@on...> - 2008-09-21 17:12:05
|
Hello Sebastian, just noticed you are already running davfs2-1.3.3 and a recent enough version of neon. So this can't be the problem. Cheers Werner |
From: Werner B. <wer...@on...> - 2008-09-16 10:41:20
|
Hello Sebastian, I am not familiar with this kind of messages from tcpdump. But I assume "R" means RST. So davfs2 interrupted the connection with RST, which should not happen. I assume neon thought there was an error in the XML-Body and abandoned the connection. I will have to examine the XML-body more closely. This will take some time. You might rerun the request with additional option "debug xml". This will raise the size of the log-file from "real big" to "horrible", because neon lists every step in parsing the XML-Body. There should be a message at the end, why it stopped parsing. There are more RST-Packets. As far as I know these should only be used in case of an error. Maybe there is some network related issue. What might help too: Is there a ChangeLog that lists the changes from your old server-version to the current one? The error first showed when you cleared a server-side cache. Is it possible, that the request was served out of the cache and only when the server had to newly create the response the problem showed up, though it had been there before? Now I will first start looking closer at the XML-body. Cheers Werner |
From: Werner B. <wer...@on...> - 2008-09-13 17:19:07
|
Hello Sebastian, thanks for the logs. The response to the PROPFIND-request for the directory in question is truncated. The headers say content-length: 1293373 But after receiving about 800 kB of data the connection is closed. I cannot see, which side initiated the closing. Can you try to evaluate which side closes the connection (using wireshark)? Maybe you can also get some information about the reason. Have there been any changes in the time before you first noticed the error (server, network, client)? There are some errors or misfeatures that are most probably not related to this error, but might cause trouble some time: Some responses send the executable-property like this: <ap:executable>0</ap:executable> Valid values are F and T (false and true). See http://www.webdav.org/mod_dav/ davfs2 will set executable false in this case, so it is not a problem now. But the value 1 will not be interpreted as True and setting this property by davfs2 will probably not work. The responses for non-collection resources send 404 Not Found for the getcontentlength property. davfs2 needs this property to show the correct file size. getlastmodified is Not Found too. davfs2 cannot show any meaningful file times. Cheers Werner |
From: Werner B. <wer...@on...> - 2008-09-01 19:10:26
|
Hello Sebastian, the listing of the contents of a directory is contained in the XML-body in response to a PROPFIND-request. An error like this is most probably caused by Neon and the server disagreeing about how to properly format, encode and parse XML. Looking at the XML-body should be the first step to take. Please use debug options debug most debug httpbody The log will now get real big. Try to restrict to mount ls for one directory showing the error (the smaller one) umount Please send gziped log to my private mail address. Instead of using the debug option, you might use wireshark to fetch just this one PROPFIND-request and response. This will be smaller. Cheers Werner |
From: Sebastian R. <seb...@l0...> - 2008-09-01 13:38:53
|
Hi, since some time, I've recognized, that two folders, containing some thousands vcards, do not show the contents, when I make an ls on the folders. When I take konqueror, and go to webdavs://.... then the contents is show. Therefore I guess the problem is somewhere on the davfs side. This is the summary, from the configure run: Configuration for building davfs2 1.3.3: Install Prefix: /usr/local Compiler: gcc Large File Support: no Neon Library: library in /usr/local (0.26.3) SSL is supported by neon National Language Support: libc I also tried with neon 0.28.0, but with the same result. I also had the server running in debug mode, and as far as I interpret the output, I saw the vcards are sent to the client. below my configuration file, with the debug statements I used: use_proxy 0 servercert /usr/local/etc/davfs2/ogocert.pem use_displayname 1 use_locks 1 debug cache debug config debug kernel debug http debug xml debug locks I mounted the webdav with debug, but that created a 16MB logfile, that I don't want to send to the list, due to the size. I cannot find anything special in it, to figure out, where the problem is, any idea what to look for, or can I send the file to someone offlist? The only errors I see, are the following: Sep 1 14:41:42 nfspublic mount.davfs: Request ends, status 200 class 2xx, error line: 200 OK Sep 1 14:41:46 nfspublic mount.davfs: [hdr] X-Dav-Error: 200 No error Sep 1 14:41:46 nfspublic mount.davfs: Header Name: [x-dav-error], Value: [200 No error] Sep 1 14:41:46 nfspublic mount.davfs: Request ends, status 207 class 2xx, error line: 207 Multi-Status Sep 1 14:41:56 nfspublic mount.davfs: [hdr] X-Dav-Error: 200 No error Sep 1 14:41:56 nfspublic mount.davfs: Header Name: [x-dav-error], Value: [200 No error] Sep 1 14:41:56 nfspublic mount.davfs: Request ends, status 207 class 2xx, error line: 207 Multi-Status Sep 1 14:41:59 nfspublic mount.davfs: [hdr] X-Dav-Error: 200 No error Sep 1 14:41:59 nfspublic mount.davfs: Header Name: [x-dav-error], Value: [200 No error] Sep 1 14:42:03 nfspublic mount.davfs: Request ends, status 207 class 2xx, error line: 207 Multi-Status but it says, No error. any idea how to get the directories filled again? kind regards Sebastian |
From: Damon R. <dam...@gm...> - 2008-05-22 11:06:37
|
Ah I see. Thats a bit more work than I was anticipating. :-) Thanks anyway, I was just looking for a way to copy some backup files up to a webdav share.. I'll try scripting cadaver instead.. Damon. 2008/5/22 Werner Baumann <wer...@on...>: > Hello Damon, > > davfs2 is written to be port*able*. But so far it has only been build on > GNU/Linux-systems and not been ported to anything else. You will have to do > a complete port. > > One reason why I never thought about porting to cygwin (besides knowing > nothing about system-programming on windows) is: > davfs2 mounts a file system and davfs2 communicates with the Linux-kernel > via /dev/fuse or /dev/coda. > Now the file system on windows is quite different from the file system on > Unix-like operating systems. And the kernel is obviously very different too. > I would be surprised if cygwin could provide the interfaces needed for > davfs2 to run. But I never cared about. > > So I will not be of any help here. But if, against what I believe, you > succeed in porting to cygwin, I would be very interested. > > Cheers > Werner > |
From: Werner B. <wer...@on...> - 2008-05-22 10:33:43
|
Hello Damon, davfs2 is written to be port*able*. But so far it has only been build on GNU/Linux-systems and not been ported to anything else. You will have to do a complete port. One reason why I never thought about porting to cygwin (besides knowing nothing about system-programming on windows) is: davfs2 mounts a file system and davfs2 communicates with the Linux-kernel via /dev/fuse or /dev/coda. Now the file system on windows is quite different from the file system on Unix-like operating systems. And the kernel is obviously very different too. I would be surprised if cygwin could provide the interfaces needed for davfs2 to run. But I never cared about. So I will not be of any help here. But if, against what I believe, you succeed in porting to cygwin, I would be very interested. Cheers Werner |
From: Damon R. <dam...@gm...> - 2008-05-22 09:34:12
|
Hi, I'm trying to compile davfs2 under cygwin but am getting a make error.. Any ideas? Thanks, Damon. damon@freyr /usr/local/src/davfs2-1.3.2 $ make make all-recursive make[1]: Entering directory `/usr/local/src/davfs2-1.3.2' Making all in po make[2]: Entering directory `/usr/local/src/davfs2-1.3.2/po' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/usr/local/src/davfs2-1.3.2/po' Making all in etc make[2]: Entering directory `/usr/local/src/davfs2-1.3.2/etc' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/usr/local/src/davfs2-1.3.2/etc' Making all in man make[2]: Entering directory `/usr/local/src/davfs2-1.3.2/man' Making all in de make[3]: Entering directory `/usr/local/src/davfs2-1.3.2/man/de' make[3]: Nothing to be done for `all'. make[3]: Leaving directory `/usr/local/src/davfs2-1.3.2/man/de' Making all in es make[3]: Entering directory `/usr/local/src/davfs2-1.3.2/man/es' make[3]: Nothing to be done for `all'. make[3]: Leaving directory `/usr/local/src/davfs2-1.3.2/man/es' make[3]: Entering directory `/usr/local/src/davfs2-1.3.2/man' make[3]: Nothing to be done for `all-am'. make[3]: Leaving directory `/usr/local/src/davfs2-1.3.2/man' make[2]: Leaving directory `/usr/local/src/davfs2-1.3.2/man' Making all in src make[2]: Entering directory `/usr/local/src/davfs2-1.3.2/src' gcc -DPROGRAM_NAME=\"mount.davfs\" -DDAV_SYS_CONF_DIR=\"/usr/local/etc/davfs2\" -DDAV_SYS_RUN=\"/var/run/mount.davfs\" -DDAV_SYS_CACHE=\"/var/cache/davfs2\" -DD AV_SECRETS=\"secrets\" -DDAV_CONFIG=\"davfs2.conf\" -DDAV_CERTS_DIR=\"certs\" -D DAV_CLICERTS_DIR=\"private\" -DDAV_DATA_DIR=\"/usr/local/share/davfs2\" -DLOCALE DIR=\"/usr/local/share/locale\" -DDAV_USER=\"davfs2\" -DDAV_GROUP=\"davfs2\" -DH AVE_CONFIG_H -I. -I.. -Wall -g -O2 -I/usr/include/neon -MT cache.o -MD -MP -M F .deps/cache.Tpo -c -o cache.o cache.c cache.c:29:19: error.h: No such file or directory cache.c:51:23: sys/xattr.h: No such file or directory cache.c: In function `dav_init_cache': cache.c:533: warning: implicit declaration of function `error' cache.c: In function `write_node': cache.c:2797: warning: long int format, different type arg (arg 5) cache.c:2797: warning: long int format, different type arg (arg 5) cache.c:2847: warning: int format, uid_t arg (arg 5) cache.c:2847: warning: int format, uid_t arg (arg 5) cache.c:2850: warning: int format, gid_t arg (arg 5) cache.c:2850: warning: int format, gid_t arg (arg 5) make[2]: *** [cache.o] Error 1 make[2]: Leaving directory `/usr/local/src/davfs2-1.3.2/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/local/src/davfs2-1.3.2' make: *** [all] Error 2 |
From: Werner B. <wer...@on...> - 2008-04-11 18:57:50
|
The problem is caused by an error in the fuse kernel module. It miscalculates the allowed size of data in writes, which results in to big messages resulting in an IO-Error. The davfs2-version in CVS now takes care of this error by telling fuse a maximum size for write, that is smaller than the actual buffer size, and the error no longer happens. The problem occurs with all 1.x.x-versions of davfs2. It only did not show up, as long as davfs2 used coda by default. With version 1.2.2 davfs2 switched to use fuse by default. To use fuse or coda: The main difference (for davfs2) is: in read and write operations coda acts directly on the cached file, without involving davfs2. If you mainly upload big files, coda should show slightly better performance. When the contents of directories is changing frequently, coda seems to sometimes reuse old, stale information, causing "file does not exist"-errors. fuse does not show this problem. Cheers Werner |
From: Werner B. <wer...@on...> - 2008-04-11 18:56:23
|
The problem is caused by an error in the fuse kernel module. It miscalculates the allowed size of data in writes, which results in to big messages resulting in an IO-Error. The davfs2-version in CVS now takes care of this error by telling fuse a maximum size for write, that is smaller than the actual buffer size, and the error no longer happens. The problem occurs will all 1.x.x-versions of davfs2. It only did not show up, as long as davfs2 used coda by default. With version 1.2.2 davfs2 switched to use fuse by default. To use fuse or coda: The main difference (for davfs2) is: in read and write operations coda acts directly on the cached file, without involving davfs2. If you mainly upload big files, coda should show slightly better performance. When the contents of directories is changing frequently, coda seems to sometimes reuse old, stale information, causing "file does not exist"-errors. fuse does not show this problem. Cheers Werner |
From: Werner B. <wer...@on...> - 2008-04-02 19:53:06
|
This error seems to happen, when an application tries to write a block of data, that does not fit in the buffer used for communication between davfs2 and fuse kernel file system. You can fix this, by setting in davfs2.conf option buf_size 65 This will extend the buffer to 65 KiByte, so blocks up to 64 KiByte will fit. The reason for this, and why it does not happen in version 1.2.1 still has to be investigated. Werner |
From: Werner B. <wer...@on...> - 2008-04-02 19:51:56
|
This error seems to happen, when an application tries to write a block of data, that does not fit in the buffer used for communication between davfs2 and fuse kernel file system. You can fix this, by setting in davfs2.conf option buf_size 65 This will extend the buffer to 65 KiByte, so blocks up to 64 KiByte will fit. The reason for this, and why it does not happen in version 1.2.1 still has to be investigated. Werner |
From: Noah D. <noa...@gm...> - 2008-04-02 17:52:00
|
On Wed, Apr 2, 2008 at 2:16 AM, Dieter Bloms <da...@bl...> wrote: > Hi Noah, > > > On Tue, Apr 01, Noah Dain wrote: > > > With davfs2 versions after 1.2.1 I cannot create files (greater than > > some small size). Instead I get back a write error, and a zero byte > > file is created with the appropriate name. However, this only seems > > to occur with programs which use the qt graphical toolkit. Command > > line and gtk apps can write large files. > > I have similar problems. > Tonight I tried coda instead of fuse with success. > > Please give coda as kernelfs a try. yes, coda works fine with 1.2.2 and 1.3.0. thanks, -- Noah Dain "The beatings will continue, until morale improves" - the Management |
From: Dieter B. <da...@bl...> - 2008-04-02 06:16:40
|
Hi Noah, On Tue, Apr 01, Noah Dain wrote: > With davfs2 versions after 1.2.1 I cannot create files (greater than > some small size). Instead I get back a write error, and a zero byte > file is created with the appropriate name. However, this only seems > to occur with programs which use the qt graphical toolkit. Command > line and gtk apps can write large files. I have similar problems. Tonight I tried coda instead of fuse with success. Please give coda as kernelfs a try. -- best regards Dieter -- I do not get viruses because I do not use MS software. If you use Outlook then please do not put my email address in your address-book so that WHEN you get a virus it won't use my address in the From field. |
From: Noah D. <noa...@gm...> - 2008-04-02 02:26:48
|
With davfs2 versions after 1.2.1 I cannot create files (greater than some small size). Instead I get back a write error, and a zero byte file is created with the appropriate name. However, this only seems to occur with programs which use the qt graphical toolkit. Command line and gtk apps can write large files. If a file is sufficiently small, it can be written via a qt application. For example, a text file of "hello, world!" can be written by qt applications to a davfs2 mounted filesystem. I'm not sure what the upper bounds is on the size yet (or if it even matters). The server is 'Apache/2.2.8 (Debian) DAV/2'. I have root access on the server. Client systems: ubuntu hardy/8.04 beta1 amd64; debian etch i386 hardy is shipping with 1.2.1, but I couldn't get davfs2 working with autofs. It seems that was fixed with 1.2.2, but then I cannot write larger files anymore. 1.3.0 exhibits the same issue as 1.2.2 for testing, i'm building from the source tarballs, all defaults used ( ./configure && make && sudo make install ) -- Configuration for building davfs2 1.2.1: Install Prefix: /usr/local Compiler: gcc Large File Support: no Neon Library: library in /usr (0.26.4) SSL is supported by neon National Language Support: libc -- Configuration for building davfs2 1.2.2: Install Prefix: /usr/local Compiler: gcc Large File Support: no Neon Library: library in /usr (0.26.4) SSL is supported by neon National Language Support: libc -- gcc (GCC) 4.2.3 -- Noah Dain "The beatings will continue, until morale improves" - the Management |
From: Dieter B. <da...@bl...> - 2008-03-26 15:48:44
|
Hi, I do a backup with duplicity, which works good with davfs2-1.2.1, but it doesn't work with davfs2 from actual cvs. my strace says something like this, when I use the actual cvs version: --snipp-- 1625 write(7, "\205\2\16\3\207,\301\311\210\333\222\262\20\7\377V\10\377n4(#\372\222\263\335Z$F\303\357\347"..., 65536) = -1 EIO (Input/output error) 1625 write(2, "IOError", 7) = 7 --snipp-- I can't find any debug option, is there any way to debug was going wrong here ? my config is: --snip-- kernel_fs fuse secrets /etc/davfs2/secrets use_locks 1 use_expect100 0 cache_size 50 file_refresh 300 --snip-- mount options: --snip-- conf=/etc/davfs2/davfs2.conf,rw,noauto 0 0 --snip-- -- best regards Dieter -- I do not get viruses because I do not use MS software. If you use Outlook then please do not put my email address in your address-book so that WHEN you get a virus it won't use my address in the From field. |
From: Werner B. <wer...@on...> - 2008-03-11 12:35:53
|
Hello Julius, Julius wrote: > Hi, > > my user is memeber of the group davfs2, but mount tells me that i have > to be root to mount. How do you enable this? > > mount -t davfs http://ipadress/dir /home/myuser/somewhere > > -rwxr-xr-x 1 root root 125K Mar 8 20:32 /usr/sbin/mount.davfs > > im using davfs-1.3. > - mount.davfs must have the setuid-bit set: as root: chmod u+s /usr/sbin/mount.davfs So it will look like -rwsr-xr-x 1 root root 125K Mar 8 20:32 /usr/sbin/mount.davfs - for non-root-users to mount, there must be an entry in /etc/fstab, like http://ipadress/dir /home/myuser/somewhere davfs user,noauto 0 0 Cheers Werner |
From: Julius <com...@gm...> - 2008-03-11 10:15:53
|
Hi, my user is memeber of the group davfs2, but mount tells me that i have to be root to mount. How do you enable this? mount -t davfs http://ipadress/dir /home/myuser/somewhere -rwxr-xr-x 1 root root 125K Mar 8 20:32 /usr/sbin/mount.davfs im using davfs-1.3. Julius. |
From: Werner B. <wer...@on...> - 2008-02-26 13:21:30
|
Hello Sebastian, I believe, I found the reason for the problems. Looks like an error in davfs2. I only tested "servercert" with self-signed server-certs, and it works. But your server-certificate is *not* self-signed. It is signed by the Server CA, and the certificate of the Server CA is signed by the Root CA. The certificate of the Root CA is self-signed. In this case neon seems to *not* want the server-certificate, but the CA-certificate. I only tested this with one CA, which directly signed the server cert. When I give the CA-certificate to davfs2 it works. In your case, I do not know, whether neon needs the certificate of the Server CA, or the self-signed certificate of the Root CA. I hope, both works. Please test both cases: - servercert <path to Server-CA-cert> and alternatively - servercert <path to Root-CA-cert> (not both at the same time). Please report the results. If it works, I will have to change the entry in the davfs2.conf-manual, and probably also change the name of the configuration option (servercert would be misleading). To see, why your index-file is corrupted, I must know, how davfs2 stops, i.e. the log file should go to the very end ("Done.") Cheers Werner |
From: Werner B. <wer...@on...> - 2008-02-25 21:20:21
|
Hello Sebastian, rather confusing: Sebastian Reitenbach wrote: > mount /webdav > /sbin/mount.davfs: the server certificate is not trusted > issuer: Office IT, My Company AG, Berlin, Berlin, DE > subject: Office IT, My Company AG, Berlin, Berlin, DE > identity: host.my-company.de > fingerprint: c4:61:80:dd:d5:d9:65:dc:9d:8e:ff:37:b6:21:16:96:1e:83:54:d2 > You only should accept this certificate, if you can > verify the fingerprint! The server might be faked > or there might be a man-in-the-middle-attack. > Accept certificate for this session? [y,N] > > mount /webdav > /sbin/mount.davfs: the server certificate is not trusted > issuer: Office IT, RapidEye AG, Brandenburg, Brandenburg, DE > subject: Office IT, RapidEye AG, Brandenburg, Brandenburg, DE > identity: ogo.rapideye.de > fingerprint: c4:61:80:dd:d5:d9:65:dc:9d:8e:ff:37:b6:21:16:96:1e:83:54:d2 > You only should accept this certificate, if you can > verify the fingerprint! The server might be faked > or there might be a man-in-the-middle-attack. > Accept certificate for this session? [y,N] > Different certificates with the same fingerprint? And still another version in davfs2/certs/ ? You did not append the logs. I am only interested in the *full* log. An exact copy of the certificate from the exact location you specified in davfs2.conf could be useful too. But maybe you first want to make sure that there is only one certificate, and the server and davfs2 use this one and only certificate, and have exactly identical copies of it. Cheers Werner |
From: Sebastian R. <seb...@l0...> - 2008-02-24 22:06:50
|
Hi Werner, Werner Baumann <wer...@on...> wrote: > Hello Sebastian, > > Sebastian Reitenbach wrote: > >> Are you sure, davfs2 can read the locally stored server certificate? > >> If yes: Please send the exact error message and any related entries in > >> the log file. > > yes, thats why I mentioned that I chmod it to 600, then mount.davfs2 errored > > out because of permission denied to read this certificate. Therer is no > > special error message, > Please don't tell me whether the error message is special or not. Just > "Please send the exact error message and any related entries in > the log file." > This is bug reporting basics. And its frustrating and time consuming, > when users don't want to tell the error messages. > Please note: I have written these messages, so I might be able to draw > some conclusions from them, if I only knew. sorry for my ignorance, here is the output when I mount the webdav drive: mount /webdav /sbin/mount.davfs: the server certificate is not trusted issuer: Office IT, My Company AG, Berlin, Berlin, DE subject: Office IT, My Company AG, Berlin, Berlin, DE identity: host.my-company.de fingerprint: c4:61:80:dd:d5:d9:65:dc:9d:8e:ff:37:b6:21:16:96:1e:83:54:d2 You only should accept this certificate, if you can verify the fingerprint! The server might be faked or there might be a man-in-the-middle-attack. Accept certificate for this session? [y,N] > > > > It's just like if I haven't specified a server > > certificate at all. > Probably you have not? Please consult the man page (davfs2.conf) and > check your config-file and the place where you stored the certificate. after running with "debug most" it printed out the configuration, where it pointed to the correct certificate. > > > > Where do I need to take a look for a logfile? > > > I would have to know what version of davfs2 you use. You did not tell me > (bug reporting basics again). If your version is 1.2.2 or 1.3.0, put the > lines I use 1.3.0, neon 0.28. > > debug most > debug ssl I just ran mount with these debug options, the whole log file output is a bit long, so I extracted the most interesting pieces I think. The full log is also available. > > into your config file. The debug messages will go into one of the log > files of your operating system (/var/log/syslog, debug.log, daemon.log > or messages, depending on your OS-version). And please: Read that fine > manuals. I don't understand, why reading my emails would be more fun > than reading my manuals. found them in the messages > > > > The certificate file contains first the output of openssl x509 -noout -text > > of the certificate, then followed by the actual certificate in pem format > > --- begin certificate --- > > ... > > > > or however it looks like, maybe the text before the actual certificate makes > > some problems? I'll remove the text and try again. > > > If this causes trouble, there would most probably be an error message. > As the certificate is parsed by the neon library, I am not 100% sure > about this. I removed the text part, but still no difference. > > Once you have enabled debug messages, it might be possible, to see from > this messages, what is going on at start up and why it takes that long. below the essence from the messages when mounting, see the comment, where it takes the loooong time. mount /webdav /sbin/mount.davfs: the server certificate is not trusted issuer: Office IT, RapidEye AG, Brandenburg, Brandenburg, DE subject: Office IT, RapidEye AG, Brandenburg, Brandenburg, DE identity: ogo.rapideye.de fingerprint: c4:61:80:dd:d5:d9:65:dc:9d:8e:ff:37:b6:21:16:96:1e:83:54:d2 You only should accept this certificate, if you can verify the fingerprint! The server might be faked or there might be a man-in-the-middle-attack. Accept certificate for this session? [y,N] kind regards Sebastian |