🛡️ Sentinel: [security improvement] 동적으로 중요 파일 제외하여 정보 노출 방지

[seonghobae]

🚨 Severity: MEDIUM
💡 Vulnerability: 디렉토리 인덱서가 .pem, .key 등 민감 파일의 기본 제외 규칙을 정적 목록에만 의존하여 정보 노출을 야기할 수 있음
🎯 Impact: 생성된 HTML이 호스팅될 경우 인증서 키 및 중요 데이터베이스 파일이 대중에 노출될 위험이 있음
🔧 Fix: process_ignore_file 에 .endsWith 검사를 추가하여 중요 확장자 파일을 동적으로 무시하도록 로직 수정
✅ Verification: ./gradlew test 로 관련 파일이 정상적으로 포함되지 않는지 검증 완료

---

PR created automatically by Jules for task 7086760838869163864 started by @seonghobae

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[opencode-agent]

Pull request overview

OpenCode cannot approve yet because required coverage evidence did not pass.

Review outcome

1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence

• Problem: The required coverage-evidence job result was failure, so OpenCode cannot establish approval sufficiency for this head.

• Root cause: Automated approval is only valid when the same-head coverage-evidence job proves supported repository test suites passed and configured docstring gates passed or were advisory, or reports not applicable because no supported source files or package manifests exist. Missing, failed, skipped, unavailable, or unsupported-tooling test evidence is a blocker.

• Fix: Install or configure the repository test/docstring evidence tooling when source files or package manifests exist, rerun the current-head coverage-evidence job, and approve only after it reports success with required evidence or explicit no-source not-applicable evidence.

• Regression test: Keep the approval branch checking needs.coverage-evidence.result == success before posting APPROVE, and publish REQUEST_CHANGES when coverage-evidence blocker states such as cancelled, skipped, failed, unsupported-tooling, or below-100 evidence are present.

• Result: REQUEST_CHANGES

• Reason: coverage-evidence result was failure, so required test/docstring evidence was not proven for current head 515d3814015990d4e3ce77392f1604deb60f776d.

• Head SHA: 515d3814015990d4e3ce77392f1604deb60f776d

• Workflow run: 30424187591

• Workflow attempt: 1

Coverage evidence

Coverage evidence job did not run or did not publish coverage evidence.

Changed-File Evidence Map

flowchart LR
PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
Evidence --> S1["Changed file (3 files)"]
S1 --> I1["repository behavior"]
I1 --> R1["Review risk: Changed file (3 files)"]
R1 --> V1["required checks"]

Loading

[opencode-agent]

OpenCode Review Overview

• Head SHA: 515d3814015990d4e3ce77392f1604deb60f776d
• Workflow run: 30424187591
• Workflow attempt: 1
• Gate result: REQUEST_CHANGES (approval step)

Pull request overview

OpenCode cannot approve yet because required coverage evidence did not pass.

Review outcome

1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence

• Problem: The required coverage-evidence job result was failure, so OpenCode cannot establish approval sufficiency for this head.

• Root cause: Automated approval is only valid when the same-head coverage-evidence job proves supported repository test suites passed and configured docstring gates passed or were advisory, or reports not applicable because no supported source files or package manifests exist. Missing, failed, skipped, unavailable, or unsupported-tooling test evidence is a blocker.

• Fix: Install or configure the repository test/docstring evidence tooling when source files or package manifests exist, rerun the current-head coverage-evidence job, and approve only after it reports success with required evidence or explicit no-source not-applicable evidence.

• Regression test: Keep the approval branch checking needs.coverage-evidence.result == success before posting APPROVE, and publish REQUEST_CHANGES when coverage-evidence blocker states such as cancelled, skipped, failed, unsupported-tooling, or below-100 evidence are present.

• Result: REQUEST_CHANGES

• Reason: coverage-evidence result was failure, so required test/docstring evidence was not proven for current head 515d3814015990d4e3ce77392f1604deb60f776d.

• Head SHA: 515d3814015990d4e3ce77392f1604deb60f776d

• Workflow run: 30424187591

• Workflow attempt: 1

Coverage evidence

Coverage evidence job did not run or did not publish coverage evidence.

Changed-File Evidence Map

flowchart LR
PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
Evidence --> S1["Changed file (3 files)"]
S1 --> I1["repository behavior"]
I1 --> R1["Review risk: Changed file (3 files)"]
R1 --> V1["required checks"]

Loading

[seonghobae]

Closing this older branch as superseded by #206, which preserves the same extension-based exclusion proposal in a narrower one-commit canonical lane and covers a strict superset of the extensions tested here.

Fresh exact comparison: this head 515d3814015990d4e3ce77392f1604deb60f776d changes .jules/sentinel.md, main.kt, and MainTest.kt to exclude .pem, .key, .sqlite, and .db; #206 head 5aef1cdfc3287a69d7e93995f97b0771fde341b7 changes the same three paths and includes those four plus additional proposed suffixes. No check, review, or security claim is transferred. #206 remains independently unmergeable and still requires product-policy review of broad suffix blocking, current-base reconstruction, exact-head tests/security, and current approval.

[google-labs-jules]

Closing this older branch as superseded by #206, which preserves the same extension-based exclusion proposal in a narrower one-commit canonical lane and covers a strict superset of the extensions tested here.

Fresh exact comparison: this head 515d3814015990d4e3ce77392f1604deb60f776d changes .jules/sentinel.md, main.kt, and MainTest.kt to exclude .pem, .key, .sqlite, and .db; #206 head 5aef1cdfc3287a69d7e93995f97b0771fde341b7 changes the same three paths and includes those four plus additional proposed suffixes. No check, review, or security claim is transferred. #206 remains independently unmergeable and still requires product-policy review of broad suffix blocking, current-base reconstruction, exact-head tests/security, and current approval.

Understood. Acknowledging that this work is now obsolete and superseded by #206, and stopping work on this task.