<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Playbooks on original.flipster</title><link>https://originalflipster.com/playbooks/</link><description>Recent content in Playbooks on original.flipster</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026</copyright><lastBuildDate>Sun, 01 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://originalflipster.com/playbooks/index.xml" rel="self" type="application/rss+xml"/><item><title>My first Vibe (with success)</title><link>https://originalflipster.com/playbooks/my-first-vibe/</link><pubDate>Sun, 01 Mar 2026 00:00:00 +0000</pubDate><guid>https://originalflipster.com/playbooks/my-first-vibe/</guid><description>The internet is divided, one half has gone full-blown Coding Agent Mode, adamant not to touch any code ever again and the other half is skeptic AF and trying to convince everyone that AI generated code still mostly sucks. So, this is just me trying to see for myself and sharing my experience after my first actually successful result from Vibe Coding or Agentic Engineering or whatever.</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://originalflipster.com/playbooks/my-first-vibe/featured.webp"/></item><item><title>7 Commandments for a successful team of engineers</title><link>https://originalflipster.com/playbooks/7-commandments-successful-team/</link><pubDate>Thu, 01 Jan 2026 00:00:00 +0000</pubDate><guid>https://originalflipster.com/playbooks/7-commandments-successful-team/</guid><description>A great team of developers, engineers or tech teams in general runs on more than just code – it runs on shared principles, or call it culture if you will. Those are the factors that will determine whether a team will succeed, namely constantly deliver good results, or fail in the long run.</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://originalflipster.com/playbooks/7-commandments-successful-team/featured.png"/></item><item><title>What's Cracking? Oh, must be your KeePass password!</title><link>https://originalflipster.com/playbooks/kdbx-keepass-password-cracking/</link><pubDate>Mon, 08 Sep 2025 00:00:00 +0000</pubDate><guid>https://originalflipster.com/playbooks/kdbx-keepass-password-cracking/</guid><description>Recently, I found myself stumbling upon a &lt;code>.kdbx&lt;/code> (KeePass Database) file as part of a backup in a CTF and needed to crack the password to gain access to the secrets contained and consequently elevate my privileges. Problem was, that I couldn&amp;rsquo;t get the hash in the right format for cracking it with &lt;code>john&lt;/code>: &lt;code>unsupported database file version (4)&lt;/code>. So, I built &lt;code>keepass-rush&lt;/code> to do so myself.</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://originalflipster.com/playbooks/kdbx-keepass-password-cracking/featured.webp"/></item><item><title>Privilege Escalation via DPAPI</title><link>https://originalflipster.com/playbooks/dpapi-privilege-escalation/</link><pubDate>Mon, 01 Sep 2025 00:00:00 +0000</pubDate><guid>https://originalflipster.com/playbooks/dpapi-privilege-escalation/</guid><description>&lt;strong>DPAPI&lt;/strong> can be useful in situations when you got an initial foothold on a Windows host and are seeking to escalate your privileges. More specifically, we are talking a scenarios where your initial access user shares their home folder with a privileged account. This is a setup that is commonly found in Active Directory contexts, when a single person is operating with 2 distinct users, 1 for their everyday work and another one for dedicated administrative actions such as managing other users &amp;amp; groups that required elevated privileges.</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://originalflipster.com/playbooks/dpapi-privilege-escalation/featured.webp"/></item></channel></rss>