Trusting Venafi's public key
Table of Contents
Expand all | Collapse all
-
- Activate Next-Generation Trust Security
-
-
- Configure AWS connection
- Configure Azure Key Vault connection
-
- Workload Identity Federation authentication
- Workload Identity Federation - Azure Identity Provider authentication
- Next-Gen Trust Security Generated Key authentication
- User permissions
- Workload Identity Federation authentication
- Next-Gen Trust Security Generated Key authentication
- User permissions
- Supported OIDC claims
-
-
-
-
- Create an F5 BIG-IP LTM machine
- Create a Microsoft Azure Private Key Vault machine
- Create a Microsoft IIS machine
- Create a Microsoft Windows (PowerShell) machine
- Create a Microsoft SQL Server machine
- Create a Common KeyStore machine
- Create a Citrix ADC machine
- Create an Imperva WAF machine
- Create a VMware NSX Advanced Load Balancer (AVI) machine
- Create an A10 Thunder ADC machine
- Create a Cloudflare machine
- Create Kemp Virtual LoadMaster machine
- Create a Palo Alto Panorama machine
-
- Provision to an F5 BIG-IP LTM
- Provision to a Microsoft Azure Private Key Vault
- Provision to Microsoft IIS
- Provision to Microsoft Windows (PowerShell)
- Provision to Microsoft SQL Server
- Provision to a Common KeyStore
- Provision to a Citrix ADC
- Provision to an Imperva WAF
- Provision to VMware NSX Advanced Load Balancer (AVI)
- Provision to an A10 Thunder ADC
- Provision to Cloudflare
- Provision to a Kemp Virtual LoadMaster
- Provision to Palo Alto Panorama
-
-
- 47-Day Validity Readiness TLS Certificates dashboard
- About the Certificate Inventory
- Managing certificate lifecycle settings
- Reissuing certificates in Next-Gen Trust Security
- Downloading certificates, certificate chains, and keystores
- Retiring, recovering, and deleting certificates
- Finding certificates in the certificate inventory
- Importing certificates from a CA using EJBCA
- Notification Center overview
- Domain-based validation for external emails
- Managing user accounts
- Troubleshooting
Trusting Venafi's public key
If you've not already trusted Venafi's public key, you'll receive a warning during deployment when you verify the VSatellite installer. You can avoid that warning by manually trusting Venafi's public key before you begin deployment.
This step is optional, but recommended.
Download and import Venafi's key
- Download Venafi's public key.curl -O https://dl.venafi.cloud/vaaskey.pubImport the key into your GPG keyring.gpg --import ./vaaskey.pubSet Ownertrust for Venafi, Inc. to Ultimate.echo -e "trust\n5\ny\n" | gpg --no-tty --command-fd 0 --edit-key "gpg-vaas@venafi.com"Verify the key in your keyring.gpg --list-keysThe result should look similar to the following:/home/edge/.gnupg/pubring.kbx ----------------------------- pub rsa4096 2022-03-18 [SCEA] BA2F4B4442D945F0A2810A686B99EC1CEEE83892 uid [ultimate] Venafi, Inc. <gpg-vaas@venafi.com> sub rsa2048 2022-03-22 [A] sub rsa2048 2022-03-22 [E]
What's next
Now that you've trusted Venafi's public key, you'll be able to verify the VSatellite installer download when you deploy VSatellites.If you want to download the VSatellite installer and the VSatellite signature file, you can use the following:curl -O https://dl.venafi.cloud/vsatctl && \ curl -O https://dl.venafi.cloud/vsatctl.sigVerifying VSatellite after download
After you have downloaded the VSatellite installer and the VSatellite signature file as part of the deploying VSatellite steps, you can verify by running the following:gpg --verify vsatctl.sig vsatctlThe result should look similar to the following:gpg: Signature made Thu Jul 27 06:37:24 2023 UTC gpg: using RSA key BA2F4B4442D945F0A2810A686B99EC1CEEE83892 gpg: issuer "gpg-vaas@venafi.com" gpg: Good signature from "Venafi, Inc. <gpg-vaas@venafi.com>" [ultimate]Related links
- If you're deploying to RHEL, carefully review special considerations here