You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 3, 2024. It is now read-only.
Seems like that https://hackasat.com CTF uses additional RNG seeds for flag generation.
Could this be something which we could considerate?
Challenges that you connect to require a ticket that the scoreboard will generate for you. Tickets look like: ticket{kilo73275yankee2:GLpXpjDWRQRmLDdyZwWmBiYKIbx4SkZp7u3Ak3WjpVy4RxI0luw2QwvLolmlmJm-vg} Tickets are bound to specific teams. Tickets include an RNG seed that challenges may use to provide a slightly different experience for your team, and to keep parts of that experience consistent across multiple connections.
Flags look like: flag{kilo73275yankee2:GAQXaJw0jWOS4UMNA6ptgf_1PrYj9BQVqph-C78Ptc4AXpUgucOlMd_MgjgsA3QcMa6YPfUuP_dftmeX44LfGig} (/flag{\w+:[a-zA-Z0-9-_]+}/ in PCRE and JS regex dialects.) Flags are bound to specific teams and can be correlated to connections. All flag submissions, including invalid ones, are logged. Do not share flags, and don't use a flag given to you by another team.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Seems like that https://hackasat.com CTF uses additional RNG seeds for flag generation.
Could this be something which we could considerate?
The text was updated successfully, but these errors were encountered: