[Interest] QML and sensitive data

Alexander Ivash elderorb at gmail.com
Thu Sep 5 17:28:57 CEST 2019

I understand this, but this is not an issue. Let say it is allowed to
have sensitive information in memory when particular QML screen (used
for showing/editing this information) is opened. But, information
should be fully eliminated from memory dump (cleaning up leftovers in
GPU is also not required at the moment) on closing this screen -
that's what I'm trying to achieve.

чт, 5 сент. 2019 г. в 18:25, Thiago Macieira <thiago.macieira at intel.com>:
> On Wednesday, 4 September 2019 16:20:44 PDT Alexander Ivash wrote:
> > Thank you for fast response, but my question is purely about QML. On
> > C++ side I have a lot of ways for nullifying / erasing sensitive
> > information *after* it is not needed (let say after particular QML
> > screen gets' closed). But on QML / JS side I have no any control at
> > all. Would be great if one of QML guys could step in and comment too.
> As I said, the moment you want to display a string, it's no longer considered
> secure. This has nothing to do with QML.
> The string will be used for text shaping, the pixels will be drawn in a
> pixmap, said pixmap will be shared with the compositor, which then by some
> means uploads it to the GPU.
> --
> Thiago Macieira - thiago.macieira (AT) intel.com
>   Software Architect - Intel System Software Products
> _______________________________________________
> Interest mailing list
> Interest at qt-project.org
> https://lists.qt-project.org/listinfo/interest

More information about the Interest mailing list