Binwalk assumed the following chunk was related to some LZMA compressed data
-because of the signature 5d 00 00 00 02. This signature might
+because of the signature 5d 00 00 00 02. This signature might
vary depending
-on the compression level used, but apparently it always start with 5d 00 00.
+on the compression level used, but apparently it always start with 5d 00 00.
Here is the start of the compressed data:
The -e (--extract) flag, will extract the files identified during a
-signature scan and the -M (--matryoshka) flag will perform this
+
The -e (--extract) flag, will extract the files identified during a
+signature scan and the -M (--matryoshka) flag will perform this
extraction recursively. There is also another really useful option in Binwalk
which allows an entropy analysis of the file. This can be helpful when
Binwalk
@@ -124,7 +126,7 @@
Using Binwalk
For example, taking a step back, if we used Binwalk extraction only once, we
would find a file named 40 (this number refers to its offset in hexadecimal).
-Using Binwalk with the -E (--entropy) flag in this file will pop the
+Using Binwalk with the -E (--entropy) flag in this file will pop the
following line chart (generated with pyqtgraph).
@@ -137,7 +139,7 @@
Using Binwalk
The signature scan for this file would give us the following output:
-
$ binwalk 40
+
$ binwalk 40
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
2658360 0x289038 Linux kernel version "2.6.21 (root@linux-qxix)
@@ -165,7 +167,7 @@
Using Binwalk
course, we could have simply extracted everything with just one command like
the following demonstration:
-
$ binwalk -eM fw_NPLUG_1_0_0_14.bin
+
$ binwalk -eM fw_NPLUG_1_0_0_14.bin
$ cd fw_NPLUG_1_0_0_14.bin.extracted/_40.extracted/_2EB000.extracted/cpio-root/
$ tree
.
@@ -426,7 +428,11 @@
There’s no way one can avoid social media completely. We are social creatures.
+Even if you close all your accounts and remove all the apps, you would still be
+influenced by other people’s behaviors and opinions, and those probably got a
+high load of influence from social media and so on.
+
+
You can indeed make money producing content online. It is also true that social
+media platforms can boost your reach. However, the majority of the population is
+just consuming and creating poor content that will never lead to a financial
+reward.
+
+
I would consider myself in the above situation. I’m not in a fair trade with
+social media. Not that I ever felt I could be. But the fear of missing out makes
+me play the game without even thinking about it.
+
+
Most of the value generated from our actions is turned into revenue for the big
+techs. In exchange for that, you will be gifted with a subtle dependency on the
+feedback you could receive if you saw something good enough.
+
+
If you can’t escape from it, maybe it’s a good idea to spend some time
+implementing filters to avoid the consumption of unhealthy content. You need to
+feed yourself, just not with junky food.
+
+
+
+
+
+
+
+
+
+
+
diff --git a/_posts/2021-07-31-wildcard-subdomain-enum.md b/_posts/2021-07-31-wildcard-subdomain-enum.md
new file mode 100644
index 0000000..023a0f4
--- /dev/null
+++ b/_posts/2021-07-31-wildcard-subdomain-enum.md
@@ -0,0 +1,67 @@
+---
+layout: post
+title: 'Subdomain enumeration with wildcard records '
+date: 2021-07-31 13:49:00 -0300
+comments: true
+categories: footprinting, subdomain, dns
+---
+
+**TL;DR**
+
+Enumerating subdomains with wildcard records is tricky but not impossible, here
+are some tips. Also, don't trust wildcards as a security mechanism for hiding
+sensitive apps.
+
+# The problem
+
+If you did some subdomain brute-force enumeration in the wild you already
+bumped into a record that resolves for any type of prefix. This is called a
+wildcard record and it can be configured by inserting a record entry with a
+label "**\***". This record will also resolve for other sublevels unless it is
+inhibited by another record entry.
+
+Many companies use wildcard records as part of their architecture. A well-known
+example is Slack which uses it for their workspaces. For example, today I asked
+my favorite DNS server to resolve the following records and got the same IP
+address:
+
+```
+shopify.enterprise.slack.com 18.231.0.250
+enterprise.slack.com 18.231.0.250
+big-name-non-existent.slack.com 18.231.0.250
+```
+
+In this case you might conclude that there is a wildcard record
+**\*.slack.com** and maybe we should ignore this domain in your subdomain
+enumeration. However, you could end up missing something like
+**status.slack.com** which does not resolve to this address. Instead it has a
+CNAME pointing to another infrastructure that could be interesting to you.
+
+It is curious how often subdomain enumeration tools mess up or do not handle
+this kind of behaviour. Many times the wildcard records are just dropped
+without any further check. The problem is that you might lose some interesting
+apps by discarding them .
+
+With that in mind, adding a wildcard record can be a tempting strategy to hide
+your own services like a needle in the haystack. I can't blame anyone for doing
+that, but just keep in mind that this is not going to save you for long.
+
+# Finding interesting stuff
+
+Thinking about how to make a better reconnaissance one could try to overcome
+this problem by treating enumeration in wildcard records differently. The
+response returned by the wildcard could be stored (sorted if it is multiple
+entries) and every subsequent DNS response would be compared with this one.
+Everytime we find a new response it would be saved in a map structure.
+
+This would make sure we have at least one subdomain that points to that new
+location that we found. However, *the world ain't all sunshine and rainbows*
+and we could obviously have a different application sitting on a machine that
+will only show up when we set a specific Host header in the HTTP request.
+
+Therefore, this is just something you could use to have more places to look for
+security vulnerabilities. There are many other more edgy cases (for example
+when including CNAME) that can happen when trying to find assets using DNS. I
+hope I can dig into that more in future posts.
+
+Do you have any tips for finding apps on records with wildcard?
diff --git a/_posts/2022-12-26-the-social-media-trap.md b/_posts/2022-12-26-the-social-media-trap.md
new file mode 100644
index 0000000..452d608
--- /dev/null
+++ b/_posts/2022-12-26-the-social-media-trap.md
@@ -0,0 +1,29 @@
+---
+layout: post
+title: The social media trap
+date: 2022-12-26 21:32:00 -0300
+comments: true
+categories:
+---
+
+There's no way one can avoid social media completely. We are social creatures.
+Even if you close all your accounts and remove all the apps, you would still be
+influenced by other people's behaviors and opinions, and those probably got a
+high load of influence from social media and so on.
+
+You can indeed make money producing content online. It is also true that social
+media platforms can boost your reach. However, the majority of the population is
+just consuming and creating poor content that will never lead to a financial
+reward.
+
+I would consider myself in the above situation. I'm not in a fair trade with
+social media. Not that I ever felt I could be. But the fear of missing out makes
+me play the game without even thinking about it.
+
+Most of the value generated from our actions is turned into revenue for the big
+techs. In exchange for that, you will be gifted with a subtle dependency on the
+feedback you could receive if you saw something good enough.
+
+If you can't escape from it, maybe it's a good idea to spend some time
+implementing filters to avoid the consumption of unhealthy content. You need to
+feed yourself, just not with junky food.
diff --git a/_site/2019/04/01/re-wireless-repeater.html b/_site/2019/04/01/re-wireless-repeater.html
index 4387e18..853bfdc 100644
--- a/_site/2019/04/01/re-wireless-repeater.html
+++ b/_site/2019/04/01/re-wireless-repeater.html
@@ -2,9 +2,9 @@
-
+
Reverse engineering a wireless repeater - Part I | patrickrbc
-
+
@@ -14,8 +14,10 @@
+
+
+{"headline":"Reverse engineering a wireless repeater - Part I","url":"http://localhost:4000/2019/04/01/re-wireless-repeater","dateModified":"2019-04-01T17:21:00-03:00","datePublished":"2019-04-01T17:21:00-03:00","mainEntityOfPage":{"@type":"WebPage","@id":"http://localhost:4000/2019/04/01/re-wireless-repeater"},"description":"Do you have an old router left behind in your room? Ever wondered how it really works inside? Sit tight and get ready, because this is going to be a series of blog posts about reverse engineering a wireless repeater. The methodology here can be applied to other IoT devices.","@type":"BlogPosting","@context":"https://schema.org"}
-
+
@@ -14,8 +14,10 @@
+
+
+{"headline":"Cryptopals: The basics","url":"http://localhost:4000/2019/04/06/cryptopals-the-basics","dateModified":"2019-04-06T16:42:00-03:00","datePublished":"2019-04-06T16:42:00-03:00","mainEntityOfPage":{"@type":"WebPage","@id":"http://localhost:4000/2019/04/06/cryptopals-the-basics"},"description":"If you have any kind of interest in crypto you should probably check this out. Recently, I started doing the Cryptopals, which are a series of cryptography challenges created by the formerly Matasano Security team. They are a collection of 48 exercises divided in 8 sets. I have just finished the first set but I can guarantee you that it was already a lot of fun and learning.","@type":"BlogPosting","@context":"https://schema.org"}
Reverse engineering a wireless repeater - Part II | patrickrbc
-
+
@@ -14,8 +14,10 @@
+
+
+{"headline":"Reverse engineering a wireless repeater - Part II","url":"http://localhost:4000/2019/06/01/re-wireless-repeater-2","dateModified":"2019-06-01T21:25:00-03:00","datePublished":"2019-06-01T21:25:00-03:00","mainEntityOfPage":{"@type":"WebPage","@id":"http://localhost:4000/2019/06/01/re-wireless-repeater-2"},"description":"This is the second part of a series of posts about reverse engineering a wireless repeater. Before reading this you might want to take a look at the first part, where I introduced the subject and explained how to gather some information without digging into the hardware. If you still haven’t downloaded the firmware of our target device you can get it here.","@type":"BlogPosting","@context":"https://schema.org"}
diff --git a/_site/2022/12/26/the-social-media-trap.html b/_site/2022/12/26/the-social-media-trap.html
new file mode 100644
index 0000000..3c37bff
--- /dev/null
+++ b/_site/2022/12/26/the-social-media-trap.html
@@ -0,0 +1,196 @@
+
+