<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Mcr on BIFIT Mitigator</title>
    <link>https://docs.mitigator.ru/v26.04/en/tags/mcr/</link>
    <description>Recent content in Mcr on BIFIT Mitigator</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language><atom:link href="https://docs.mitigator.ru/v26.04/en/tags/mcr/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Example: MCR UDP</title>
      <link>https://docs.mitigator.ru/v26.04/en/kb/bpf/tutorial/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.mitigator.ru/v26.04/en/kb/bpf/tutorial/</guid>
      <description>This is a step‑by‑step example of how to write an MCR countermeasure with UDP authentication (protocol description) to get hands‑on experience with BPF countermeasure programming. The final program will be under 100 lines of code.
You will need:
MITIGATOR v20.06 or higher. Ability to run commands from the terminal. Basic knowledge of the C language (explanations will be provided as we go). Understanding that packets have protocols, headers, and payloads. Environment Setup Any operating system will work, but Linux is recommended.</description>
    </item>
    <item>
      <title>MITIGATOR Challenge Response</title>
      <link>https://docs.mitigator.ru/v26.04/en/integrate/mcr/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.mitigator.ru/v26.04/en/integrate/mcr/</guid>
      <description>Tip This describes the MITIGATOR Challenge Response (MCR) protocol for developers of external systems. The MCR countermeasure is described in the built-in help.
MITIGATOR Challenge Response (MCR) is a protocol for IP authentication on MITIGATOR. The protocol can be implemented both by a protected application and separately, for example, when a game launcher is being checked, and game traffic is passed. The program that implements the protocol and passes the test is called the client (in the example above, the client is the launcher).</description>
    </item>
  </channel>
</rss>