New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Default 'nothing allowed' state for ServiceComputePrivacy #90
Comments
|
As far as i know this was intended, empty |
|
ComputePrivacy is going to look like this: where: Having allowRawAlgorithm == false && allowAllPublishedAlgorithms == false -> only trusted algos can be started. Default values on publishing:
|
if the pod has no network access how does it fetch the data? |
|
data is fetched by pod-configuration, before algo pod is created. |
At the moment, whenever a new compute data set is published all published algorithms are allowed to run on it by default, which seems unintended. This is because in the background there are some unexpected interpretations of non-existing or empty array value for
publisherTrustedAlgorithms.To make this more clear and explicit, we could have something like
allowAllAlgorithmswithinServiceComputePrivacy, set tofalseby default upon data set publish, as suggested in oceanprotocol/market#417 (comment)The text was updated successfully, but these errors were encountered: