DongHyeonkaandClaude Opus 5
b2963105a8
The keycloak project ended with four open questions that design could not
settle. A two-VM lab was built to answer them by measurement, and this is
that material: 26 experiments, 125 raw command outputs, 22 browser captures.
Follows the import procedure in README.md.
source/ the originating repository verbatim — 78 documents, 28 SVGs,
8 manifests, plus .source-revision recording the commit
final/ the SSOT
document.md 729 lines written from the 29 experiment documents, not
concatenated: what was predicted, what was measured, and
where the measurement itself was wrong
evidence/raw 125 outputs, flattened to <experiment>__<file> because
the originals collided (01-baseline.txt appeared three
times) and the audit only globs the top level
evidence/meta one per raw file; command and exitCode are null and the
README says why rather than inventing them
evidence/browser 22 captures
assets/ three diagrams through techviz
.techviz/ their VizSpecs
A separate project rather than an addition to keycloak: the B-layer answers
that project's four questions, but the A, C and D layers are about cluster
failure, SSO and operations, and one document.md should hold one subject.
The four question records there can point here through 관계.
Recorded rather than papered over: only three of the 28 diagrams were
remade. The repository forbids hand-drawn SVG and forbids titles inside the
canvas; all 28 originals carry both, so converting them is redrawing, not
reformatting. They stay in source/ and the gap is written into the document.
verify-pipeline.py passes. audit-records.py reports no issues.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
50 lines
2.3 KiB
Markdown
50 lines
2.3 KiB
Markdown
---
|
|
kind: CONCEPT
|
|
slug: grpc-advanced-diagnostics-c01
|
|
title: Channelz는 유용해서 위험한 표면이다
|
|
topic: security-and-trust-boundaries
|
|
project: clean-architecture-backend-template
|
|
status: 게시 전
|
|
sourceRevision: 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916
|
|
rootTreeNode: concept:grpc-advanced-diagnostics-c01
|
|
evidenceCapturedOn: 2026-09-01
|
|
assets:
|
|
- key: grpc-advanced-diagnostics-c01
|
|
file: ../../../final/evidence/rendered/grpc-advanced-diagnostics-c01.svg
|
|
- key: grpc-advanced-diagnostics-c01-diagram
|
|
file: ../../../final/assets/diagrams/grpc-advanced-diagnostics-c01.svg
|
|
evidence:
|
|
- ../../../final/evidence/raw/grpc-advanced-diagnostics-c01.txt
|
|
source:
|
|
- 원본 분석 절은 analysis/grpc/grpc-advanced-diagnostics.md#L41 이다.
|
|
module: grpc-advanced-diagnostics
|
|
---
|
|
|
|
# Channelz는 유용해서 위험한 표면이다
|
|
|
|
이 리프는 진단 표면(Channelz·CSDS)과 그것을 게시 가능하게 만드는 편집기, 그리고 고급 능력의 검증 대상을 이름 짓는 테스트킷 계약을 담는다. 편집기가 필요한 이유가 편집기 자신의 javadoc에 적혀 있다.
|
|
|
|
## 본문
|
|
|
|
<!-- body:start -->
|
|
|
|
진단 표면(Channelz·CSDS)과 그것을 게시 가능하게 만드는 편집기, 그리고 고급 능력이 무엇을 상대로 검증되어야 하는지를 이름 짓는 테스트킷 계약을 담는다.
|
|
|
|
## 이 리프가 담는 것
|
|
|
|
:::evidence key="grpc-advanced-diagnostics-c01-diagram" alt="리프 경계 안에 진단 표면과 편집기와 테스트킷 계약 세 상자가 나란히 들어 있는 구조" caption="이 리프가 담는 것" zoom="false"
|
|
:::
|
|
|
|
## 편집기가 필요한 이유
|
|
|
|
편집기 javadoc 이 왜 이것이 필요한지 적는다.
|
|
|
|
> "Channelz is unusually dangerous to expose because it is genuinely useful: it holds every socket's local and remote address, the security details of each connection, and per-call state… once the endpoint exists the whole of it is one authorization mistake away from being readable."
|
|
|
|
## 이 기록이 다루는 파일 범위
|
|
|
|
:::evidence key="grpc-advanced-diagnostics-c01" alt="코드베이스에서 파일 목록을 만든 출력 4줄. 이 기록이 다루는 범위가 그 목록이다." caption="코드베이스 파일 목록 — 4줄 · exit 0" zoom="true"
|
|
:::
|
|
|
|
<!-- body:end -->
|