node-accelerator v3.4 + v3.5 (proxyware self-audit · CT_EST_TIMEOUT · SYNPROXY note)#13
Merged
Conversation
…SDK) Read-only proof that a node is not a residential proxy and carries no bandwidth-monetization SDK — evidence to answer hoster abuse tickets. - signature scan (IPIDEA/PacketSDK/Honeygain/EarnApp/Peer2Profit/...) across processes, systemd units, cron, files and docker images - established connections to known proxyware C2 (resolve domains -> match ESTABLISHED) - external-facing listeners (operator context) - verdict clean|suspect; `--proxyware --json` emits one object (CI single-line safe) - signatures are product names only; generic "proxy" is NOT matched, so the node's own xray/VLESS does not false-positive Tested on a live node: bash -n + shellcheck clean, verdict=clean, JSON one line. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
- optimize: nf_conntrack_tcp_timeout_established вынесен в ENV CT_EST_TIMEOUT (default 7440 без изменения поведения; валидируется 120..432000; персистится в optimize.conf — ре-ран без ENV не сбрасывает). idle-туннели/мосты могут ↑. - protect/README: SYNPROXY задокументирован как избыточный на VPN-relay (syncookies + per-IP ct-лимиты уже дают анти-спуф); остаётся opt-in/default-off. - CHANGELOG: v3.5. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
node-accelerator v3.4 + v3.5
Закрывает накопленную локальную ветку (v3.4) + мелкий тюнинг-апдейт (v3.5). Поведение по умолчанию НЕ меняется — новые ручки opt-in, дефолты = прежние значения.
v3.5 —
CT_EST_TIMEOUT+ SYNPROXY notenf_conntrack_tcp_timeout_establishedвынесен из хардкода в ENVCT_EST_TIMEOUT(сек, дефолт7440— без изменения поведения). Валидируется (120…432000, иначе дефолт) и персистится вoptimize.conf(ре-ран без ENV не сбрасывает). idle-туннели/мосты без частого keepalive могут поднять (напр.14400=4ч); ноды под флуд-профилем — дефолт (агрессивнее реклеймит брошенные / connect-and-hold established).tcp_syncookies=1+ per-IP ct-лимиты, а издержки (be_liberal, поломка TFO, per-packet overhead) не оправданы; против connect-and-hold / PPS не помогает. Остаётся opt-in, default off.v3.4 —
na-report --proxyware(read-only self-audit)clean|suspect,--json. Доказательная база под abuse-тикеты хостеров. Generic «proxy» не матчим (чтобы не ловить сам xray/VLESS).Проверки
shellcheck --severity=error— чисто;bash -n— чисто (локально).