libatbus-protocol-crypto

Implement X25519 ECDH handshakes and encrypt libatbus protocol messages.

234|71|Updated Mar 14, 2016
One-click install
npx skills add https://github.com/owent/libatbus --skill libatbus-protocol-crypto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: libatbus-protocol-crypto
Source: https://github.com/owent/libatbus/tree/main/.agents/skills/libatbus-protocol-crypto
Command: npx skills add https://github.com/owent/libatbus --skill libatbus-protocol-crypto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enables secure transport for libatbus by providing a robust cryptographic handshake (ECDH), algorithm negotiation, encryption of messages, and authenticated access token handling, ensuring trusted node communication.

Core Features & Use Cases

  • End-to-end crypto handshake using X25519 and HKDF-SHA256 key derivation
  • Protobuf-based message framing with optional compression and encryption
  • Token-based authentication and signing for access control
  • Testing patterns and cross-language vector support for crypto flows
  • Configurable crypto and compression policies for runtime reloading

Quick Start

Instantiate two nodes, perform an X25519 handshake, and securely exchange a test message.

Frequently Asked Questions about libatbus-protocol-crypto

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

FAQPage Schema
How do I implement an ECDH handshake for secure node communication?

The protocol supports AEAD and CBC ciphers, allowing per-message encryption decisions. You can selectively encrypt messages based on your security requirements while maintaining protobuf-based message framing across node communications.

Can I negotiate compression alongside encryption for protobuf messages?

Yes, configurable crypto and compression policies support runtime reloading. The protocol enables dynamic negotiation of compression algorithms alongside encryption settings, applying per-message encryption decisions to optimize secure data transport.

How does token-based authentication work for libatbus protocol connections?

Token-based authentication and signing validate access control during the handshake process. This mechanism ensures only authenticated nodes establish trusted connections, securing communications across various platforms.

Does this crypto handshake support cross-language testing vectors?

Yes, the implementation provides testing patterns and cross-language vector support for crypto flows. This enables validation of handshake, encryption, and message framing logic across various platform implementations.