Shantanu Singh

> > @jonesmz Not sure if they'd be accepting of that change so easily. They'd make the argument of updating `boost/asio` to add support for GnuTLS _natively_ instead of leveraging...

> > I guess that beast doesn't need to care about TLS because it is hidden underlying layer from the beast. > > I was wrong. Due to very complected...

> @shantanu1singh , could you try #673 ? > > As I commented at [#663 (comment)](https://github.com/redboltz/mqtt_cpp/pull/663#issuecomment-703384855), GnuTLS support is implemented by boost asio and boost beast, not mqtt_cpp. > So...

@redboltz I haven't had the chance to test it yet. Will likely get to it today or tomorrow. I'll keep you posted here.

@redboltz I tried out #673 but it failed with an error. I've pointed out what needs to be changed in your PR. If you can help update that, I can...

This is the error just as a reference: ``` /home/shantanu/repos/mqtt_cpp_1/include/mqtt/endpoint.hpp: In member function ‘bool mqtt::endpoint::handle_close_or_error(mqtt::error_code)’: /home/shantanu/repos/mqtt_cpp_1/include/mqtt/endpoint.hpp:4567:17: error: there are no arguments to ‘ERR_GET_REASON’ that depend on a template parameter, so...

Thanks @jonesmz I'm currently occupied with work. Will send a PR once I have something ready.

ah, I see. Interesting, thanks for the link. I'll take a look