On 11/25/20 2:48 PM, Theo Buehler wrote:
> On Wed, Nov 25, 2020 at 02:19:38PM -0500, Aisha Tammy wrote:
>> On 11/25/20 2:01 PM, Theo Buehler wrote:
>>> On Wed, Nov 25, 2020 at 01:12:03PM -0500, Aisha Tammy wrote:
On 11/25/20 12:34 PM, Stuart Henderson wrote:
> On 2020/11/25 12:03, Aisha
On 11/25/20 2:01 PM, Theo Buehler wrote:
> On Wed, Nov 25, 2020 at 01:12:03PM -0500, Aisha Tammy wrote:
>> On 11/25/20 12:34 PM, Stuart Henderson wrote:
>>> On 2020/11/25 12:03, Aisha Tammy wrote:
Hi,
It has come to my attention that upstream does not support
libressl and only
On 11/25/20 12:34 PM, Stuart Henderson wrote:
> On 2020/11/25 12:03, Aisha Tammy wrote:
>> Hi,
>> It has come to my attention that upstream does not support
>> libressl and only wants to support openssl
>> https://github.com/uNetworking/uWebSockets/issues/994
>>
>> I am unsure on how to fix this
On 2020/11/25 14:19, Aisha Tammy wrote:
> On a side side note: While this consumer is correctly working now,
> the upstreams horrible statement still does exist...
> Do we want/need to link it to OpenSSL instead?
Not if it works.
Since the only thing using usockets/uwebsockets in ports at the
On Wed, Nov 25, 2020 at 02:19:38PM -0500, Aisha Tammy wrote:
> On 11/25/20 2:01 PM, Theo Buehler wrote:
> > On Wed, Nov 25, 2020 at 01:12:03PM -0500, Aisha Tammy wrote:
> >> On 11/25/20 12:34 PM, Stuart Henderson wrote:
> >>> On 2020/11/25 12:03, Aisha Tammy wrote:
> Hi,
> It has come
On Wed, Nov 25, 2020 at 01:12:03PM -0500, Aisha Tammy wrote:
> On 11/25/20 12:34 PM, Stuart Henderson wrote:
> > On 2020/11/25 12:03, Aisha Tammy wrote:
> >> Hi,
> >> It has come to my attention that upstream does not support
> >> libressl and only wants to support openssl
> >>
On 2020/11/25 12:03, Aisha Tammy wrote:
> Hi,
> It has come to my attention that upstream does not support
> libressl and only wants to support openssl
> https://github.com/uNetworking/uWebSockets/issues/994
>
> I am unsure on how to fix this port.
> There is no problem right now as the only
