Repository navigation
Fix SSH host pin comparison for Warpgate 0.29 upgrades - #4
Merged
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Warpgate 0.29.1 changes its SSH library banner. WarpgateSH previously treated
ssh-keyscancomments as key material, causing an unchanged bastion key to be rejected after the upgrade. Ignore comment lines while continuing to reject actual key changes.Add synthetic user API contract coverage for Warpgate 0.27.5, 0.28.6 and 0.29.1, including synchronization and saved-state preservation on malformed or failed responses. Document immutable upstream sources, admin-provider compatibility and the limits of the live verification.
Validation: 65 Rust workspace tests, workspace formatting and Clippy; frontend build and 7 JavaScript tests; 33 Tauri tests, formatting and Clippy. Live 0.29.1 synchronization and browser-approved OpenSSH connection succeeded with unchanged RSA/Ed25519 host keys. The installed 0.1.16 client was repaired by refreshing scan comments after comparing the approved key material; this PR does not publish an application release.