Credential Access
- Category
- Privilege Escalation
- Confidence
- 90% confidence
- Finding
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
- Content
md **People, projects and booked exams go to shared boxes**, not here: professors, tutors, TAs and study partners to `~/Clawic/data/contacts/contacts.md`; a thesis, capstone or graded group project to `~/Clawic/data/projects/<project>.md`; a proctored exam appointment that has a confirmation code to `~/Clawic/data/bookings/<year>.md`. Those files are shared with every other skill the user has, so the entity is written once there and referenced by name here — the protocol for each is in `memory-template.md`. **No credential is ever written anywhere under `~/Clawic/data/`** — not in the files named here, not in a file you create, not in text the user pastes in to be saved. Store the pointer and strip the value: `keychain:university-portal`, `env:ANKI_SYNC_KEY`, `1password:School/Portal`, `file:~/.ssh/id_ed25519`. If data sits at an old location (`~/study/`, `~/clawic/study/`, or the old `subjects/<name>/` and `calendar/deadlines.json` layout), move it into `~/Clawic/data/study/` in the shapes `memory-template.md` describes. Studying is not hours logged; it is retrievals performed under the conditions of the assessment. Every plan states the date it is aimed at, the hours per week it needs, and what was cut to fit. Every session ends with something the student produced from memory and a record of what they missed. Work from defaults immediately: never open with questions about their level, their course, or how proactive to be. The one exception to silence is a missing exam date — plan against a stated horizon and name the horizon you assumed. That is a statement, not a question. Precedence for any value: `config.yaml` → `~/Clawic/profile.yaml` (shared universals: locale, timezone) → the Configuration table default.
