We have proprietary security solution for the Qualcomm linux which we enable on opensourced meta-qcom by providing the required binaries compiled on downstream.
Now I am trying to add sepolicies for our solution through a .pp file, generated by adding our policies as a patch on top of refpolicy while building the meta-qcom layer. This policy file is required to be packed as part of an rpm package to enable our sepolicies and published to the open source dev-community. Could you please provide the guidance on which license obligations will fall for us to use this approach for adding the sepolicies through the .pp file?
We have proprietary security solution for the Qualcomm linux which we enable on opensourced meta-qcom by providing the required binaries compiled on downstream.
Now I am trying to add sepolicies for our solution through a .pp file, generated by adding our policies as a patch on top of refpolicy while building the meta-qcom layer. This policy file is required to be packed as part of an rpm package to enable our sepolicies and published to the open source dev-community. Could you please provide the guidance on which license obligations will fall for us to use this approach for adding the sepolicies through the .pp file?