Tech Help

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.  ...