Update vsatctl to Upgrade Security of Existing VSatellite Connections
Table of Contents
Expand all | Collapse all
-
- Activate Next-Generation Trust Security
-
-
- Configure Akamai Connection
- 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
-
-
-
- Add AWS Public CA
- Add AWS Private CA
- Add DigiCert One Certificate Authority
- Add Entrust
- Add GlobalSign Atlas
- Add GlobalSign MSSL
- Add GoDaddy
- Add Google CAS (GCAS)
- Add a HID PKIaaS CA
- Add Certificate Manager - Self-Hosted
- Set Up an OpenSSL Certificate Authority Connector
- Create a Sectigo Certificate Manager Certificate Authority
- Add SSL.com
- Add Zero Touch PKI
-
- Example: Create a Custom CA Connector Using the CA Connector Framework
- Creating an Entrust CA Gateway Connector
- Creating a HashiCorp Vault CA Connector
- Creating a SecureW2 Connector
- Creating a SwissSign Connector
- Creating a Tucows OpenSRS Connector
- Working with Custom CA Connectors in the Certificate Authorities Inventory
- Set Up Certificate Expiration Notifications
- Using a Custom DNS Provider
- CNAME Delegation for Domain Validation
- About Authorized Domains
-
- Getting Started with Next-Gen CA
- Adding Root CAs
- Adding Issuing CAs
- Agentic Plugins for Next-Gen CA
- Downloading Root CA Certificates
- Decommissioning CAs
- Viewing Your PKI
- Viewing CA Details
- CA Configuration Limits
- Default CAs by Configuration Tier
- About the PKI Hierarchy
- About Configuration Tiers
- About Certificate Issuance and Revocation
- About Post-Quantum Certificates
- About Subordinate CA Providers
- Add Subordinate CA Providers
- About Issuer Configurations
- Issuer Certificates Page
-
-
- 47-Day Validity Readiness TLS Certificates
- About the Certificate Inventory
- Managing Certificate Lifecycle Settings
- Reissuing Certificates in Next-Gen Trust Security
- Duplicating DigiCert Certificates
- Downloading Certificates, Certificate Chains, and Keystores
- Retiring, Recovering, and Deleting Certificates
- Finding Certificates in the Certificate Inventory
- Importing Certificates from DigiCert
- Importing Certificates from EJBCA
- Importing Certificates from GlobalSign Atlas
- Importing Certificates from GlobalSign MSSL
-
- Create a Workload Identity Management or Discovery Agent Built-in Account
- Create an OCI Registry Built-in Account
- Create a Certificate Manager - Self-Hosted Built-in Account
- Create a Scanafi Built-in Account
- Toggling a Built-in Account On or Off
- Editing Built-in Accounts
- Deleting Existing Built-in Accounts
- Renew Existing Built-in Accounts
- Licensing PKI
- Troubleshooting
Update vsatctl to Upgrade Security of Existing VSatellite Connections
Updated 11 February 2025
VSatellite has been updated to improve security by enabling TLS certificate validation when k3s connects to the Venafi registry. Previously, k3s did not validate TLS certificates, which could allow insecure connections. This security update is automatically applied to new VSatellite installations, but if you have existing VSatellite servers, you must manually update them.
To Upgrade a VSatellite Server
- Download the latest version of vsatctl:curl -O https://dl.venafi.cloud/vsatctlMake the file executable and run the security update:chmod +x ./vsatctl && ./vsatctl update securityIf your registries.yaml file is in a non-default location, specify the path:sudo ./vsatctl update security --registries-file /path/to/registries.yaml
Important Considerations
- If you have custom configurations in registries.yaml, they will be overwritten when you run the security update.To preserve custom configurations, back up the file before updating:cp /etc/rancher/k3s/registries.yaml /etc/rancher/k3s/registries.yaml.bakAfter updating, manually reapply your custom configurations.Alternatively, you can skip running the security update and manually edit the registries.yaml file:
- Open the file in a text editor:nano /etc/rancher/k3s/registries.yamlLocate the insecure_skip_verify setting and change it to false:mirrors: your-registry: endpoint: - "https://your-registry-url" tls: insecure_skip_verify: falseSave and exit the file.Restart k3s to apply the changes:sudo systemctl restart k3s
How Will I Know If My Server Needs This Update?
If your vsatctl is older than version 2.0.32, you should apply this update as a best practice to align with the latest security standards.Where Can I Get Support?
For additional guidance or troubleshooting, contact CyberArk support or visit our Customer Support site.