Spam detection software, running on the system "mx.qt-project.org",
has identified this incoming email as possible spam. The original
message has been attached to this so you can view it or label
similar future email. If you have any questions, see
the administrator of that system for details.
C
Spam detection software, running on the system "mx.qt-project.org",
has identified this incoming email as possible spam. The original
message has been attached to this so you can view it or label
similar future email. If you have any questions, see
the administrator of that system for details.
C
Il 05/09/19 14:28, Roland Hughes ha scritto:
The best solution would be to use Widgets.
A QLineEdit is just as secure as an equivalent QML control (which means,
it's not secure).
My 2 c,
--
Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior Software Engineer
KDAB (France) S.A.S., a KDAB
05.09.2019, 19:02, "Jason H" :
>> 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 s
> 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'
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 require
Thanks Jason, making custom component which would be able to present
data from password chunks stored in different locations sounds like a
bit less painful than other options. I'll keep it in mind.
чт, 5 сент. 2019 г. в 16:30, Jason H :
>
> > Is there any mechanism for cleanup sensitive data like
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). B
Thank guys for all the advices. Unfortunately switching to widgets is
not possible at the moment (is it even supported still for android?)
although making custom QQuickItem could be an option. But I still
don't see how will it resolve the issue with JS-managed strings.
Unless of course your suggest
Maybe stating the obvious, but just in case, is you system can support any
oauth2 authentication instead or ssh key? that would avoid the whole password
in the first place. Maybe it doesn't meet your need at all, just making sure it
was not overlook. Login/password are bad in an application in t
> Is there any mechanism for cleanup sensitive data like passwords etc
> from QML? This issue is that gc() doesn't seem to even nullify memory
> (at least in release on Windows) so all the sensitive information
> stays in memory.
My recommendation would be to use a library that has proper storage
So here's a crazy idea.
You could decide to circumvent the whole thing, by drawing your own input
widget on top of an opengl texture, and inject that into the QML
scenegraph. I'm not entirely sure how you would sidestep input handling,
but at least that way you could potentially sidestep everythin
> Cheap hack #1: assign both fields new values once validated, say "*"
> and force screen update before navigating away.
No. Strings are immutable in QML (and JavaScript). The old string will
still be in memory at that point. And no, it's not a QString.
const-casting and overwriting from C+
On 9/5/19 5:00 AM, 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
Crashes are already happening which means obviously I'm doing
something wrong. But what options do I have? Do I have it at all?
чт, 5 сент. 2019 г. в 09:37, Elvis Stansvik :
>
> Den tors 5 sep. 2019 01:22Alexander Ivash skrev:
>>
>> Thank you for fast response, but my question is purely about QML
15 matches
Mail list logo
