changes config file to specify TSLv1 SSL protocol after POODLE vuln

@jusx @brightbytes-dude 

https://trello.com/c/gKIASGHW/2125-case-reports-not-downloading-error-generating-pdf

This is what's required to fix the PDF generation error. PhantomJS uses SSLv3 protocol by default, but now that's been disabled after the POODLE vulnerability was uncovered. Until PhantomJS comes out with their new release version to change the default protocol to TLSv1, we have to specify it as a config option.

Once the fix is verified and this is merged, we can take the last prod release branch, run `bundle update shrimp` locally, and do a hot deploy.
LMAO - sounds about right.  Woof!!!!!

On Tue, Oct 21, 2014 at 10:14 AM, Erik Lyngved <notifications@github.com>
wrote:

> In lib/shrimp/config.json:
>
> > @@ -3,5 +3,6 @@
> >      "ignoreSslErrors": false,
> >      "loadImages": true,
> >      "outputEncoding": "utf8",
> > -    "webSecurity": true
> > +    "webSecurity": true,
> > +    "sslProtocol": "tlsv1"
>
> Damn little poodles, they are so cute and then they shit under the couch
> and you spend hours and hours wondering where the smell is coming from.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/brightbytes/shrimp/pull/1/files#r19162867>.
>