# always find (blogs) — RSS Amplifier Recent posts from the 2 feeds in the RSS Amplifier directory that cover always find. Page: Feed: --- ## [Release 1.6.14](https://narrafirma.com/2026/06/22/release-1-6-14/) _2026-06-22 · Cynthia Kurtz · NarraFirma_ This minor NarraFirma release adds one bit of functionality and makes a few visual tweaks. An off-line NarraFirma journal NarraFirma began its life as a write-it-yourself notebook. When I finished the third edition of Working with Stories in 2014, I wanted to write something that would help people think through their PNI projects by answering \[ \] ## [Release 1.6.13](https://narrafirma.com/2026/04/27/release-1-6-13/) _2026-04-27 · Cynthia Kurtz · NarraFirma_ This minor NarraFirma release is a very minor one. It does only two things: It fixes two mistakes I made while getting the 1.1.12 release ready (the version was wrong in the WordPress readme file, and the tested up to WordPress version was also wrong). It improves the description of NarraFirma on the GitHub readme \[ \] ## [Release 1.6.12](https://narrafirma.com/2026/04/27/release-1-6-12/) _2026-04-27 · Cynthia Kurtz · NarraFirma_ This minor NarraFirma release contains one speed improvement and several interface improvements. Better loading speed The fees of the hosting provider we have been using to host all of our web sites for two decades have been going up and up. So we decided to save some money by moving narrafirma.com (with its demo version \[ \] ## [BSidesSF 2026: rugdoctor - a broken JIT compiler pwn challenge](https://www.skullsecurity.org/2026/bsidessf-2026-rugdoctor-a-broken-jit-compiler-pwn-challenge) _2026-03-30 · ron · SkullSecurity Blog_ This is a write-up for rugdoctor, which is a JIT compiler with a 16-bit integer overflow. The integer overflow allows you to jump to the middle of other instructions, to run small bits of code in between other instructions. As always, you can find copies of the binaries, containers, and full solution in our GitHub repo! ## [BSidesSF 2026: read(write(call))me - progressive pwn challenges](https://www.skullsecurity.org/2026/bsidessf-2026-read-write-call-me-progressive-pwn-challenges) _2026-03-30 · ron · SkullSecurity Blog_ This is a write-up for three “pwn” challenges - readwritecallme, readwriteme, readme. They’re all pretty straight forward, and designed to teach a specific exploit type: how to exploit an arbitrary memory write. All three challenges let you read arbitrary memory, and the first two additionally let you write to arbitrary memory. The final one (readme) only lets you read memory, but it has a buffer… ## [BSidesSF 2026: nameme - a DNS-based pwn challenge](https://www.skullsecurity.org/2026/bsidessf-2026-nameme-a-dns-based-pwn-challenge) _2026-03-30 · ron · SkullSecurity Blog_ This is a challenge I’ve been considering making forever. It’s possible I’ve already made it, even, it’s one of those things that appeals to my brain! As always, you can find copies of the binaries, containers, and full solution in our GitHub repo! ## [BSidesSF 2026: miscellaneous challenges (if-it-leads, gitfab, jengacrypt)](https://www.skullsecurity.org/2026/bsidessf-2026-miscellaneous-challenges-if-it-leads-gitfab-jengacrypt-) _2026-03-30 · ron · SkullSecurity Blog_ This will be a write-up for the three shorter / more miscellaneous challenges I wrote: if-it-leads gitfab jengacrypt As always, you can find copies of the binaries, containers, and full solution in our GitHub repo! ## [Release 1.6.11](https://narrafirma.com/2025/07/28/release-1-6-11/) _2025-07-28 · Cynthia Kurtz · NarraFirma_ This minor NarraFirma release contains several slight prettifications. All of them were occasioned by my going over all the images from NarraFirma in my new edition of Working with Stories to make sure they are clear and understandable. I didn t like how some of the graph fonts and spacings looked in the book, so I \[ \] ## [Release 1.6.10](https://narrafirma.com/2025/07/10/release-1-6-10/) _2025-07-10 · Cynthia Kurtz · NarraFirma_ This minor NarraFirma release adds a few new features and fixes a few bugs. Your win-win proposal(s) I realized that NF did not give you an opportunity to write and record win-win proposals: things you want to say to potential project participants. So I added a section with some questions to help you do that. \[ \] ## [BSidesSF 2025: Miscellaneous challenges](https://www.skullsecurity.org/2025/bsidessf-2025-miscellaneous-challenges) _2025-04-27 · ron · SkullSecurity Blog_ In this post, I’m going to do write-ups for a few challenges that don’t really meaningfully categorize. As usual, you can find the code and complete solutions on our GitHub repo! ## [Licensed Dispensaries, Pay with Crypto (Sponsored)](https://crawlproof.com/a/oCcTj11GD27e) _2025-04-27 · **Sponsored**_ Search verified licensed dispensaries and pay with Bitcoin, Lightning, or stablecoins. ## [BSidesSF 2025: 101 Challenges](https://www.skullsecurity.org/2025/bsidessf-2025-101-challenges) _2025-04-27 · ron · SkullSecurity Blog_ I wrote a wholllle pile of 101 web challenges this year, which are ultimately going to be adapted for a workshop I’m giving at NorthSec in Montreal next month. I’m not going to spend a ton of time on them, I’ll just give the solutions quickly. As usual, you can find the code and complete solutions on our GitHub repo! And, if these are particularly interesting to you, come see me in Montreal! ## [BSidesSF 2025: accan and drago-daction: pwn your own memory](https://www.skullsecurity.org/2025/bsidessf-2025-accan-and-drago-daction-pwn-your-own-memory) _2025-04-27 · ron · SkullSecurity Blog_ If you read my bug-me write-up or my Linux process injection blog, you may be under the impression that I’ve been obsessed with the ability of Linux processes to write to their own memory. These challenges are no exception! You can download source and the challenge (including solutions) here (acaan) and here (drago-daction). ## [BSidesSF 2025: bug-me (hard reversing challenge)](https://www.skullsecurity.org/2025/bsidessf-2025-bug-me-hard-reversing-challenge-) _2025-04-27 · ron · SkullSecurity Blog_ Every year, I make a list of ideas and it contains the same thing: “process that debugs itself”. It’s from a half-remembered Windows challenge I solved when I was very new to CTFs. I’m obsessed with that concept, having messed with writing debuggers a few times (including Mandrake), and blogging about process injection. You’ll find a few challenges influenced by that those concepts thie yar, but… ## [Release 1.6.9](https://narrafirma.com/2025/03/31/release-1-6-9/) _2025-03-31 · Cynthia Kurtz · NarraFirma_ This very minor NarraFirma release does nothing but fix some warnings I got from WordPress when I released version 1.6.8. As always, if you find any bugs or find anything in NF confusing or hard to use please tell me on the GitHub issues page. ## [Release 1.6.8](https://narrafirma.com/2025/03/31/release-1-6-8/) _2025-03-31 · Cynthia Kurtz · NarraFirma_ This very minor NarraFirma release adds a notes field to each question category (about each group s status, ability, expectations, and feelings) on the Describe participant groups page. As always, if you find any bugs or find anything in NF confusing or hard to use please tell me on the GitHub issues page. ## [goto-zero: An extended intro to solving stack overflow CTF challenges](https://www.skullsecurity.org/2024/goto-zero-a-fake-ctf-challenge-to-show-off-something) _2024-12-10 · ron · SkullSecurity Blog_ Hey all! My husband’s company recently did an internal (commercial) CTF, and as a CTF nerd I got suckered into helping him. I thought one of the challenges had a pretty interesting solution - at least, something I hadn’t done before - and I thought I’d do a little write-up! Because it’s a commercial CTF, I wrote my own vulnerability binary, which you can grab here. It’s much, much simpler, but has…