>> How do I generate the required CRT and KEY - File for localhost which shall >> work on every other client's localhost.
Or asked in a different way: The qwebsocketserver - example: https://code.qt.io/cgit/qt/qtwebsockets.git/tree/examples/websockets/sslechoserver?h=5.15 already has the CERT- and KEY files included. Should it be possible to run this example server on my localhost and any other machine's localhost without the need to generate new certificates ? -- http://www.carot.de Email : alexan...@carot.de Tel.: +49 (0)177 5719797 > Gesendet: Dienstag, 21. Juli 2020 um 10:07 Uhr > Von: "Alexander Carôt" <alexander_ca...@gmx.net> > An: "Thiago Macieira" <thiago.macie...@intel.com> > Cc: interest@qt-project.org > Betreff: Re: [Interest] wss:// on localhost > > > I don't see how that affects anything. Are you saying you can't update the > > application? If you can't update the application, how are you going to > > apply > > the fixes we're discussing here? > > > Misunderstanding :-) Of course I apply application updates in more or less > regular intervals of several weeks. > > > > If you meant that they aren't able to generate the certificate, let me > > clarify > > that I meant the application should do that automatically. > > > That was the misunderstanding - I thought you wanted each user to generate it > manually. > > > > There needs to be > > no user interaction. The certificate is just something that the WebSocket > > client and server agree upon before start, like the port number. I > > mentioned > > "every few months" just so you don't incur the penalty of the generation on > > every start. > > > So far I assumed that it is impossible to generate a localhost certificate > which runs on any other machine's localhost as well and it brings me to the > next question: > > > How do I generate the required CRT and KEY - File for localhost which shall > work on every other client's localhost. > > Sorry if the solution might be trivial - I am simply completely unexperienced > in terms of securiry :-) > > Thanks a lot again in advance > > Alex > > > -- > http://www.carot.de > Email : alexan...@carot.de > Tel.: +49 (0)177 5719797 > > > > Gesendet: Montag, 20. Juli 2020 um 16:40 Uhr > > Von: "Thiago Macieira" <thiago.macie...@intel.com> > > An: interest@qt-project.org > > Betreff: Re: [Interest] wss:// on localhost > > > > On Monday, 20 July 2020 01:57:31 PDT Alexander Carôt wrote: > > > The problem is that my application currently has a daily pageview of > > > > 1000 > > > and a user base of more than 10.000 - most of the user are non-tech-sage > > > so > > > I need the most simply solution. > > > > I don't see how that affects anything. Are you saying you can't update the > > application? If you can't update the application, how are you going to > > apply > > the fixes we're discussing here? > > > > If you meant that they aren't able to generate the certificate, let me > > clarify > > that I meant the application should do that automatically. There needs to > > be > > no user interaction. The certificate is just something that the WebSocket > > client and server agree upon before start, like the port number. I > > mentioned > > "every few months" just so you don't incur the penalty of the generation on > > every start. > > > > -- > > Thiago Macieira - thiago.macieira (AT) intel.com > > Software Architect - Intel System Software Products > > > > > > > > _______________________________________________ > > Interest mailing list > > Interest@qt-project.org > > https://lists.qt-project.org/listinfo/interest > > > _______________________________________________ > Interest mailing list > Interest@qt-project.org > https://lists.qt-project.org/listinfo/interest > _______________________________________________ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
