How Kordon security works
- On the computer: no admin rights; the panel talks to Kordon on
127.0.0.1with a random key in a user-only file, and checks the host, the key and the origin (DNS rebinding and CSRF); the browser extension answers only to extensions; secrets on disk are0600. - Beyond a plain kill switch: apps are paused right before the computer sleeps and let go only after a fresh IP check on waking; if Kordon crashes or is killed, a watchdog pauses the protected apps until it's back; IPv6, DNS, WebRTC, proxy-bypass and per-service route checks;
kordon runfor a single command on a server or in CI. - Our server knows the Telegram chat id, a SHA-256 hash of each computer's secret, with the IP reputation watch on, the VPN address when it changes and every 6 hours, only to check it against blocklists and not stored, from 1.4.5 a hash of the computer's system ID (hashed again on the server, so the same computer isn't counted as new under another account; the ID itself never leaves the computer), the computer's name, and - for the remote, while signed in - status, country, protected app names and weekly numbers, in memory, never IP addresses. It also keeps the last settings profile (no addresses), which alerts you turned off, statistics for Kordon's owner without IP addresses (which computers, by secret hash, checked in on which day and hour with the Kordon version and OS; how many are online each minute; counts of events by kind - sign ins, VPN and leak alerts by kind, Download clicks - not tied to people; individual activity records and per-minute samples are deleted after 60 days. Events without identifiers and hourly aggregates are kept for up to 400 days), support conversations (your Telegram @username, computer names, messages and files; closed ones are deleted after 90 days) and a sign in link while it's valid (15 minutes). Kordon's server runs on its own. Sign in, the remote and alerts never get your IP: requests reach them through kordon.tech (older builds use efimovdev.ru), with no access log for Kordon; rate limiting lives in nginx memory only. Only our checks
ip.kordon.techandstun.kordon.techsee the address - to say it back to you; they keep no log and store it nowhere. The DNS checkdns.kordon.technever sees your IP at all: your DNS server (the provider's, the VPN's or a public one) is what asks it, and it only says that server's address back. - Sign in: an Ed25519-signed ticket from the server, valid 7 days, refreshed every 6 hours, checked against a key built into the app.
- Updates:
SHA256SUMS.txtis signed with an Ed25519 key only the owner holds; Kordon installs nothing without a valid signature, even if the GitHub account were taken over. Every release is built on GitHub Actions, not on someone's computer. macOS builds are Developer ID signed; Apple's notarization comes with the next version. Verify a release yourself (OpenSSL 3):
printf -- '-----BEGIN PUBLIC KEY-----\nMCowBQYDK2VwAyEAV0AkZc32DAnaNF2S9eJL+jsWdLjlSnLwAdxmysIs3MQ=\n-----END PUBLIC KEY-----\n' > kordon-update.pem base64 -d < SHA256SUMS.txt.sig > SHA256SUMS.sig.bin openssl pkeyutl -verify -pubin -inkey kordon-update.pem -rawin -in SHA256SUMS.txt -sigfile SHA256SUMS.sig.bin shasum -a 256 -c SHA256SUMS.txt --ignore-missing
- Report a vulnerability in the bot @kordon_security_bot (Support → Write). Please don't publish details before a fix is out; we answer within 72 hours.
Добровольные проверка и диагностика (готовится)
Проверка запускает одноразовый процесс. Изолированный Guard может приостановить только его; список рабочих процессов пользователя в тест не передаётся. Секрет входа не попадает в дочерний процесс: через stdin он получает отдельный токен на 3 минуты. Наблюдатель хранит только временные счётчики без IP. Результат подтверждает измеренную паузу и возобновление, а не отсутствие всех сетевых утечек и не защиту от блокировки аккаунта.
Диагностика отправляется только после просмотра и подтверждения точного JSON. Сервер отклоняет неизвестные поля, связывает отчёт с вошедшей установкой, ограничивает частоту, удаляет отчёты после 14 дней и позволяет владельцу удалить их раньше. Идентификатор отчёта сам по себе не даёт права чтения: поддержке нужна проверка владельца Telegram, установке - собственный секрет. Повтор той же отправки не создаёт дубликат. Локальный журнал и переписка в облако не загружаются.
TIN 730210106410 · OGRNIP 325730000086336
Email: devefimov@gmail.com · Phone: +7 (993) 099-36-23 · Support: @kordon_security_bot, daily 10:00-20:00 Moscow time