sbp commented on issue #34: URL: https://github.com/apache/tooling-releases-client/issues/34#issuecomment-4925548392
Our security model to begin with in the server was that we simply don't store secret data other than PATs (and even those are hashed at least), so that we don't have to worry about what turns up in stack traces. As long as we're careful about PATs, nothing can turn up in a stack trace that we need to worry about. Very recently, however, we added support for expedited releases (https://github.com/apache/tooling-trusted-releases/issues/962) which we consider secret. This was difficult to lock down, and now changes the profile on this. We might have to reconsider and move towards opaque stack traces. I think we've paid a really heavy price for this feature, despite my intense efforts to minimise the complexity and security risks. -- 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]
