On Tue, Sep 09, 2025 at 05:57:13PM +0100, Daniel P. Berrangé wrote: > This introduces two new flags "secure" and "insecure" against > the Type struct, and helpers to check this against the ObjectClass > struct. > > An object type can be considered secure if it is either marked > 'secure', or is not marked 'insecure'. The gives an incremental > path where the security status is undefined for most types, but > with the possibility to require explicitly secure types, or > exclude explicitly insecure types.
Should there be a check in code that nothing tries to set both flags simultaneously? -- Eric Blake, Principal Software Engineer Red Hat, Inc. Virtualization: qemu.org | libguestfs.org
