Repository navigation
docs: mark dstack-auth as development, testing and evaluation only - #1576
Merged
Merged
Conversation
dstack-auth takes its policy from a file on the host, so whoever controls the host can authorize any compose hash and obtain app keys, and nobody else can audit what was authorized. That does not meet the trust model production deployments rely on; point production users at auth-eth or an equivalent service instead. Signed-off-by: Kevin Wang <wy721@qq.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
dstack-auth reads its policy from a file on the host, so the host operator can authorize any compose hash and obtain app keys, and third parties cannot audit what was authorized. Mark it as development, testing and evaluation only across the docs and
--help, and stop listing it as a production policy backend.