Issue #363 new


created an issue

We already have LuaSocket, so why not add support for SSL-protected networking as well?

Comments (18)

  1. Boolsheet

    The OpenSSL dependency is pretty heavy in its file size. Maybe it's possible to strip it down to just the things LuaSec needs. Then again, compiling OpenSSL has to be a very interesting adventure.

  2. Anonymous

    OpenSSL dependency is a nightmare on windows. Basically you have to run a separate installer on the client before the thing will work. It's killing a non-löve related project at my workplace.

  3. kikito


    I think the cost of adding and maintaining that dependency on all systems does not justify the benefits - the usage of SSL in games is too niche; maybe 5 or 6 people in total would need it.

    Now, if someone other than the core devs did support this on the 3 main systems, I would not have a problem.

  4. Kyle Conroy

    Thomas R. Koll The only way is to setup an HTTP to HTTPS proxy. I'm planning on doing this via Heroku.

    +1 I would really like to be able to make HTTPS requests. I've wanted to use both the GitHub API and the Sentry API from my game, but both require HTTPS.

  5. josefnpat

    I would like to have https as well. Perhaps we could just add a ./configure flag that isn't enabled by default, and distribute the binaries on the side?

    That way "normal" developers can just use the nice small binary, and win/mac developers use a love-https binary. (linux users can just make it a dependency via luarocks?)

  6. David Serrano

    I think something like luasec would be cool and is defitnally a good addition but maybe make it optional somehow. That way only the ones who use it can suffer from the extra weight.

  7. josefnpat

    To put this issue in perspective, would it make sense to add libcurl to the framework, or should this workaround be documented on the wiki, and the ticket marked as wontfix?

  8. Log in to comment