[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A5E3ENSS6TFGZSSSJSD577":3,"skill-same:01M7A5E3ENSS6TFGZSSSJSD577":99},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":14,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":6,"ownerDescription":49,"updatedAt":50,"install":51,"resources":64},"01M7A5E3ENSS6TFGZSSSJSD577","configuring-tls-1-3-for-secure-communications",null,"Configures TLS 1.3 (RFC 8446) on servers, covering cipher suite and key-exchange group selection, and validates the resulting configuration with openssl s_client and testssl.sh. Use when deploying or hardening TLS 1.3 for secure communications, or when testing a server for common TLS misconfigurations and vulnerabilities.","NeelakshSaxena\u002FVayu","NeelakshSaxena","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F87892838?v=4","01M7A3B9YFS6F6N9DD1787DT86","Neelaksh Saxena","01M7A3B9ZKBT09MNMPX2XN69BY",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fconfiguring-tls-1-3-for-secure-communications\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fconfiguring-tls-1-3-for-secure-communications\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: configuring-tls-1-3-for-secure-communications\ndescription: Configures TLS 1.3 (RFC 8446) on servers, covering cipher suite and\n  key-exchange group selection, and validates the resulting configuration with openssl\n  s_client and testssl.sh. Use when deploying or hardening TLS 1.3 for secure communications,\n  or when testing a server for common TLS misconfigurations and vulnerabilities.\ndomain: cybersecurity\nsubdomain: cryptography\ntags:\n- cryptography\n- tls\n- ssl\n- transport-security\n- network-security\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.DS-01\n- PR.DS-02\n- PR.DS-10\nmitre_attack:\n- T1557\n- T1040\n- T1573.002\n- T1539\n- T1556.004\n---\n# Configuring TLS 1.3 for Secure Communications\n\n## Overview\n\nTLS 1.3 (RFC 8446) is the latest version of the Transport Layer Security protocol, providing significant improvements over TLS 1.2 in both security and performance. It reduces handshake latency to 1-RTT (and 0-RTT for resumed sessions), removes obsolete cipher suites, and mandates perfect forward secrecy. This skill covers configuring TLS 1.3 on servers, validating configurations, and testing for common misconfigurations.\n\n\n## When to Use\n\n- When deploying or configuring configuring tls 1 3 for secure communications capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- Familiarity with cryptography concepts and tools\n- Access to a test or lab environment for safe execution\n- Python 3.8+ with required dependencies installed\n- Appropriate authorization for any testing activities\n\n## Objectives\n\n- Configure TLS 1.3 on nginx and Apache web servers\n- Implement TLS 1.3 in Python applications using the ssl module\n- Validate TLS configurations with openssl and testssl.sh\n- Understand TLS 1.3 cipher suites and key exchange mechanisms\n- Configure 0-RTT early data with appropriate protections\n- Disable legacy TLS versions (1.0, 1.1) and weak cipher suites\n\n## Key Concepts\n\n### TLS 1.3 Cipher Suites\n\n| Cipher Suite | Key Exchange | Authentication | Encryption | Hash |\n|-------------|-------------|----------------|------------|------|\n| TLS_AES_256_GCM_SHA384 | ECDHE\u002FDHE | Certificate | AES-256-GCM | SHA-384 |\n| TLS_AES_128_GCM_SHA256 | ECDHE\u002FDHE | Certificate | AES-128-GCM | SHA-256 |\n| TLS_CHACHA20_POLY1305_SHA256 | ECDHE\u002FDHE | Certificate | ChaCha20-Poly1305 | SHA-256 |\n\n### TLS 1.3 vs 1.2 Improvements\n\n- **1-RTT Handshake**: Full handshake completes in one round trip (vs 2 in TLS 1.2)\n- **0-RTT Resumption**: Resumed connections can send data immediately\n- **No RSA Key Exchange**: Only ephemeral Diffie-Hellman (mandatory PFS)\n- **Simplified Cipher Suites**: Removed CBC, RC4, 3DES, static RSA, SHA-1\n- **Encrypted Handshake**: Server certificate is encrypted after ServerHello\n\n### Key Exchange Groups\n\n- **x25519**: Curve25519 ECDH (preferred, fast)\n- **secp256r1**: NIST P-256 ECDH (widely supported)\n- **secp384r1**: NIST P-384 ECDH (higher security margin)\n- **x448**: Curve448 ECDH (highest security)\n\n## Workflow\n\n1. Verify OpenSSL version supports TLS 1.3 (1.1.1+)\n2. Generate or obtain TLS certificate and private key\n3. Configure server to use TLS 1.3 cipher suites\n4. Disable TLS 1.0 and 1.1 (optionally keep 1.2 for compatibility)\n5. Set preferred key exchange groups\n6. Enable OCSP stapling for certificate validation\n7. Test configuration with openssl s_client and testssl.sh\n8. Configure HSTS header for HTTP Strict Transport Security\n\n## Security Considerations\n\n- 0-RTT data is vulnerable to replay attacks; limit to idempotent requests\n- Always include TLS 1.2 fallback if legacy client support is required\n- Use ECDSA certificates for better performance (vs RSA)\n- Enable OCSP stapling to improve client certificate validation\n- Set HSTS header with long max-age and includeSubDomains\n- Monitor for certificate transparency logs\n\n## Validation Criteria\n\n- [ ] TLS 1.3 handshake completes successfully\n- [ ] Only approved cipher suites are offered\n- [ ] Perfect forward secrecy is enforced\n- [ ] TLS 1.0 and 1.1 are rejected\n- [ ] OCSP stapling is functional\n- [ ] Certificate chain is valid and complete\n- [ ] testssl.sh reports no vulnerabilities\n","# Configuring TLS 1.3 for Secure Communications\n\n## Overview\n\nTLS 1.3 (RFC 8446) is the latest version of the Transport Layer Security protocol, providing significant improvements over TLS 1.2 in both security and performance. It reduces handshake latency to 1-RTT (and 0-RTT for resumed sessions), removes obsolete cipher suites, and mandates perfect forward secrecy. This skill covers configuring TLS 1.3 on servers, validating configurations, and testing for common misconfigurations.\n\n\n## When to Use\n\n- When deploying or configuring configuring tls 1 3 for secure communications capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- Familiarity with cryptography concepts and tools\n- Access to a test or lab environment for safe execution\n- Python 3.8+ with required dependencies installed\n- Appropriate authorization for any testing activities\n\n## Objectives\n\n- Configure TLS 1.3 on nginx and Apache web servers\n- Implement TLS 1.3 in Python applications using the ssl module\n- Validate TLS configurations with openssl and testssl.sh\n- Understand TLS 1.3 cipher suites and key exchange mechanisms\n- Configure 0-RTT early data with appropriate protections\n- Disable legacy TLS versions (1.0, 1.1) and weak cipher suites\n\n## Key Concepts\n\n### TLS 1.3 Cipher Suites\n\n| Cipher Suite | Key Exchange | Authentication | Encryption | Hash |\n|-------------|-------------|----------------|------------|------|\n| TLS_AES_256_GCM_SHA384 | ECDHE\u002FDHE | Certificate | AES-256-GCM | SHA-384 |\n| TLS_AES_128_GCM_SHA256 | ECDHE\u002FDHE | Certificate | AES-128-GCM | SHA-256 |\n| TLS_CHACHA20_POLY1305_SHA256 | ECDHE\u002FDHE | Certificate | ChaCha20-Poly1305 | SHA-256 |\n\n### TLS 1.3 vs 1.2 Improvements\n\n- **1-RTT Handshake**: Full handshake completes in one round trip (vs 2 in TLS 1.2)\n- **0-RTT Resumption**: Resumed connections can send data immediately\n- **No RSA Key Exchange**: Only ephemeral Diffie-Hellman (mandatory PFS)\n- **Simplified Cipher Suites**: Removed CBC, RC4, 3DES, static RSA, SHA-1\n- **Encrypted Handshake**: Server certificate is encrypted after ServerHello\n\n### Key Exchange Groups\n\n- **x25519**: Curve25519 ECDH (preferred, fast)\n- **secp256r1**: NIST P-256 ECDH (widely supported)\n- **secp384r1**: NIST P-384 ECDH (higher security margin)\n- **x448**: Curve448 ECDH (highest security)\n\n## Workflow\n\n1. Verify OpenSSL version supports TLS 1.3 (1.1.1+)\n2. Generate or obtain TLS certificate and private key\n3. Configure server to use TLS 1.3 cipher suites\n4. Disable TLS 1.0 and 1.1 (optionally keep 1.2 for compatibility)\n5. Set preferred key exchange groups\n6. Enable OCSP stapling for certificate validation\n7. Test configuration with openssl s_client and testssl.sh\n8. Configure HSTS header for HTTP Strict Transport Security\n\n## Security Considerations\n\n- 0-RTT data is vulnerable to replay attacks; limit to idempotent requests\n- Always include TLS 1.2 fallback if legacy client support is required\n- Use ECDSA certificates for better performance (vs RSA)\n- Enable OCSP stapling to improve client certificate validation\n- Set HSTS header with long max-age and includeSubDomains\n- Monitor for certificate transparency logs\n\n## Validation Criteria\n\n- [ ] TLS 1.3 handshake completes successfully\n- [ ] Only approved cipher suites are offered\n- [ ] Perfect forward secrecy is enforced\n- [ ] TLS 1.0 and 1.1 are rejected\n- [ ] OCSP stapling is functional\n- [ ] Certificate chain is valid and complete\n- [ ] testssl.sh reports no vulnerabilities\n",{"name":5,"tags":25,"author":31,"domain":32,"license":15,"version":33,"nist_csf":34,"subdomain":26,"description":7,"mitre_attack":38},[26,27,28,29,30],"cryptography","tls","ssl","transport-security","network-security","mahipal","cybersecurity","1.0",[35,36,37],"PR.DS-01","PR.DS-02","PR.DS-10",[39,40,41,42,43],"T1557","T1040","T1573.002","T1539","T1556.004","main","7540bbccf0c1ded6156a467b02c95b61ad62413f",".agents\u002Fskills\u002Fconfiguring-tls-1-3-for-secure-communications","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena","Currently exploring the intersection of tech","2026-09-11 03:02:31",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add NeelakshSaxena\u002FVayu --skill configuring-tls-1-3-for-secure-communications",{"tool":57,"command":58},"bunx","bunx skills add NeelakshSaxena\u002FVayu --skill configuring-tls-1-3-for-secure-communications",{"tool":60,"command":61},"pnpm","pnpm dlx skills add NeelakshSaxena\u002FVayu --skill configuring-tls-1-3-for-secure-communications","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fconfiguring-tls-1-3-for-secure-communications\u002FSKILL.md",true,[65,71,75,81,85,89,95],{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"assets\u002Ftemplate.md","ASSET","资产文件",2127,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fconfiguring-tls-1-3-for-secure-communications\u002Fassets\u002Ftemplate.md",{"path":72,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fapi-reference.md","REFERENCE","参考文档",1481,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fconfiguring-tls-1-3-for-secure-communications\u002Freferences\u002Fapi-reference.md",{"path":82,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fstandards.md",2573,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fconfiguring-tls-1-3-for-secure-communications\u002Freferences\u002Fstandards.md",{"path":86,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fworkflows.md",2304,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fconfiguring-tls-1-3-for-secure-communications\u002Freferences\u002Fworkflows.md",{"path":90,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":93,"sourceHtmlUrl":94},"scripts\u002Fagent.py","SCRIPT","脚本",5490,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fconfiguring-tls-1-3-for-secure-communications\u002Fscripts\u002Fagent.py",{"path":96,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":97,"sourceHtmlUrl":98},"scripts\u002Fprocess.py",14481,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fconfiguring-tls-1-3-for-secure-communications\u002Fscripts\u002Fprocess.py",[100,107,114,121,128,135],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":20},"01M7ACCCVNCFKMA9X6D15X6G98","runpodctl","Runpod CLI for managing GPU\u002FCPU workloads from the terminal — pods, serverless endpoints, templates, network volumes, Hub deploys, models, SSH, and file transfer (send\u002Freceive). Use for terminal\u002FCI\u002Fscripting, Hub browse\u002Fdeploy, SSH setup, `doctor`, or when the Runpod MCP tools are not connected. For structured tool calls in an MCP-enabled session, prefer runpod-mcp.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpodctl\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":20},"01M7ACC63SRHEA5KMCHSMZK2TC","runpod","Start here for any Runpod task — running GPU\u002FCPU pods, deploying serverless endpoints, templates, network volumes, building images, or understanding how Runpod works. Routes to the right skill (runpod-mcp, runpodctl, flash, companion-clis, runpod-usage, runpod-templates, runpod-migrate) and indexes two dozen live-verified end-to-end examples (golden paths) — use it when the lane is unclear, and for any multi-step or provisioning task even when it is not.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":20},"01M7ACC0Q1C89N9BZBV91CTQTF","runpod-usage","How Runpod works and how to work it — pods vs serverless, GPU\u002FVRAM selection, storage, building a container, networking, plus the agentic pod development loop (provision → ssh-exec → set up → poll readiness) and on-pod install hygiene (uv\u002Fapt). Use to answer \"how does X work\", \"which GPU\", \"how do I build a container\", or \"how do I stand up a workload on a pod\". Guidance, not a tool — execute with runpodctl, runpod-mcp, or flash.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-usage\u002FSKILL.md",[],[],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":20},"01M7ACBRPE345GF5GM5B8P8RRC","runpod-templates","Runpod's official prebuilt pod templates (ComfyUI, PyTorch, and others): what each image ships, which ports and paths it uses, how to pick one, how to pin a version, and what is missing on first boot. Use when a task says \"run \u003CX> on a pod\" and an official template already covers it, instead of building an image — and when a user needs help with or wants to fix something about a Runpod template they are already running (won't boot, can't reach the UI, missing models, wrong CUDA line, broken ComfyUI workflow metadata on imported workflows): start here and route onward. Deploy with runpodctl or runpod-mcp; end-to-end walkthroughs live in the runpod router's golden paths.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-templates\u002FSKILL.md",[],[],{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":20},"01M7ACBJATHKVX1TWES2F44GY8","runpod-migrate","Migrate a codebase from the Runpod GraphQL API or REST v1 to REST v2 — inventory which parts use which API version, rewrite the call sites, flag breaking changes, and verify. Use when someone asks to move to v2, asks what v2 would change, or asks which Runpod API their code is on. For managing infrastructure rather than migrating code, use runpod-mcp or runpodctl.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-migrate\u002FSKILL.md",[],[],{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":20},"01M7ACBC7GHVH6T9YEAPCG2AP8","runpod-mcp","Manage Runpod infrastructure — pods, serverless endpoints, jobs, templates, network volumes, container-registry auth, GPU\u002FCPU catalog, and billing — via the Runpod MCP server's structured tool calls. Use when the Runpod MCP tools (create-pod, list-endpoints, …) are connected in this session, or to connect them (hosted OAuth or local npx). Prefer this over runpodctl for plain infra CRUD when MCP is available; use runpodctl for the terminal, file transfer, or SSH setup.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-mcp\u002FSKILL.md",[],[]]