> Yes! And they have graciously given us an SSL certificate. We are very pleased by that :)

Who-da thunk it :).

Configuring ssl can be tricky, especially getting it right. I'de love to help if you have any problems. We use sslcheck.x509labs.com internally to make sure everything is working correctly. It even has step-by-step instructions on how to fix some problems.

> On the other side: cabal, at least, uses the HTTP package, and I've been (slowly) working on adding SSL support.

Oh lovely! I can not find your work through the github repos, but I'd love to take a look and see if I can help.

On Sat, Nov 2, 2013 at 12:58 PM, Jason Dagit <dagitj@gmail.com> wrote:

On Sat, Nov 2, 2013 at 12:25 PM, Eli Frey <eli.lee.frey@gmail.com> wrote:

Hello all,

It recently came to my attention that hackage is http only. I would love to do anything I can to help hackage support https. What is the process for volunteering with the IHG (I imagine this is the avenue for helping with hackage/haskell.org).

If the IHG is having dificulty getting an SSL certificate, GlobalSign (ful disclosure, they are my employer) provides free certificates to FOSS projects.

Yes! And they have graciously given us an SSL certificate. We are very pleased by that :)

Having an SSL certificate is a recent thing for us and the infrastructure team is currently busy wrapping up other tasks. We do have folks assigned to putting the cert in place and configuring everything, they just need a bit more time :) (More volunteers would help too, but that's longer term.)

I am also concerned that cabal does not have support for SSL, but hackage must come first and at least then a sufficiently paranoid person can download their packages over https and ad them to their cabal sandboxes.

Yes, this is the next part to tackle.

Jason