[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6HM17BRCMDM6MM62SPPMFKA":3,"skill-same:01M6HM17BRCMDM6MM62SPPMFKA":111},{"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":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":6,"ownerHtmlUrl":59,"ownerBlogUrl":6,"ownerDescription":60,"updatedAt":61,"install":62,"resources":75},"01M6HM17BRCMDM6MM62SPPMFKA","implementing-digital-signatures-with-ed25519",null,"Ed25519 is a high-performance digital signature algorithm using the Edwards curve Curve25519. It provides 128-bit security with 64-byte signatures and 32-byte keys, offering significant advantages ove","HenriqueMC17\u002Fagente-core","HenriqueMC17","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F206460478?v=4","01M6HB63HBBF18AC4H09XTB549","Henrique Monteiro Cardoso","01M6HB63NGSQXWKWCFWW2B20W0",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fimplementing-digital-signatures-with-ed25519\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"implementing","with","ed25519","implementing digital signatures with ed25519","signatures","curve","security","high","keys","it","high-performance","bit","integrity","digital-signatures","cryptography","authentication","pr","cybersecurity","performance","2026-11-10 10:12:30",false,"---\nname: implementing-digital-signatures-with-ed25519\ndescription: Ed25519 is a high-performance digital signature algorithm using the Edwards curve Curve25519. It provides 128-bit security with 64-byte signatures and 32-byte keys, offering significant advantages ove\ndomain: cybersecurity\nsubdomain: cryptography\ntags:\n- cryptography\n- digital-signatures\n- ed25519\n- authentication\n- integrity\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- T1600\n- T1573\n- T1553\ncategory: implementing-digital-signatures-with-ed25519\n---\n# Implementing Digital Signatures with Ed25519\n\n## Overview\n\nEd25519 is a high-performance digital signature algorithm using the Edwards curve Curve25519. It provides 128-bit security with 64-byte signatures and 32-byte keys, offering significant advantages over RSA and ECDSA including deterministic signatures (no random nonce needed), resistance to side-channel attacks, and fast verification. This skill covers implementing Ed25519 for document signing, code signing, and API authentication.\n\n\n## When to Use\n\n- When deploying or configuring implementing digital signatures with ed25519 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- Generate Ed25519 key pairs for signing\n- Sign messages and files with Ed25519\n- Verify signatures against public keys\n- Implement multi-signature verification\n- Build a simple code signing system\n- Compare Ed25519 performance with RSA and ECDSA\n\n## Key Concepts\n\n### Ed25519 vs RSA vs ECDSA\n\n| Property | Ed25519 | RSA-3072 | ECDSA P-256 |\n|----------|---------|----------|-------------|\n| Security | 128-bit | 128-bit | 128-bit |\n| Public key size | 32 bytes | 384 bytes | 64 bytes |\n| Signature size | 64 bytes | 384 bytes | 64 bytes |\n| Key generation | ~50 us | ~100 ms | ~1 ms |\n| Sign | ~70 us | ~5 ms | ~200 us |\n| Verify | ~200 us | ~200 us | ~500 us |\n| Deterministic | Yes | No (PSS) | No (unless RFC 6979) |\n\n### Key Properties\n\n- **Deterministic**: Same message + key always produces same signature\n- **Collision-resistant**: No separate hash function needed\n- **Side-channel resistant**: Constant-time implementation\n- **Small keys**: 32 bytes each (public and private)\n\n## Security Considerations\n\n- Ed25519 does not support key recovery from signatures\n- Verify the full message, not a hash (Ed25519 hashes internally)\n- Public keys must be validated before use (check for low-order points)\n- Private keys should be stored encrypted at rest\n- Ed25519 is not yet approved for all NIST use cases (Ed448 is preferred for federal)\n\n## Validation Criteria\n\n- [ ] Key pair generation produces valid Ed25519 keys\n- [ ] Signature verification succeeds for valid message\n- [ ] Signature verification fails for tampered message\n- [ ] Signature verification fails for wrong public key\n- [ ] Deterministic: same input produces same signature\n- [ ] File signing and verification works correctly\n- [ ] Performance meets or exceeds RSA-3072\n","# Implementing Digital Signatures with Ed25519\n\n## Overview\n\nEd25519 is a high-performance digital signature algorithm using the Edwards curve Curve25519. It provides 128-bit security with 64-byte signatures and 32-byte keys, offering significant advantages over RSA and ECDSA including deterministic signatures (no random nonce needed), resistance to side-channel attacks, and fast verification. This skill covers implementing Ed25519 for document signing, code signing, and API authentication.\n\n\n## When to Use\n\n- When deploying or configuring implementing digital signatures with ed25519 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- Generate Ed25519 key pairs for signing\n- Sign messages and files with Ed25519\n- Verify signatures against public keys\n- Implement multi-signature verification\n- Build a simple code signing system\n- Compare Ed25519 performance with RSA and ECDSA\n\n## Key Concepts\n\n### Ed25519 vs RSA vs ECDSA\n\n| Property | Ed25519 | RSA-3072 | ECDSA P-256 |\n|----------|---------|----------|-------------|\n| Security | 128-bit | 128-bit | 128-bit |\n| Public key size | 32 bytes | 384 bytes | 64 bytes |\n| Signature size | 64 bytes | 384 bytes | 64 bytes |\n| Key generation | ~50 us | ~100 ms | ~1 ms |\n| Sign | ~70 us | ~5 ms | ~200 us |\n| Verify | ~200 us | ~200 us | ~500 us |\n| Deterministic | Yes | No (PSS) | No (unless RFC 6979) |\n\n### Key Properties\n\n- **Deterministic**: Same message + key always produces same signature\n- **Collision-resistant**: No separate hash function needed\n- **Side-channel resistant**: Constant-time implementation\n- **Small keys**: 32 bytes each (public and private)\n\n## Security Considerations\n\n- Ed25519 does not support key recovery from signatures\n- Verify the full message, not a hash (Ed25519 hashes internally)\n- Public keys must be validated before use (check for low-order points)\n- Private keys should be stored encrypted at rest\n- Ed25519 is not yet approved for all NIST use cases (Ed448 is preferred for federal)\n\n## Validation Criteria\n\n- [ ] Key pair generation produces valid Ed25519 keys\n- [ ] Signature verification succeeds for valid message\n- [ ] Signature verification fails for tampered message\n- [ ] Signature verification fails for wrong public key\n- [ ] Deterministic: same input produces same signature\n- [ ] File signing and verification works correctly\n- [ ] Performance meets or exceeds RSA-3072\n",{"name":5,"tags":43,"author":44,"domain":36,"license":15,"version":45,"category":5,"nist_csf":46,"subdomain":33,"description":7,"mitre_attack":50},[33,32,21,34,31],"mahipal","1.0",[47,48,49],"PR.DS-01","PR.DS-02","PR.DS-10",[51,52,53],"T1600","T1573","T1553","main","5eea5b3296f4673b5f481e8bcc1ba76281149f16","modules\u002Fimplementing-digital-signatures-with-ed25519",0,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core","https:\u002F\u002Fgithub.com\u002FHenriqueMC17","Qualquer tecnologia suficientemente avançada é indistinguível da mágica.","2026-09-28 22:40:38",{"source":8,"skillName":5,"commands":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add HenriqueMC17\u002Fagente-core --skill implementing-digital-signatures-with-ed25519",{"tool":68,"command":69},"bunx","bunx skills add HenriqueMC17\u002Fagente-core --skill implementing-digital-signatures-with-ed25519",{"tool":71,"command":72},"pnpm","pnpm dlx skills add HenriqueMC17\u002Fagente-core --skill implementing-digital-signatures-with-ed25519","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fimplementing-digital-signatures-with-ed25519\u002FSKILL.md",true,[76,82,87,93,97,101,107],{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},"assets\u002Ftemplate.md","ASSET","资产文件",890,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fimplementing-digital-signatures-with-ed25519\u002Fassets\u002Ftemplate.md",{"path":83,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":86},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fimplementing-digital-signatures-with-ed25519\u002FLICENSE",{"path":88,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fapi-reference.md","REFERENCE","参考文档",1712,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fimplementing-digital-signatures-with-ed25519\u002Freferences\u002Fapi-reference.md",{"path":94,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Fstandards.md",1314,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fimplementing-digital-signatures-with-ed25519\u002Freferences\u002Fstandards.md",{"path":98,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Fworkflows.md",1343,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fimplementing-digital-signatures-with-ed25519\u002Freferences\u002Fworkflows.md",{"path":102,"resourceType":103,"resourceTypeDesc":104,"sizeBytes":105,"sourceHtmlUrl":106},"scripts\u002Fagent.py","SCRIPT","脚本",5885,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fimplementing-digital-signatures-with-ed25519\u002Fscripts\u002Fagent.py",{"path":108,"resourceType":103,"resourceTypeDesc":104,"sizeBytes":109,"sourceHtmlUrl":110},"scripts\u002Fprocess.py",11192,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fimplementing-digital-signatures-with-ed25519\u002Fscripts\u002Fprocess.py",[112,142,167,189,205,226],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":123,"publishedAt":38},"01M6HPFF0RCN0X6WT5EBSV71GY","validating-backup-integrity-for-recovery","Validate backup integrity through cryptographic hash verification, automated restore testing, corruption detection, and recoverability checks to ensure backups are reliable for disaster recovery and ransomware response scenarios.","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fvalidating-backup-integrity-for-recovery\u002FSKILL.md",[118],{"categoryNo":119,"categoryName":120,"taxonomyType":121,"taxonomyTypeDesc":122},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[31,124,125,126,127,128,36,129,130,131,132,133,134,135,136,137,138,139,140,141],"backup","recovery","validating backup integrity for recovery","for","testing","validate","verification","hash-verification","incident-response","ransomware","detection","t1078","t1490","disaster-recovery","restore","incident","disaster recovery","ransomware response",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":148,"publishedAt":38},"01M6HPFAWJVFK25Q33K3T7WQ8G","triaging-vulnerabilities-with-ssvc-framework","Triage and prioritize vulnerabilities using CISA's Stakeholder-Specific Vulnerability Categorization (SSVC) decision tree framework to produce actionable remediation priorities.","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-vulnerabilities-with-ssvc-framework\u002FSKILL.md",[],[149,150,151,152,20,36,153,154,155,156,157,158,159,160,161,162,163,164,165,166],"vulnerabilities","framework","ssvc","triaging vulnerabilities with ssvc framework","triage and prioritize","CISA","vulnerability-management","risk-management","cvss","remediation","vulnerability","prioritization","decision-tree","prioritize","decision","priorities","actionable","tree",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":173,"publishedAt":38},"01M6HPF6JS9X72WP59094H3ASQ","triaging-security-incident","Performs initial triage of security incidents to determine severity, scope, and required response actions using the NIST SP 800-61r3 and SANS PICERL frameworks. Classifies incidents by type, assigns priority based on business impact, and routes...","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-security-incident\u002FSKILL.md",[],[25,174,139,36,175,176,177,135,136,178,179,180,181,182,183,184,185,186,187,188],"triaging security incident","actions","soc","NIST","analysis","severity-classification","incident-triage","SANS-PICERL","SOC-operations","picerl","conversion","isolation","scope","impact","consistency",{"skillNo":190,"name":191,"nameZh":6,"description":192,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":193,"categories":194,"keywords":195,"publishedAt":38},"01M6HPF2EX6ZYNYYHKBRJN7GEF","triaging-security-incident-with-ir-playbook","Classify and prioritize security incidents using structured IR playbooks to determine severity, assign response teams, and initiate appropriate response procedures.","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-security-incident-with-ir-playbook\u002FSKILL.md",[],[25,196,197,174,139,20,36,198,176,132,199,200,135,136,201,179,162,202,203,204],"playbook","triaging security incident with ir playbook","teams","IR-playbook","severity","classification","classify","incidents","initiate",{"skillNo":206,"name":207,"nameZh":6,"description":208,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":209,"categories":210,"keywords":211,"publishedAt":38},"01M6HPEY9XPGE7X95AG4XJFQAW","triaging-security-alerts-in-splunk","Triages security alerts in Splunk Enterprise Security by classifying severity, investigating notable events, correlating related telemetry, and making escalation or closure decisions using SPL queries and the Incident Review dashboard. Use when...","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-security-alerts-in-splunk\u002FSKILL.md",[],[25,212,213,214,215,216,36,217,218,219,176,220,135,221,222,223,182,224,139,225],"security alerts","splunk","triaging security alerts in splunk","alerts","review","siem","dashboard","search","correlation-search","t1566","notable-events","incident-review","cm","de",{"skillNo":227,"name":228,"nameZh":6,"description":229,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":230,"categories":231,"keywords":232,"publishedAt":38},"01M6HPET6XGEPEJPN7V032JGZ0","tracking-threat-actor-infrastructure","Threat actor infrastructure tracking involves monitoring and mapping adversary-controlled assets including command-and-control (C2) servers, phishing domains, exploit kit hosts, bulletproof hosting, a","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftracking-threat-actor-infrastructure\u002FSKILL.md",[],[233,234,235,236,36,237,238,239,240,241,242,221,243,244,224,245,225,246,247,248],"infrastructure","tracking threat actor infrastructure","tracking","threat","monitoring","mitre-attack","threat-actor","threat-intelligence","command-and-control","dns","command","exploit","intelligence","domains","kit","hosts"]