,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Sunday, July 31st 2022 - Consolas
'''''''''''''''''''''''''''''''''
So as I'm working through the PEN-200 and OSCP training, I'm finding that
much to my delight, I get to stay in the terminal most of the time. There
are only a few occasions where I need to reach for my mouse, and thats
when I have to perform browser related tasks such as using burp or 
Builtwith/Appalyzer plugins.

Burp is the big one. There are discovery scanners out there that can
parse httpd headers and give the same information as builtwith, as an
example. But burp I have yet to find an alternative for, and that honestly
is very surprising. 

So, I'm going to write one.

I'm not going to do it immediately, to do so would just be an excuse to 
procrastinate my studies. But when I'm done with this current course and
have the OSCP behind me I'm going to write a proxy/http request editor
in go. I have a good idea how it would be designed, architecturally. The
biggest hurdle would be learning go, and that's understandable. Why not
write it in a language I already know? Well, my first thought was C, as
is usual for me.

But I haven't worked in C in a few years, and I hate its "memory
management". Notice the sarcastic quotes.
Since I'm going to be refamiliarizing myself anyway, I think it's a
prime opportunity to learn a new language. Why go? Because rust is stop.

Enjoy that stupid little joke. See you guys tomorrow.

- diviniti