-
Notifications
You must be signed in to change notification settings - Fork 346
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade process and v1.2.2 pre release #23
Comments
I have this issue as well and tried getting around it by putting this in my gemfile: you can see the effect of doing this by running this worked fine locally on my mac, but i get this error when running on cloud66 linux box i'm hacking around this by doing a |
@richardwan you need to install
|
Bundling from the master branch of this repo rather than the official Gem build seems to have fixed an issue with a PDF with images from Amazon S3 over SSL were not rendering. Due to a silent SSL failure with the older 0.9.9.3 build of wkhtmltopdf. |
0.12.3 has been merged in PR #31 |
The currently bundled version of wkhtmltopdf is v1.2.1. Since last week a lot of web hosts have disabled SSLv3 because of the POODLE attack.
wkhtmltopdf v1.2.1 (and earlier) still use SSLv3 by default. This has been changed in the current testing release (v1.2.2.testing).
I was having a look to create a patch with the updated (testing) binaries so we could use this pre version in our app right now (since we rely on assets deliverd over https with SSLv3 disabled). Is there any good way to update the bundled binaries? It seems that the osx one can be extracted from the pkg, but I have no idea how to do that for the linux binaries. One option is to start a vagrant box for each required release and extract the binary from there but would that be enough? It would be nice if there was some more information on how to udpate the binaries.
The text was updated successfully, but these errors were encountered: