一键在 Manus 中运行任何 Skill

add-eap-method

星标672

分支298

更新时间2026年6月8日 07:55

Add an EAP authentication method (e.g. EAP-TLS) within the existing EAP handler system (TR-F004). Use when the change involves EAP handshake, fragmentation, state management, or failure semantics.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

talkincode

talkincode/toughradius

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Skill: Add an EAP Authentication Method

Feature ID: TR-F004 | Milestone: M1 (EAP-TLS)

When to use

When adding a new EAP method (e.g. EAP-TLS) within the existing EAP system.

Pre-research

view internal/radiusd/plugins/eap/coordinator.go         # coordinator, do NOT rewrite
view internal/radiusd/plugins/eap/interfaces.go          # handler interface
file_search "internal/radiusd/plugins/eap/handlers/*_handler.go"
view internal/radiusd/plugins/eap/statemanager/          # EAP state management
grep_search "EapMethod" --include internal/app/**         # enabled-list config

Existing references: md5_handler.go, mschapv2_handler.go, otp_handler.go.

Protocol specs & reference implementations

International standards (read repo-local docs/rfcs/ first):

rfc3748-eap.txt - EAP framework
rfc5216-eap-tls.txt - EAP-TLS (handshake, fragmentation, identity)
rfc3579-radius-eap-support.txt - RADIUS carrying EAP (EAP-Message / Message-Authenticator)
rfc5247-eap-key-management.txt - EAP key management
rfc7499-packet-fragmentation.txt - RADIUS fragmentation
Others: rfc5281-eap-ttls.txt, rfc7170-teap.txt (if extending tunneled methods)

Backfill missing specs per ../reference-rfc/SKILL.md.

Reference implementations (for ideas only; mind licensing and protocol compatibility, do not copy incompatible code):

BeryJu radius-eap: https://github.com/BeryJu/radius-eap
Implementation notes: https://beryju.io/blog/2025-05-implementing-eap/

Implementation steps

Handler skeleton: implement the handler interface at internal/radiusd/plugins/eap/handlers/<method>_handler.go (mirror mschapv2).
State management: reuse statemanager; correlate multi-round handshakes / fragmentation (TLS) via the EAP State, and do not add branches inside the coordinator.
Registration: wire into the coordinator and the enabled list (EapMethod config) the same way existing handlers do.
Failure semantics: return an explicit reason on failure, convert it to AuthError, and emit metrics (reference internal/radiusd/errors and radius_metrics.go).
Config schema: if new config is needed (e.g. certificate paths), see ../add-config-schema/SKILL.md.

Boundaries

Do not rewrite the EAP coordinator (coordinator.go).
For EAP-TLS, deliver a minimal working auth path first; certificate revocation / policy come in later milestones.
eap-otp currently uses a fixed sample OTP; do not copy its fixed value when implementing a real method.

Acceptance

Handler unit tests + end-to-end auth tests pass
Failure cases have explicit reject reasons and metrics
go test ./internal/radiusd/... and golangci-lint run pass
An end-to-end acceptance test is added under test/integration/ (see ../add-acceptance-test/SKILL.md), executed by CI
PR references TR-F004 and the M1 subtask ID, and cites the RFC clauses relied upon

同仓库更多 Skills

同仓库

release-version

talkincode/toughradius

Review merged PRs since the last Git tag and decide whether a ToughRADIUS release is warranted. Use when Codex is asked to prepare a version release, audit unreleased changes, decide whether to publish, create a new release tag, or tag origin/main after PR review.

2026-07-08672

orchestrate-roadmap

talkincode/toughradius

Global orchestrator / dispatcher role. Activated when the user issues an "auto-delegate development / continue the roadmap / auto-delegate" command (without naming a specific subtask); runs the full loop - select task, pick SOP, dispatch, quality gates, open PR, self-iterate the roadmap.

2026-06-11672

review-pr

talkincode/toughradius

Independent review gate for auto-delegation PRs (TR-F022). Use after an orchestration round opens a PR, and as the first step of every new round to clear in-flight PRs - run an adversarial, CI-anchored review, request changes via labels + comments, and auto-merge only when the review passes and CI is green.

2026-06-11672

document-go-apis

talkincode/toughradius

Standard-library-style Go API documentation and comment conventions (TR-F024). Use when adding or changing exported Go identifiers, writing package comments, or backfilling godoc on a package so it reads like the Go standard library.

2026-06-09672

add-acceptance-test

talkincode/toughradius

Write CI-executable acceptance/integration tests for protocol or end-to-end changes (TR-F022). Use whenever a milestone subtask needs CI-backed acceptance, covering test/integration integration tests and unit tests.

2026-06-08672

add-adminapi-endpoint

talkincode/toughradius

Add a group of Admin REST endpoints in the management backend (TR-F012). Use when a feature needs management APIs such as create/read/update/delete.

2026-06-08672

name	add-eap-method
description	Add an EAP authentication method (e.g. EAP-TLS) within the existing EAP handler system (TR-F004). Use when the change involves EAP handshake, fragmentation, state management, or failure semantics.

Skill: Add an EAP Authentication Method

Feature ID: TR-F004 | Milestone: M1 (EAP-TLS)

When to use

When adding a new EAP method (e.g. EAP-TLS) within the existing EAP system.

Pre-research

view internal/radiusd/plugins/eap/coordinator.go         # coordinator, do NOT rewrite
view internal/radiusd/plugins/eap/interfaces.go          # handler interface
file_search "internal/radiusd/plugins/eap/handlers/*_handler.go"
view internal/radiusd/plugins/eap/statemanager/          # EAP state management
grep_search "EapMethod" --include internal/app/**         # enabled-list config

Existing references: md5_handler.go, mschapv2_handler.go, otp_handler.go.

Protocol specs & reference implementations

International standards (read repo-local docs/rfcs/ first):

rfc3748-eap.txt - EAP framework
rfc5216-eap-tls.txt - EAP-TLS (handshake, fragmentation, identity)
rfc3579-radius-eap-support.txt - RADIUS carrying EAP (EAP-Message / Message-Authenticator)
rfc5247-eap-key-management.txt - EAP key management
rfc7499-packet-fragmentation.txt - RADIUS fragmentation
Others: rfc5281-eap-ttls.txt, rfc7170-teap.txt (if extending tunneled methods)

Backfill missing specs per ../reference-rfc/SKILL.md.

Reference implementations (for ideas only; mind licensing and protocol compatibility, do not copy incompatible code):

BeryJu radius-eap: https://github.com/BeryJu/radius-eap
Implementation notes: https://beryju.io/blog/2025-05-implementing-eap/

Implementation steps

Handler skeleton: implement the handler interface at internal/radiusd/plugins/eap/handlers/<method>_handler.go (mirror mschapv2).
State management: reuse statemanager; correlate multi-round handshakes / fragmentation (TLS) via the EAP State, and do not add branches inside the coordinator.
Registration: wire into the coordinator and the enabled list (EapMethod config) the same way existing handlers do.
Failure semantics: return an explicit reason on failure, convert it to AuthError, and emit metrics (reference internal/radiusd/errors and radius_metrics.go).
Config schema: if new config is needed (e.g. certificate paths), see ../add-config-schema/SKILL.md.

Boundaries

Do not rewrite the EAP coordinator (coordinator.go).
For EAP-TLS, deliver a minimal working auth path first; certificate revocation / policy come in later milestones.
eap-otp currently uses a fixed sample OTP; do not copy its fixed value when implementing a real method.

Acceptance

Handler unit tests + end-to-end auth tests pass
Failure cases have explicit reject reasons and metrics
go test ./internal/radiusd/... and golangci-lint run pass
An end-to-end acceptance test is added under test/integration/ (see ../add-acceptance-test/SKILL.md), executed by CI
PR references TR-F004 and the M1 subtask ID, and cites the RFC clauses relied upon