> On 4 Nov 2024, at 12:39, Volker Hilsheimer via Development
> wrote:
>> On 19 Aug 2024, at 14:12, Dimitrios Apostolou via Development
>> wrote:
>>
>> Reminder that this QUIP is still open for feedback:
>>
>> https://codereview.qt-project.org/c/meta/quips/+/575276
>>
>> Concerns have been ad
> On 19 Aug 2024, at 14:12, Dimitrios Apostolou via Development
> wrote:
>
> Reminder that this QUIP is still open for feedback:
>
> https://codereview.qt-project.org/c/meta/quips/+/575276
>
> Concerns have been addressed and further feedback is welcome here or on
> codereview.
>
> Regards
Reminder that this QUIP is still open for feedback:
https://codereview.qt-project.org/c/meta/quips/+/575276
Concerns have been addressed and further feedback is welcome here or on
codereview.
Regards,
Dimitris
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.or
> On 11 Jul 2024, at 15:51, Giuseppe D'Angelo wrote:
>
> On 11/07/2024 15:21, Volker Hilsheimer wrote:
>> For many APIs, application code provides the data (perhaps indirectly),
>> e.g. to QDateTime::fromString. In that case we can assume that the
>> application had at least some chance to scru
On 11/07/2024 15:21, Volker Hilsheimer wrote:
For many APIs, application code provides the data (perhaps indirectly),
e.g. to QDateTime::fromString. In that case we can assume that the
application had at least some chance to scrub the input, or at the very
least control where that string comes fr
> On 11 Jul 2024, at 13:26, Giuseppe D'Angelo via Development
> wrote:
>
> On 10/07/2024 19:08, Kai Köhne via Development wrote:
>> That's a lot of questions. But a lot comes down to: Can we agree on parts of
>> Qt that are more critical and, therefore, should be subject to additional
>> secur
Giuseppe
D'Angelo via Development
Date: Thursday, 11. July 2024 at 14.30
To: development@qt-project.org
Subject: Re: [Development] Proposing QUIP-23: Qt-Security header in source code
files
On 10/07/2024 19:08, Kai Köhne via Development wrote:
> That's a lot of questions. But a lot
On 10/07/2024 19:08, Kai Köhne via Development wrote:
That's a lot of questions. But a lot comes down to: Can we agree on
parts of Qt that are more critical and, therefore, should be subject to
additional security (in terms of approvers, coding standards, fuzzing
...)? And can we then document
Hi,
Let me add a bit of a bigger picture here.
I think we all share the goal of making the Qt Framework and tools as
high-quality and robust as possible. We've also been continuously investing in
this, be it on the technical side or on the process side. But the world is
changing, and the expec
