<?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>FTP on maxtsec</title><link>https://maxtsec.com/tags/ftp/</link><description>Recent content in FTP on maxtsec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 19 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://maxtsec.com/tags/ftp/index.xml" rel="self" type="application/rss+xml"/><item><title>OffSec Proving Grounds Practice - AuthBy Writeup</title><link>https://maxtsec.com/offsec-pg-authby-writeup/</link><pubDate>Tue, 19 May 2026 00:00:00 +0000</pubDate><guid>https://maxtsec.com/offsec-pg-authby-writeup/</guid><description>&lt;h1 id="offsec-proving-grounds-practice---authby-writeup"&gt;OffSec Proving Grounds Practice - AuthBy Writeup&lt;/h1&gt;
&lt;p&gt;This is my writeup for &lt;strong&gt;AuthBy&lt;/strong&gt;, a Windows machine from OffSec Proving Grounds Practice.&lt;/p&gt;
&lt;p&gt;I found this machine quite useful because the attack path was not just about scanning and running a public exploit. The chain started from &lt;strong&gt;FTP enumeration&lt;/strong&gt;, moved into credential discovery, then web access, initial foothold through a PHP reverse shell, and finally Windows privilege escalation.&lt;/p&gt;
&lt;p&gt;The overall attack path was:&lt;/p&gt;</description></item></channel></rss>