opportunistic-security-rfc7435

Guide communication protocol design with RFC 7435 opportunistic security principles.

Updated Jul 20, 2026
One-click install
npx skills add https://github.com/trancee/MeshLink-template --skill opportunistic-security-rfc7435
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opportunistic-security-rfc7435
Source: https://github.com/trancee/MeshLink-template/tree/main/.agents/skills/opportunistic-security-rfc7435
Command: npx skills add https://github.com/trancee/MeshLink-template --skill opportunistic-security-rfc7435

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of implementing secure communication protocols that avoid the all-or-nothing trap, ensuring that encryption is used whenever possible without breaking connectivity.

Core Features & Use Cases

  • Protocol Design Guidance: Provides the framework for implementing cleartext-baseline security that upgrades to encrypted or authenticated sessions per-peer.
  • Trust Model Implementation: Offers clear definitions and logic for integrating Trust on First Use (TOFU) and downgrade-resistant authentication methods.
  • Use Case: When designing a peer-to-peer messaging SDK, use this Skill to determine how to negotiate encryption with peers while maintaining compatibility with legacy nodes that do not yet support advanced authentication.

Quick Start

Use the opportunistic-security-rfc7435 skill to analyze my current protocol design and suggest improvements for implementing opportunistic encryption and TOFU trust models.

Frequently Asked Questions about opportunistic-security-rfc7435

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is opportunistic security and how does it handle protocol encryption upgrades?

Opportunistic security provides encrypted communication whenever possible without breaking connectivity, establishing a cleartext baseline that upgrades to encrypted sessions per-peer based on negotiated capabilities.

How do I implement Trust on First Use (TOFU) for peer-to-peer messaging protocols?

Implementing TOFU requires defining trust model logic that accepts an initial unauthenticated peer key, then integrating downgrade-resistant authentication to prevent attackers from forcing cleartext fallback on subsequent connections.

Can I use opportunistic security to maintain compatibility with legacy networking nodes?

Yes, opportunistic security is designed for incremental security deployment, allowing your protocol to negotiate encryption with capable peers while maintaining cleartext fallback for legacy nodes lacking advanced authentication.

What is the best way to design downgrade-resistant authentication for communication protocols?

The best way is implementing per-peer capability negotiation that strictly validates session upgrades, ensuring any fallback to unauthenticated cleartext is logged and limited to genuinely unsupported legacy peers.

When should I not use opportunistic encryption in my protocol design?

Avoid opportunistic encryption when your protocol requires strict mandatory mutual authentication for all sessions, as its cleartext-fallback logic intentionally permits unauthenticated connections to maximize peer connectivity.