raphw commented on PR #191:
URL: https://github.com/apache/maven-resolver/pull/191#issuecomment-1253730059

   As a user, you do not normally have control over the state of your/the build 
server's local repository. A build server might share some mounted folder with 
many nodes to reduce traffic, especially in cloud environments this night be 
implemented to avoid additional traffic. If other builds do not validate the 
checksums and my build will neither as a consequence, then the principal that 
any used artifact can be validated based on locally available information is 
broken. I could still emulate this by using a setting with a fresh repository 
location, but ideally I would want to treat the repository as an untrusted, 
remote server, just like a remote repository, only with the convenience that 
the artifacts are already downloaded.
   
   For this reason I was hoping for an option to evaluate this. If not by 
default, maybe by setting a system property, as allowing for a zero trust 
approach is quite handy. Maybe this system property could also allow for 
generating these checksum files.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to