1,870
edits
Changes
Jump to navigation
Jump to search
Line 17:
Line 17: + + + + + + + + + + + + + + + +
How to set up a secure webdav area on an Apache 2.0 server that can hold an Adobe Acrobat 8 shared review document (view source)
Revision as of 15:46, 28 August 2007
, 15:46, 28 August 2007→Problem 2: Adobe Reader 8 on the Mac will not connect to my webdav server over ssl
Because fellow authors rarely have client certificates that I know I can rely on, it is easier to use http basic authentication anyway, so I never tried to get client certs to work with Acrobat shared reviews. Maybe some day when pki technology becomes widespread in the scientific community, it will make sense to revisit the question.
Because fellow authors rarely have client certificates that I know I can rely on, it is easier to use http basic authentication anyway, so I never tried to get client certs to work with Acrobat shared reviews. Maybe some day when pki technology becomes widespread in the scientific community, it will make sense to revisit the question.
== Problem 2: Adobe Reader 8 on the Mac will not connect to my webdav server over ssl ==
This problem I have not yet managed to solve. Adobe Reader on Windows works fine with the exact same shared review. I spent quite a bit of time on it, trying to make it work on the Mac. I tried importing the complete chain of signer certificates directly into the cert store maintained by Adobe Reader itself, but still no success. The ssl key exchange fails during the connection process. The Apache server log shows the following entry.
<pre>
[Sun Aug 26 10:42:27 2007] [info] Connection to child 7
established (server gryphn.phys.uconn.edu:443, client
68.118.192.252)
[Sun Aug 26 10:42:27 2007] [info] Seeding PRNG with 136 bytes
of entropy
[Sun Aug 26 10:42:27 2007] [error] SSL handshake failed
(server gryphn.phys.uconn.edu:443, client 68.118.192.252)
[Sun Aug 26 10:42:27 2007] [error] SSL Library Error:
336151576 error:14094418:SSL routines:func(148):reason(1048)
</pre>
The error reason 1048 seems to indicate a problem validating the signature on the host server certificate. That is why I worked on getting Adobe Reader to recognize my signers as legitimate signing authorities. It seemed to make no difference. For now, I must resign myself to not using shared reviews because too many of my colleagues use the Mac. So far, no one out on the message boards seems to have run into this problem. When someone solves it, I will post the answer here.