QtCS25 - Qt & Cybersecurity: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
(→Notes) |
||
| Line 9: | Line 9: | ||
==Notes== | ==Notes== | ||
Qt security score markers in files | |||
One conclusion: mark all files in library code, but not examples or tests, even if insignificant | |||
Tooling could scan the markers, to warn on creation on new files, without the marker (perhaps from Bots) | |||
Benefit: it's easier to have it in files, than in abandoned gerrit changes, because its close to the files, and abandoned changes are hard to fine | |||
[[Category:QtCS2025]] | [[Category:QtCS2025]] | ||
Revision as of 14:20, 8 May 2025
Session Summary
Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum.
Session Owners
Lorem Ipsum
Consetetur Sadipscing
Notes
Qt security score markers in files
One conclusion: mark all files in library code, but not examples or tests, even if insignificant
Tooling could scan the markers, to warn on creation on new files, without the marker (perhaps from Bots)
Benefit: it's easier to have it in files, than in abandoned gerrit changes, because its close to the files, and abandoned changes are hard to fine