At the beginning this was for my own personal use as I was in need of some sort of encryption for a work project without using openssl, then I just released the code for the class on github, it's more a code exercise than a real usable class for the issues you pointed out.
On Wed, Jul 12, 2017 at 4:43 AM, Marc Mutz <marc.m...@kdab.com> wrote: > On 2017-07-12 00:05, Matteo wrote: > [...] > >> My point was not to use openssl or external libs, i understand the >> security issue of something that is not certified and audited. >> > [...] > > Good to know. Now you "just" need to make sure *all* your potential users > understand this, too. Which brings me to the question: who, exactly, is the > target audience for a non-proven, non-audited, non-certified, AES-only, > Qt-using implementation? > > Thanks, > Marc > > -- Matteo
_______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
