<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet href="/rss/styles.xsl" type="text/xsl"?><rss version="2.0"><channel><title>codesecho — enterprise infrastructure, tested</title><description>Hands-on guides to enterprise infrastructure — MikroTik, Cisco, TIBCO and Unix. Real commands, real output, and what to do when reality does not match the vendor documentation.</description><link>https://codesecho.com/</link><language>en</language><lastBuildDate>Wed, 12 Aug 2026 23:11:21 GMT</lastBuildDate><item><title>CVE-2018-14847: Is Your MikroTik Still Backdoored?</title><link>https://codesecho.com/networking/cve-2018-14847-still-backdoored/</link><guid isPermaLink="false">NET-002</guid><description>Patching RouterOS never removed what the exploit left behind. Six commands that find the accounts, scripts and proxies that survived the upgrade.</description><pubDate>Wed, 12 Aug 2026 00:00:00 GMT</pubDate><category>Networking</category><category>mikrotik</category><category>routeros</category><category>cve</category><category>incident-response</category><category>security</category><author>Manoranjan Behera</author></item><item><title>MikroTik Security Hardening: 10 Checks Most People Miss</title><link>https://codesecho.com/networking/mikrotik-security-hardening-10-checks/</link><guid isPermaLink="false">NET-001</guid><description>Ten RouterOS defaults that stay enabled after a clean install, why an /export will never show them to you, and the exact command to close each one.</description><pubDate>Wed, 12 Aug 2026 00:00:00 GMT</pubDate><category>Networking</category><category>mikrotik</category><category>routeros</category><category>hardening</category><category>firewall</category><category>security</category><author>Manoranjan Behera</author></item></channel></rss>