Tech Help

Wifi Beacons      This was an adventure.      Some back story first, when any device you have that listens for connections for wifi wants to connect to something, even when the access point it's trying to reach isn't there, the default tends to be probe for it. That's basically a small little radio in your phone, car, watch, light bulb, whatever saying publicly "YO! IS MY WIFI OUT THERE? WHAT ABOUT THIS OTHER ONE!!?!? NOT THAT ONE EITHER, OKAY NEVER MIND!". When doing wireless network pentesting, it's pretty common to use tools like kismet or airodump and include these beacons, in part to flag what's relating to what network you're targeting / have permission to access and in part to see if network devices in scope are connecting so you can redirect their traffic to a fake network as part of the test. But I came up with an idea a while back due to having a scan going at my house and I kept seeing these "ROPD-CAR4" (fake, but something like th...

The problem      I'm not really big on endorsing services, but I found DocuSeal over the last weekend and thought I'd share some experiences with it. I've been discussing a lot lately about how people should have some basic sign before work performed stuff, even for contractors and individually owned companies so they aren't getting screwed over (there's a lot of ways to do this to someone). Personally I'm using obsidian and it's print to pdf thing to create and edit (if needed) templates for various forms and reporting situations. Platforms like google forms is nice for just generic information filled out, but doesn't do any digital signatures or provide any proofs that the data wasn't tampered/altered/or faked. So I've been trying to find a solution to suggest to others that doesn't completely suck or cost an arm and a leg.      But before I get to how DocuSeal seems to work for me on that, lets discuss this for a second so you understand t...

Weird Routes?  History:      So I wasn't really sure how to start this post, but I guess some back story. Many in the IT world know consumer ISPs (internet service providers) like ATT, Comcast, Charter (now spectrum), all have a weird history of "you can't prove there's a problem because we don't escalate it properly, now you're stuck with this while we replace your router 200 times because it can't be on us" sort of problems. I switched to spectrum because in my area its the only non-att fiber lines, and ATT couldn't tell me why my router had an ssh server listening on it. They couldn't think it was compromised or could be compromised, they couldn't tell me anything they just replaced it. Then replaced it again. Then again. After 2 years of doing that, I just had enough. Later that year after leaving ATT, https://en.wikipedia.org/wiki/Salt_Typhoon . But sadly, despite my contempt for ATT by this point, this post isn't about them. More ...

Snooze Words: Documentation      In our quest to automate the dumb stuff, we tend to always leave it a huge pain in the butt to do documentation. Mostly cause some parts of documentation have to be customized and adjusted and trying to automate that we sometimes overengineer it. Without that, we get used to loading up MS Word or similar products and setting up the documents we need. Then along with services like docusign to get signatures for things like our Pentest MSA and Scoping documents, we can also automate the generation of reports. There's several tools out there for this, and I've experimented with making a few myself. For this example though I'm going to go through using obsidian as a grounds for our documentation and jupyter-lab as our pentesting platform.      To start with, I'm definitely gonna want to have a way to make a formalized document. Doc? PDF? Well I'm originally I went the doc route by using the python docx library. It worked, but wa...

Creating a testpage:      So, after taking some offensive javascript lessons, the bright idea came to mind that I should see what else I can make with it. I'd been playing with some ideas about dnsrebinding and using subdomains that resolve to internal ips as pivot points to point to private ips, and I'd found a way to sort through all the subdomains one at a time and try to resolve them. So I added that with other pre-existing knowledge. I have heard many times of people making javascript use websockets to then scan the network so I thought, pft, do you even need websockets for this?     Well, there's some problems. First of which, it seems the method of doing this waits until completion to move along. That will bog down most browsers. I was also trying to go off of an extremely large list of subdomains and literally all ports. So browser tab had to wait on (lots of ips) on (65550) ports. Terrible design, terrible idea, aaaaaand then came the weird part.  ...