[Interest] wss:// on localhost

[Jason H]

IANAL, and this dives into legal issues, but if the creature function took a path to a binary, and some options (assuming openssl options?) and allow the developer/user to specify the binary, I think the legal issues would be avoided. If the user wanted to use some other mechanism, they would just provide a script as the binary and map the openssl options to the custom binary.

Just my 0.02.


> Sent: Wednesday, July 29, 2020 at 5:08 PM
> From: "Thiago Macieira" <thiago.macieira at intel.com>
> To: interest at qt-project.org
> Subject: Re: [Interest] wss:// on localhost
>
> On Wednesday, 29 July 2020 07:46:36 PDT Jason H wrote:
> > Kinda sounds like there should be a QSslCertificate::create() method?
>
> Yes, but we may not be able to have that in Qt without running into export
> controls. Qt cryptographic code is only approved for sockets.
>
> --
> Thiago Macieira - thiago.macieira (AT) intel.com
>   Software Architect - Intel DPG Cloud Engineering
>
>
>
> _______________________________________________
> Interest mailing list
> Interest at qt-project.org
> https://lists.qt-project.org/listinfo/interest
>