sbp commented on issue #564: URL: https://github.com/apache/tooling-trusted-releases/issues/564#issuecomment-3774633551
When I ran this on my usual development instance, after removing my SSH key to ensure that it's regenerated, the permissions were fine and the explicit check did not do anything. This confused me because I checked the `asyncssh` code just to be sure of what was happening, and could not find that it sets a umask or applies permissions. Running this in a fresh container, I see that the new explicit check is changing the permissions, so `asyncssh` is not applying the required permissions there and this may have been the reason for the original issue, except that `rm -rf state` is said to have fixed it. This may deserve further investigation, but the committed check should be sufficient. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
