LTD-Beget / LTD-Beget/syncookied
FYI: syncsync solves SipHash vs SHA-1 mismatch and adds a time-based shared-secret ticker
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 324
- Forks
- 42
- PR merge metrics
- No merged PRs in 30d
Description
If you use syncookied in networks where a single public IP (VIP) is terminated by multiple hosts—and you’re stuck with “where to get a shared secret,” or simply want to run newer kernels (Linux 4.11+ computes TCP SYN cookies with SipHash while the public syncookied relies on SHA-1)—consider **syncsync**. It’s a loadable kernel module (LKM) that restores SHA-1 for TCP SYN cookies system-wide and adds a time-based shared-secret ticker (derived from a base secret + time identically across all servers). Packaged via DKMS—no kernel rebuild required.
When used together with syncookied, it removes the need for tcpsecrets and userspace secret distribution, and simplifies transparent on-path insertion/removal of syncookied in multi-host setups (ECMP/DR, etc.). Repository: [psylity/syncsync](https://github.com/psylity/syncsync).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
This issue is an informational reference to the external psylity/syncsync repository; it names no file, test, or entry point in syncookied. Start by reviewing the linked project and repository context, but no completion criteria or change to this repository are specified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- networking, operating-systems, security
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100