canonical-partner-dev team mailing list archive

[dardhal <883839@xxxxxxxxxxxxxxxxxx>]

Thank God I found this comment / bug report from Roger James, as it has
saved me from getting even angrier at this problem than I already was. I
can fully confirm the bug with Ubuntu 11.10 32 bit and Acrobat Reader
9.4.2, and the fix that the reporter has detailled in the comment above.

This is not only a severe functionality bug, but a very simple one to fix as well from the comment above. Without the fix or the workaround lots of online paperwork simply don't work, as many site SSL certificates are not signed by the typical commercial root CA, so following Acrobat instructions and running commands like the one below, doesn't make a difference:
acroread -installCertificate www-s.munimadrid.es 443

In fact, under the user's application directory the file with the cert
gets created, but as long as you don't workaround the cert file by hand,
it doesn't make the connection work. I went to the pain of dumping the
connection data via Wireshark, and the TLSv1 session is dropped by the
client end (Acrobat Reader) sending the other end a "unknow CA
certificate" message.

So it seemed clear the problem was somewhere in Acrobat, and thank God
Roger had already "fixed" it.

Please commit a fix for this issue to the package, as not everyone is
going to be able to workaround it, as like it or not, Adobe Acrobat is
the de-facto standard (and maybe the only one PDF reader) witch
capabilities to be used for things like attaching files to PDF
documents, digitally signing  them, and securely send them to an enabled
server.

-- 
You received this bug notification because you are a member of Canonical
Partner Developers, which is subscribed to acroread in Ubuntu.
https://bugs.launchpad.net/bugs/883839

Title:
  Wrong file names generated by acroread -installCertificate

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/acroread/+bug/883839/+subscriptions