Unifi OS removed keytool in v3.1+ and other updates to unifi deploy hook #5095
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…certificates in case something goes wrong. Partial fixes in acmesh-official#3359 Comment #1817258702 and others - Unifi removed keytool from OS, which breaks the ability to deploy certificates used by the console. Deciding how to fix is up to the sysadmin, inserted some advice when it fails. Comment #2061486940 - Automatically set the cipher suites in system configuration.
|
fix the format errors. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ubiquiti removed keytool from UnifiOS ~v3.1, but still uses a JKS keystore with a self-signed for the console application.
This script probably shouldn't be auto-installing packages on appliances, but this now explains what's up to the user and lets them decide when it fails on a missing keytool.
The Unifi console is not configured to use strong cipher suites required by default letsencrypt RSA certificates, so update the configuration prior to service restart.
In my initial attempts to use this deploy hook, it broke and I had to hunt down original certificates, so backup the existing certificates, which we just assume are working.