enclave-tls-interceptor

Intercept TLS sessions and generate ephemeral CA and leaf certificates for the Latch Enclave proxy.

2|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/latchagent/latch-core --skill enclave-tls-interceptor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: enclave-tls-interceptor
Source: https://github.com/latchagent/latch-core/tree/main/.agents/skills/enclave-tls-interceptor
Command: npx skills add https://github.com/latchagent/latch-core --skill enclave-tls-interceptor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires node-forge, and includes scripts (resource) components.

What problem does it solve?

This Skill provides secure TLS session interception for the Latch Enclave proxy, ensuring encrypted communication and managing certificate generation for enhanced security.

Core Features & Use Cases

  • TLS Session Interception: Intercept and manage TLS sessions for secure communication.
  • Ephemeral CA Certificate Generation: Generates self-signed RSA 2048 CA certificates for each session.
  • Per-Domain Leaf Certificates: On-demand generation of signed certificates for each domain.
  • Session Lifecycle Management: Entire lifecycle tied to session start and end.
  • Use Case: Ideal for securing data transmission between Latch Enclave and external services.

Quick Start

Start a new session with the Latch Enclave proxy and enable TLS interception.

Frequently Asked Questions about enclave-tls-interceptor

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

FAQPage Schema
How do I intercept TLS sessions for a secure proxy?

TLS session interception for a secure proxy is handled by managing the session lifecycle and generating domain-specific leaf certificates on demand. This ensures encrypted communication between the proxy and external services.

How does ephemeral certificate generation work for secure communication?

Ephemeral certificate generation creates a self-signed RSA 2048 CA certificate for each session. It then issues on-demand domain-specific leaf certificates signed by that CA to secure communication.

Do I need node-forge to generate X.509 certificates for proxy session management?

Yes, node-forge is required as a dependency to handle X.509 certificate generation. It provides the cryptographic functions needed to create the CA and leaf certificates during the session lifecycle.

Can I use TLS interception for securing data transmission to external services?

Yes, TLS interception secures data transmission to external services by generating ephemeral CA and leaf certificates. This ensures all communication remains encrypted throughout the proxy session lifecycle.

What is the best way to manage per-domain leaf certificates for intercepted sessions?

The best way to manage per-domain leaf certificates is generating them on demand during the session lifecycle. A self-signed RSA 2048 CA certificate signs each domain-specific leaf certificate for secure communication.

When should I not use ephemeral CA certificates for TLS interception?

Ephemeral CA certificates for TLS interception are tied to the session lifecycle and should not be used when persistent trust is required. Since the CA is regenerated per session, long-term certificate pinning will fail.