Will OnlyFans being down due to the PHP vulnerability cause any ...

2026-10-21T17:08:54Z

Will OnlyFans being down due to the PHP vulnerability cause any significant impact?

sure, but the password isn't the date, and no one is ...

2026-10-13T14:26:23Z

In reply to nevent1q…pdj4
_________________________

sure, but the password isn't the date, and no one is unpacking the firmware, reversing that function in 5 minutes.

password isn't the date, it's derived from the date. I ...

2026-10-13T14:21:01Z

In reply to nevent1q…8qdd
_________________________

password isn't the date, it's derived from the date. I don't think any of the write ups provide enough detail to derive the algorithm, and by the time they'd published the vendor had pulled the firmware.

I've just published a new GitHub repo - pentesttools. ...

2026-04-04T14:28:04Z

I've just published a new GitHub repo - pentesttools. It's not exactly groundbreaking, but it speeds up my workflow massively.

As OT and maritime testers, we spend a lot of time walking around, plugging into networks, quickly getting orientated, and scanning safely. Every engagement is the same dance: configure an interface, set an IP, add a gateway, scan, move on to the next subnet. Repeat. When you're standing in an equipment room with a laptop balanced on one hand, every key press matters.

So I did something about it. I took about six months of my bash history, anonymised it, and fed it through our ChatGPT instance to analyse what commands I was running most frequently and where I was losing time. The patterns were obvious.

First thing you do when you plug in is set your active interface:

setif eth1

Every command from that point on knows which interface to use. No more typing "dev eth1" over and over. Adding a default gateway goes from:

sudo ip route add default via 192.168.1.254 dev eth1

To:

setgw 192.168.1.254

Searching for files on shares or extracted firmware goes from:

find . -iname "*config*" 2>/dev/null

to just:

f config

The big one - connecting to a new network, scanning it, and getting results:

sudo ip addr flush dev eth1
sudo ip addr add 192.168.8.100/24 dev eth1
sudo ip link set eth1 up
sudo ip route add default via 192.168.8.1 dev eth1
sudo arp-scan 192.168.8.0/24 > arp_scan.raw
grep -oE '\b([0-9]{1,3}\.){3}[0-9]{1,3}\b' arp_scan.raw > hosts.txt
sudo nmap -p 22,80,443 -sV --open -iL hosts.txt

Seven commands. Now:

recon 192.168.8.0/24 192.168.8.1 -p safe

One line. Configures the interface, ARP scans, extracts live hosts, and runs nmap with a safe profile. All timestamped and logged.

I also spent time on the bash prompt. Screenshots are evidence on engagements, so ours shows the date, time, IP, and interface:

┌──(04-04-2026 14:32 192.168.8.100@eth1)-[~/client/scans]

Every screenshot instantly tells you what network you were on and when. No more guessing when writing the report weeks later.

Each terminal also gets its own persistent history file, merged into a global log. histall nmap searches across all terminals.

33 scripts in total covering network config, scanning, credential logging, firewall rules, file transfers, and more. Things like blockport ot to instantly firewall OT/ICS ports, or loot to log credentials consistently.

It's also got typo aliases, because if you've never typed "namp" instead of "nmap" at 2am, you haven't been pentesting long enough.

Installs in one command. Designed for disposable VMs - spin up, install, test, destroy.

https://github.com/cybergibbons/pentesttools

They have very strange cats in Richmond. ...

2025-11-26T19:33:16Z

They have very strange cats in Richmond.

Nostr notes by cybergibbons

Will OnlyFans being down due to the PHP vulnerability cause any ...

sure, but the password isn't the date, and no one is ...

password isn't the date, it's derived from the date. I ...

I've just published a new GitHub repo - pentesttools. ...

They have very strange cats in Richmond. ...