<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Network-Fingerprinting on Netacoding | Cybersecurity, Assembly &amp; Network Research</title>
    <link>https://netacoding.com/tags/network-fingerprinting/</link>
    <description>Recent content in Network-Fingerprinting on Netacoding | Cybersecurity, Assembly &amp; Network Research</description>
    <image>
      <title>Netacoding | Cybersecurity, Assembly &amp; Network Research</title>
      <url>https://netacoding.com/img/logo-netacoding.png</url>
      <link>https://netacoding.com/img/logo-netacoding.png</link>
    </image>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 24 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://netacoding.com/tags/network-fingerprinting/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Windows tcpip.sys ICMP Timestamp Bug: EnableICMPTimestampRep=0 Registry Bypass &amp; RFC 792 Violation | Kernel RE</title>
      <link>https://netacoding.com/posts/windows-icmp-timestamp-bugs/</link>
      <pubDate>Fri, 24 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://netacoding.com/posts/windows-icmp-timestamp-bugs/</guid>
      <description>EnableICMPTimestampRep=0 does not suppress ICMP Timestamp Replies (Type 14) on Windows 11. Ghidra RE of tcpip.sys 10.0.26100.8457 confirms Ipv4pHandleTimestampRequest generates T14 unconditionally, plus a second bug: Receive/Transmit timestamps written little-endian in violation of RFC 792. Only effective mitigation: WFP firewall rule.</description>
    </item>
    <item>
      <title>ICMP Timestamp Type 13/14 Linux Kernel Internals: RFC 792 Deviations &amp; ftrace Call Chain Analysis</title>
      <link>https://netacoding.com/posts/icmp-timestamp-internals/</link>
      <pubDate>Tue, 07 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://netacoding.com/posts/icmp-timestamp-internals/</guid>
      <description>Depth-8 ftrace analysis of icmp_timestamp() in the Linux kernel: full call chain from ip_rcv() to ICMP Type 14 reply generation, payload length threshold behavior, conntrack interaction, ts_ori unconditional echo across the full 32-bit range, and six documented deviations from RFC 792.</description>
    </item>
  </channel>
</rss>
