Files
alknet/tasks/auth/client-auth-handler.md
glm-5.1 5c820a41e9 tasks: decompose Phase 0a ADR foundation and mark prior tasks completed
Add 10 new tasks under tasks/architecture/ for Phase 0a (ADR writing):
- 9 ADR tasks (026-034) with dependency-ordered structure
- 1 review checkpoint task before Phase 0b spec writing

ADR dependency graph (3 generations):
  Gen 1 (parallel): 026, 029, 030, 031, 032, 034
  Gen 2 (depends on 029): 027, 028
  Gen 3 (depends on 027+028): 033
  Gen 4: review checkpoint

Also mark all 34 prior implementation tasks as completed — they
were finished but still showing as pending in the taskgraph.
2026-06-07 08:55:33 +00:00

40 lines
1.5 KiB
Markdown

---
id: auth/client-auth-handler
name: Implement client-side SSH authentication with Ed25519 key pairs
status: completed
depends_on:
- auth/key-loading
- auth/error-types
scope: narrow
risk: low
impact: component
level: implementation
---
## Description
Implement the client-side SSH authentication. The client presents an Ed25519 private key during SSH handshake. This creates the `russh::client::Handler` implementation and the `russh::client::ConnectStreamConfig` that uses the loaded key.
No password auth. The client handler is simpler than the server — it just needs to provide the private key and handle the auth callback from russh.
## Acceptance Criteria
- [ ] `crates/alknet-core/src/auth/client_auth.rs` exports `ClientAuthConfig` and client handler
- [ ] `ClientAuthConfig` holds: `private_key: KeyPair`, optional `public_key: PublicKey`
- [ ] `ClientAuthConfig::from_key_source(source: KeySource) -> Result<Self>` — loads key via key-loading module
- [ ] Implements `russh::client::Handler` with `auth_publickey()` returning the public key
- [ ] Client handler returns `russh::client::AuthResult::Accept` or appropriate auth state
- [ ] Unit tests: valid key creates handler, auth flow succeeds with mock SSH session
## References
- docs/architecture/client.md — "Authentication is Ed25519 public key or OpenSSH certificate (ADR-012)"
- docs/architecture/decisions/012-auth-ed25519-and-cert-authority.md — key-based auth only
## Notes
> To be filled by implementation agent
## Summary
> To be filled on completion