<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Posts on BarkBlog</title>
    <link>http://dogblog.pages.dev/posts/</link>
    <description>Recent content in Posts on BarkBlog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language><atom:link href="http://dogblog.pages.dev/posts/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>AWGG - Breaking Out</title>
      <link>http://dogblog.pages.dev/posts/a-wolf-gals-guide-breaking-out/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>http://dogblog.pages.dev/posts/a-wolf-gals-guide-breaking-out/</guid>
      <description>AWGG - Breaking Out Of Jail
So, you end up in a shell, and you realize you&amp;rsquo;re stuck in jail. What do you do now? You break out of course!
Step 1: Enumeration
The first thing you&amp;rsquo;ll want to do is basic enumeration. Start finding what binaries you have access to while &amp;ldquo;locked up&amp;rdquo;. At the very LEAST you&amp;rsquo;ll have access to shell one-liners, but any compilers, interpreters, or packages for other languages (gcc, python, lua, node, etc.</description>
    </item>
    
    <item>
      <title>AWGG - RF Hacking Recommendations</title>
      <link>http://dogblog.pages.dev/posts/a-wolf-gals-guide-rf-hacking-recommendations/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>http://dogblog.pages.dev/posts/a-wolf-gals-guide-rf-hacking-recommendations/</guid>
      <description>A Wolf Gal&amp;rsquo;s &amp;ldquo;Getting Started&amp;rdquo; Guide to RF Hacking for Dummies:
More and more people are wondering where I get my kit from, especially people wanting to break into infosec, so I&amp;rsquo;m putting this together to hopefully give some basic recommendations for intro wireless pentesting equipment. This is NOT a comprehensive list, nor is it the be-all-end-all of equipment either, but rather some tools I&amp;rsquo;ve used in my day-to-day doing wireless audits.</description>
    </item>
    
    <item>
      <title>Forensics homelabbing from an internet wolf</title>
      <link>http://dogblog.pages.dev/posts/reflections-on-forensics-labbing/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>http://dogblog.pages.dev/posts/reflections-on-forensics-labbing/</guid>
      <description>Reflections on Forensics Labbing
Lately I&amp;rsquo;ve been poking into DFIR and working on diversifying my skillset, part of that diversity is getting familiar with forensics. Working in offensive roles, I know what tracks I leave, and how to clean up my mess after, but what is interesting is all of the artifact we as attackers dont necessarily think about off-the-cuff.
Getting into things has been slow-rolling, as you step into this microculture of LEOs, Feds, and mom and pop consulting who&amp;rsquo;ve been using their tools for a very long time because they &amp;ldquo;just work&amp;rdquo;.</description>
    </item>
    
    <item>
      <title>Intro</title>
      <link>http://dogblog.pages.dev/posts/introduction/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>http://dogblog.pages.dev/posts/introduction/</guid>
      <description>Hello!
My name is Rey, and this blog is about my life experiences in tech. Many posts will be technical rambling, information security related issues, and deep dives into projects im working on, while others may be about the furry fandom, queer discovery, and my transition.
Here are a few of my socials that I&amp;rsquo;m most active on if you want to keep up with me!
BlueSky Mastodon Telegram A few interesting things about me!</description>
    </item>
    
    <item>
      <title>WOOF!</title>
      <link>http://dogblog.pages.dev/posts/wolfgame/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>http://dogblog.pages.dev/posts/wolfgame/</guid>
      <description>Woof, woof, woof! </description>
    </item>
    
  </channel>
</rss>
