Files
mtusi2026lab4/evidence/attachments/storage.md
T
ricoromaandClaude Opus 5.5 8dc925e8ca docs: add attachments evidence and report
- re-capture coverage-exclusion evidence on the lab 4 stand: cache,
  auth storage, replay after API recreate, test-persistence,
  attachment-failover (stop, kill), attachment-storage
- green evidence/tests: student_test via LB, test_isolated,
  failure_checks; smoke, slow transfer, test-failover per replica
- bench_rollout label attachments: e1161f7 -> schema with attachments
  under load, no errors, messages = keys
- REPORT.md: attachments architecture, write order, defense answers,
  level 3/4 evidence rows, limitations; PLAN.md stage 2

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-21 01:50:10 +03:00

6.1 KiB
Raw Blame History

Где лежат вложения: метаданные в PostgreSQL, байты в приватном bucket

  • Дата: 2026-10-20, 22:32:55–22:33:20 UTC.
  • Commit: d56b892 (код приложения — 116d8d3, change attachments).
  • Стенд: рабочий mtusi-lab4 — HAProxy на 127.0.0.1:8080, две реплики API, PostgreSQL, Valkey, S3 (SeaweedFS, bucket messenger, API S3 на хосте только 127.0.0.1:S3_OUT_PORT).
  • Исключение сверки покрытия attachments «Байты не в БД и не на диске API» (student-tests/spec_coverage.py); пункты 2 и 4 сценария защиты; design change attachments, решения 3, 4, 13.

Команда driver.py attachment-storage загружает tests/fixtures/sample.png дважды через LB (с именем storage-check-<случайное>-<n>.png) и проверяет, без печати токенов и секретов:

  • колонки таблиц вложений (psql): из bytea — только sha256 ровно 32 байта, колонки с байтами изображения нет;
  • object_key каждой загрузки — <база>/attachments/<id>/original, без filename;
  • объект с этим ключом есть в bucket, размер совпадает (weed shell fs.ls -l в контейнере s3);
  • анонимный GET ключа с хоста — 403;
  • участник скачивает тот же SHA-256;
  • docker diff каждой реплики — файлов оригиналов нет.

Проверка

$ python3 .claude/skills/run-mtusi-messenger/driver.py --port 8080 attachment-storage
columns of attachment tables:
  attachments  id  uuid
  attachments  chat_id  uuid
  attachments  owner_id  uuid
  attachments  filename  text
  attachments  content_type  text
  attachments  size_bytes  integer
  attachments  sha256  bytea
  attachments  object_key  text
  attachments  status  text
  attachments  updated_at  timestamp with time zone
  attachments  created_at  timestamp with time zone
  message_attachments  message_id  uuid
  message_attachments  position  smallint
  message_attachments  attachment_id  uuid
  message_attachments  created_at  timestamp with time zone
upload via 5f5d4ac50d9a: object_key messenger/attachments/5e3a529e-abb2-49e1-a461-8334c7ba0eae/original
  sha256 uploaded 99ea7533c441f79cd630d15ce4d58d1ec4e06f6f0efb3b77a5c088305cd1bd75, downloaded by a member (200) 99ea7533c441f79cd630d15ce4d58d1ec4e06f6f0efb3b77a5c088305cd1bd75
upload via 847ad74efd7c: object_key messenger/attachments/6afac582-4256-4ca0-8ae1-10aef5de8705/original
  sha256 uploaded 99ea7533c441f79cd630d15ce4d58d1ec4e06f6f0efb3b77a5c088305cd1bd75, downloaded by a member (200) 99ea7533c441f79cd630d15ce4d58d1ec4e06f6f0efb3b77a5c088305cd1bd75
docker diff 5f5d4ac50d9a: 2 changes
  C /app
  A /app/config.toml
docker diff 847ad74efd7c: 2 changes
  C /app
  A /app/config.toml
bytea columns                  expected sha256  got sha256
octet_length(sha256)           expected 32  got 32
object_key form                expected messenger/attachments/5e3a529e-abb2-49e1-a461-8334c7ba0eae/original  got messenger/attachments/5e3a529e-abb2-49e1-a461-8334c7ba0eae/original
filename not in key            expected no  got no
object in bucket, bytes        expected 111817  got 111817
anonymous GET of the key       expected 403  got 403
downloaded sha256 = uploaded   expected yes  got yes
object_key form                expected messenger/attachments/6afac582-4256-4ca0-8ae1-10aef5de8705/original  got messenger/attachments/6afac582-4256-4ca0-8ae1-10aef5de8705/original
filename not in key            expected no  got no
object in bucket, bytes        expected 111817  got 111817
anonymous GET of the key       expected 403  got 403
downloaded sha256 = uploaded   expected yes  got yes
original files in 5f5d4ac50d9a expected 0  got 0
original files in 847ad74efd7c expected 0  got 0
sha256 of the fixture: 99ea7533c441f79cd630d15ce4d58d1ec4e06f6f0efb3b77a5c088305cd1bd75
PASS: metadata in PostgreSQL, bytes only in the private bucket messenger, none in the API containers
exit=0
  • Загрузки приняли обе реплики; у каждого вложения свой объект, ключ назначил сервер по имени базы и id.
  • docker diff реплик — только смонтированный config.toml: оригиналы на диск API не пишутся (тело живёт в памяти процесса до PUT).

Отрицательная проверка: bucket открыт анониму

Анонимное чтение bucket открыто руками через weed shell (как ошибка оператора), затем повторный bootstrap его закрывает.

$ printf 's3.anonymous.set -bucket messenger -access Read\n' | docker compose exec -T s3 sh -c "exec weed shell -master=127.0.0.1:9333 2>&1"
Set anonymous access on bucket "messenger" to: Read
$ python3 .claude/skills/run-mtusi-messenger/driver.py --port 8080 attachment-storage | grep -E "anonymous|FAIL|PASS"
anonymous GET of the key       expected 403  got 200  FAIL
anonymous GET of the key       expected 403  got 200  FAIL
FAIL: 2 check(s) failed
exit=1
$ docker compose up -d s3-bootstrap
$ docker compose logs --no-log-prefix s3-bootstrap | tail -3
s3-bootstrap: anonymous access to messenger closed
s3-bootstrap: user api exists
s3-bootstrap: checks passed (api key put/get/delete; api key list and bucket create, anonymous get and list denied)
$ python3 .claude/skills/run-mtusi-messenger/driver.py --port 8080 attachment-storage | grep -E "anonymous|FAIL|PASS"
anonymous GET of the key       expected 403  got 403
anonymous GET of the key       expected 403  got 403
PASS: metadata in PostgreSQL, bytes only in the private bucket messenger, none in the API containers
exit=0

Команда замечает открытый bucket (код 1 и названная проверка), а штатный bootstrap возвращает приватность.