> Irrespective to any other detail in this thread: this is, by definition, > not secure (sec by obscurity).
Completely right but my point is that my current use case actually does not require any security at all. I am really not interested in trivializing security at all, however, in feel like dealing with significant disproportionate issues. Of course this is a result of the security concept but I also think it's worth discussing conceptual problems resulting in the actual thread. I am afraid this might take a little longer ;-) Best Alex -- http://www.carot.de Email : alexan...@carot.de Tel.: +49 (0)177 5719797 > Gesendet: Sonntag, 02. August 2020 um 21:06 Uhr > Von: "Giuseppe D'Angelo via Interest" <interest@qt-project.org> > An: interest@qt-project.org > Betreff: Re: [Interest] wss:// on localhost > > Il 02/08/20 20:43, Alexander Carôt ha scritto: > > Also I don't see a way to get access to the key - it is compiled into the > > binary and on top of it it's triple-secured/encypted > > Irrespective to any other detail in this thread: this is, by definition, > not secure (sec by obscurity). > > My 2 c, > -- > Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior Software Engineer > KDAB (France) S.A.S., a KDAB Group company > Tel. France +33 (0)4 90 84 08 53, http://www.kdab.com > KDAB - The Qt, C++ and OpenGL Experts > > _______________________________________________ > 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
