Repository navigation
Serve randomized decoy sites with robots.txt - #2
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
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.
Masked HTTPS routes now serve a static site through GOST's built-in loopback file server, including
/robots.txtwithDisallow: /and HTMLnoindex,nofollow. A standard-library Python script generates a random heading and abstract SVG once; repeated Ansible runs preserve the site. Knock and authenticated proxy traffic retain their existing behavior.Verification uses public route metadata so route-specific masking is checked without logging chain credentials. Includes generation tests and regeneration instructions. One-time migration commands and private inventory are excluded.
Validation:
Host provisioning now runs both Ubuntu 24.04 and Debian 12 two-host Jump on every PR and push, including main. Workflow YAML and event/job conditions were validated locally.
SSH configuration validation handlers now trigger their reload notifications after successful validation. A runnable Ansible regression test covers both admin and proxy handlers (56 local tests passed). The two-host CI test shares SSH identity/known-host settings with ProxyJump and no longer manually reloads SSH before testing, so unapplied configuration cannot be masked.