I love the idea of Let’s Encrypt, but I recently bought a three year wildcard cert subscription for about $120. I would need to fall firmly into the true believer category to go the route you suggest.
Cary > On Jan 14, 2016, at 11:20 AM, Eric Hellman <e...@hellman.net> wrote: > > A while back, the issue of needing a wildcard certificate (not supported by > Lets Encrypt) for EZProxy was discussed. > > In my discussions with publishers about switching to HTTPS, EZProxy > compatibility has been the most frequently mentioned stumbling block > preventing a complete switch to HTTPS for some HTTPS-ready publishers. In > two cases that I know of, a publisher which has been HTTPS-only was asked by > a library customer to provide insecure service (oh the horror!) for this > reason. > > It's been pointed out to me that while Lets Encrypt is not supporting > wildcard certificates, up to 100 hostnames can be supported on a single LE > certificate. A further limit on certificates issued per week per domain would > mean that up to 500 hostnames can be registered with LE in a week. > > Are there EZProxy instances out there that need more than 500 hostnames, > assuming that all services are switched to HTTPS? > > Also, I blogged my experience talking to people about privacy at #ALAMW16. > http://go-to-hellman.blogspot.com/2016/01/not-using-https-on-your-website-is-like.html > > <http://go-to-hellman.blogspot.com/2016/01/not-using-https-on-your-website-is-like.html> > > Eric > > > Eric Hellman > President, Free Ebook Foundation > Founder, Unglue.it https://unglue.it/ > https://go-to-hellman.blogspot.com/ > twitter: @gluejar >