Disclaimer: I've never used pytorch and I also know nothing about software security practices.
But I don't see a scenario where pytorch needs network access. It seems wrong that at any level within the codebase I can import any module and use its API.
I think there need to be additional import restrictions or static analysis.
This also seems like languages do not have the right abstractions to talk about this stuff. As a comparison, I like how in rust I can look at the function signature and see the mutability and lifetimes of everything without understanding any of the code underneath.
I feel there needs to be something similar here with dependencies. A dev should be able to audit all their dependencies easily and see "oh dep X uses eval()" or network access, etc without looking at any underlying code.
Mobile apps enforce permissions. Shouldn't a dev be able to whitelist certain functionality and not take everything including the kitchen sink.
But I don't see a scenario where pytorch needs network access. It seems wrong that at any level within the codebase I can import any module and use its API.
I think there need to be additional import restrictions or static analysis.
This also seems like languages do not have the right abstractions to talk about this stuff. As a comparison, I like how in rust I can look at the function signature and see the mutability and lifetimes of everything without understanding any of the code underneath.
I feel there needs to be something similar here with dependencies. A dev should be able to audit all their dependencies easily and see "oh dep X uses eval()" or network access, etc without looking at any underlying code.
Mobile apps enforce permissions. Shouldn't a dev be able to whitelist certain functionality and not take everything including the kitchen sink.