qt/qtremoteobjects.git - Qt distributed object system

	Commit message (Collapse)	Author	Age	Files	Lines
*	Mark QtRemoteObjects as security critical	Øystein Heskestad	2025-07-04	1	-0/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	The QtRemoteObjects serialization is built on top of QDataStream, but QDataStream is not secure. Mark all files parsing data as security critical. The security is dependent on the backend used. The local and QNX backends communicate only locally but are insecure on a compromised host. The TCP backend is by default insecure, but it supports TLS, and can be secure if that is used. The two files in the repparser directory are used for parsing, but only at build time, and are therefore kept at security significant. The remaining files are marked as security signifcant. QUIP: 23 Task-number: QTBUG-135570 Pick-to: 6.10 6.9 6.8 Change-Id: I11176c036d95f8c706bd05e1cab1ba499003f683 Reviewed-by: Edward Welbourne <edward.welbourne@qt.io>
*	Expose (private) API for creating QtRO types	Brett Stottlemyer	2025-01-07	1	-0/+216
	The intent is to better support Python bindings. This adds RepParser to the main source of RemoteObjects, where before the parsing of .rep files into code had been independent of the RemoteObjects source. We need to know about the AST output from the parser to generate the dynamic classes. We add qremoteobjectrepparser_p.h (and a corresponding c++ file) with the APIs to generate QMetaObjects dynamically and register the types we can dynamically. The structs used for dynamic enum/gadget/class types were moved to a new header file so they could be shared with Node's dynamic parsing as well as the newly added API. [ChangeLog] Add external/private interface to support bindings (specifically Python) to generate dynamic classes from .rep files. Pick-to: 6.9 Change-Id: Id5bef60ae7c6e178ed9b2f8391224d05eda54662 Reviewed-by: Michael Brasser <michael.brasser@live.com>