HTTPS, SSL

[0x00]

Hello community, time to time I think anyone who want work with network data with oauth2 or something else (I mean all what works on HTTPS protocol) faced with not-friendly interfaces. So SFML do you have any plans on this? Because C++ standart have no solutions to work from scratch with network (SSL) (only in C++20 some remarks). Any others solutions like boost or poco is to fat for using)

[Laurent]

HTTPS (and other stuff relying on secured sockets, such as SFTP) is a complex thing, and relies on third-party libraries such as OpenSSL. If someone wants to provide an implementation, why not, but that's not our priority.

[0x00]

HTTPS (and other stuff relying on secured sockets, such as SFTP) is a complex thing, and relies on third-party libraries such as OpenSSL. If someone wants to provide an implementation, why not, but that's not our priority.

So if I correctly understood, anyone who want SSL implementation needs to do cross-platform classes and make pull request on github, is it a correct thought?

In latest time more and more sites migrate to HTTPS and some things are not available.

[eXpl0it3r]

The first step would be to discuss the planned changes, especially the choice of TLS third-party library, here on the forum.

[Rosme]

Depending on how to approach this, Windows and Apple has their own implementation that SFML could possibly use, leaving Linux to use something else like OpenSSL or BoringSSL. Or we could wrap around the same library for all platforms.

[korczurekk]

I'd wrap one library (preferably OpenSSL) on any OS, it would minimize platform-dependent code and be way shorter.

[Tank]

Wrapping one library isn't a good idea when it comes to security patches — Heartbleed anyone? If the underlying operating system provides own SSL APIs, I'd definitely suggest using those.