-
Notifications
You must be signed in to change notification settings - Fork 0
Build/CD 과정에서의 버그 수정 #5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
The head ref may contain hidden characters: "build/cd-\uACFC\uC815-\uBC84\uADF8-\uD574\uACB0"
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(1) 문제점: Secret 파일의 권한을 0444(모든 사용자에게 읽기 권한)로 변경하는 것은 보안 위험이 있습니다. 동일한 노드에서 실행되는 다른 파드나 프로세스가 해당 secret 파일을 읽을 수 있게 됩니다.
(2) 영향: 컨테이너 내의 모든 사용자(다른 그룹 포함)가
/etc/keys경로의 secret 파일을 읽을 수 있어, 권한이 없는 프로세스나 악의적인 코드가 민감한 정보에 접근할 수 있습니다.(3) 수정 제안: 원래 설정인 0400(소유자만 읽기 가능) 또는 0440(소유자와 그룹만 읽기 가능)을 유지하세요. 만약 애플리케이션이 secret 파일을 읽지 못하는 문제가 있다면, 컨테이너의 runAsUser/runAsGroup을 적절히 설정하거나, fsGroup을 사용하여 파일 소유권을 조정하는 것이 더 안전합니다.