Key Facts
- Category
- Security & Validation
- Input Types
- text
- Output Type
- json
- Sample Coverage
- 0
- API Ready
- Yes
Overview
The AGEX Keypair Generator allows you to quickly generate secure, base64-encoded Ed25519 keypairs specifically designed for AGEX bundle signing and verification. By creating a dedicated public and private key pair, you can ensure the integrity and authenticity of your AGEX packages during deployment and distribution.
When to Use
- •When preparing to sign AGEX bundles for secure distribution and deployment.
- •When setting up a new release pipeline or environment that requires cryptographic verification.
- •When rotating existing signing keys to maintain security compliance for your AGEX packages.
How It Works
- •Enter an optional Signer ID to label the generated keypair for a specific team, environment, or purpose.
- •Click the generate button to run the Ed25519 cryptographic keypair generation process.
- •Download or copy the resulting JSON output containing the base64-encoded public and private keys.
- •Store the private key securely for signing, and distribute the public key to parties verifying the bundles.
Use Cases
Examples
1. Generate Production Signing Key
DevOps Engineer- Background
- A DevOps engineer needs to configure a secure deployment pipeline for AGEX bundles and requires a new Ed25519 keypair.
- Problem
- Generating a secure, base64-encoded Ed25519 keypair labeled specifically for the production environment.
- How to Use
- Enter 'prod-signer-01' in the Signer ID field and click generate.
- Example Config
-
signerId: "prod-signer-01" - Outcome
- A JSON payload containing the Ed25519 public and private keys labeled with the Signer ID 'prod-signer-01' is generated.
2. Generate Keypair for Team Verification
Security Administrator- Background
- A security administrator wants to set up bundle verification for an external QA team.
- Problem
- Creating a keypair without a specific label to quickly test the signature verification flow.
- How to Use
- Leave the Signer ID field blank and click generate.
- Example Config
-
signerId: "" - Outcome
- A standard Ed25519 keypair is generated in JSON format, ready for immediate testing and verification.
Related Hubs
FAQ
What algorithm does this tool use?
It uses the Ed25519 signature scheme, which provides high security and fast performance.
Is the private key stored on your servers?
No, the keypair is generated locally in your browser and is never sent to or stored on any server.
What is the purpose of the Signer ID?
The Signer ID is an optional label to help you identify which keypair belongs to which environment, team, or deployment pipeline.
How should I store the generated private key?
You should store the private key in a secure secrets manager or environment variable, and never share it publicly.
How do others verify my AGEX bundles?
You share your generated public key with the verifying parties, who use it to validate the signatures created by your private key.