Skip to main content

otp-challenger

Enable agents and skills to challenge users for fresh two-factor authentication proof (TOTP or YubiKey) before executing sensitive actions. Use this for identity verification in approval workflows - deploy commands, financial operations, data access, admin operations, and change control.

소스 정보

저장소
Kernel8901/ai-agent-skills-classification
최근 소스 활동
2026년 4월 4일 15:26
감지된 SKILL.md 언어
영어
스타
6
포크
1

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

파일 탐색기
18 개 파일

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
name
otp-challenger
version
1.0.3
description
Enable agents and skills to challenge users for fresh two-factor authentication proof (TOTP or YubiKey) before executing sensitive actions. Use this for identity verification in approval workflows - deploy commands, financial operations, data access, admin operations, and change control.
metadata
{"openclaw":{"emoji":"🔐","homepage":"https://github.com/ryancnelson/otp-challenger","requires":{"bins":"[Truncated]","anyBins":"[Truncated]"},"install":["[Truncated]","[Truncated]","[Truncated]"]}}
# OTP Identity Challenge Skill Challenge users for fresh two-factor authentication before sensitive actions. ## When to Use Require OTP verification before: - Deploy commands (`kubectl apply`, `terraform apply`) - Financial operations (transfers, payment approvals) - Data access (PII exports, customer data) - Admin operations (user modifications, permission changes) ## Scripts ### verify.sh Verify a user's OTP code and record verification state. ```bash ./verify.sh <user_id> <code> ``` **Parameters:** - `user_id` - Identifier for the user (e.g., email, username) - `code` - Either 6-digit TOTP or 44-character YubiKey OTP **Exit codes:** - `0` - Verification successful - `1` - Invalid code or rate limited - `2` - Configuration error (missing secret, invalid format) **Output on success:** ``` ✅ OTP verified for <user_id> (valid for 24 hours) ✅ YubiKey verified for <user_id> (valid for 24 hours) ``` **Output on failure:** ``` ❌ Invalid OTP code ❌ Too many attempts. Try again in X minutes. ❌ Invalid code format. Expected 6-digit TOTP or 44-character YubiKey OTP. ``` ### check-status.sh Check if a user's verification is still valid. ```bash ./check-status.sh <user_id> ``` **Exit codes:** - `0` - User has valid (non-expired) verification - `1` - User not verified or verification expired **Output:** ``` ✅ Valid for 23 more hours ⚠️ Expired 2 hours ago ❌ Never verified ``` ### generate-secret.sh Generate a new TOTP secret with QR code (requires `qrencode` to be installed). ```bash ./generate-secret.sh <account_name> ``` ## Usage Pattern ```bash #!/bin/bash source ../otp/verify.sh if ! verify_otp "$USER_ID" "$OTP_CODE"; then echo "🔒 This action requires OTP verification" exit 1 fi # Proceed with sensitive action ``` ## Configuration **Required for TOTP:** - `OTP_SECRET` - Base32 TOTP secret **Required for YubiKey:** - `YUBIKEY_CLIENT_ID` - Yubico API client ID - `YUBIKEY_SECRET_KEY` - Yubico API secret key (base64) **Optional:** - `OTP_INTERVAL_HOURS` - Verification expiry (default: 24) - `OTP_MAX_FAILURES` - Failed attempts before rate limiting (default: 3) - `OTP_STATE_FILE` - State file path (default: `memory/otp-state.json`) Configuration can be set via environment variables or in `~/.openclaw/config.yaml`: ```yaml security: otp: secret: "BASE32_SECRET" yubikey: clientId: "12345" secretKey: "base64secret" ``` ## Code Format Detection The script auto-detects code type: - **6 digits** (`123456`) → TOTP validation - **44 ModHex characters** (`cccccc...`) → YubiKey validation ModHex alphabet: `cbdefghijklnrtuv` ## State File Verification state stored in `memory/otp-state.json`. Contains only timestamps, no secrets. ## Human Documentation See **[README.md](./README.md)** for: - Installation instructions - Setup guides (TOTP and YubiKey) - Security considerations - Troubleshooting - Examples
GitHub에서 보기