<?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 Daniel Vera on Medium]]></title>
        <description><![CDATA[Stories by Daniel Vera on Medium]]></description>
        <link>https://medium.com/@mezcalitodesoftware?source=rss-44c0f5a6f4ed------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*e9Rak2AwtstOKbSLEt7lYg@2x.jpeg</url>
            <title>Stories by Daniel Vera on Medium</title>
            <link>https://medium.com/@mezcalitodesoftware?source=rss-44c0f5a6f4ed------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 13:13:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mezcalitodesoftware/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[Simple yet effective Bash Obfuscator]]></title>
            <link>https://mezcalitodesoftware.medium.com/simple-yet-effective-bash-obfuscator-27fa3d974723?source=rss-44c0f5a6f4ed------2</link>
            <guid isPermaLink="false">https://medium.com/p/27fa3d974723</guid>
            <category><![CDATA[obfuscation]]></category>
            <category><![CDATA[tools]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[bash]]></category>
            <category><![CDATA[terminal]]></category>
            <dc:creator><![CDATA[Daniel Vera]]></dc:creator>
            <pubDate>Sun, 09 Feb 2025 00:29:50 GMT</pubDate>
            <atom:updated>2025-02-09T00:29:50.784Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*kV1UVuZbLoWqzxlF.jpg" /></figure><p><strong>Note:</strong> The steps described in this tutorial were applied on UNIX-based operating systems.</p><h3>Introduction</h3><p>In this guide, we’ll go through the process of creating your own Bash obfuscator. Obfuscation is the practice of deliberately making code harder to understand, often to protect intellectual property or to deter reverse engineering. We’ll explore several techniques for achieving this goal using Bash scripts.</p><p>Download the source code before continuing:</p><pre>#!/bin/bash<br><br>output=$3<br>filex=tmpmainfile.sh<br>echo $&quot;$(cat $2)&quot; &gt; $filex<br>banner=$(figlet &quot;$1&quot; | gzip | base64)<br>banner=&quot;base64 -d &lt;&lt;&lt;\&quot;$banner\&quot; | gunzip&quot;<br>key=&quot;# ===BANNER===&quot;<br>perl -i -pe  &quot;s@$key@$banner@gms&quot; ${filex}<br><br>currentDir=$(dirname &quot;$0&quot;)<br>cp $currentDir/template.sh $output<br><br>funcaname=&quot;xf&quot;$(dbus-uuidgen)<br>barridoName=&quot;b&quot;$(dbus-uuidgen)<br>markerName=&quot;m&quot;$(dbus-uuidgen)<br>markerNameVar=&quot;m&quot;$(dbus-uuidgen)<br><br>echo -n $markerNameVar&quot;=\$(awk &#39;/^___&quot;$markerName&quot;___/ {print NR+1; exit 0; }&#39; \&quot;\${0}\&quot;);&quot; &gt;&gt; $output<br>echo -n $barridoName&quot;=\$(tail -n+\${&quot;$markerNameVar&quot;} \&quot;\${0}\&quot;);&quot; &gt;&gt; $output<br><br>echo &quot;&quot; &gt;&gt; $output<br>echo &#39;function &#39;$funcaname&#39;(){&#39; &gt;&gt; $output<br>echo &#39;echo $(base64 -d &lt;&lt;&lt; &quot;$1&quot;| gunzip);&#39; &gt;&gt; $output<br>echo &#39;}&#39; &gt;&gt; $output<br><br>REGX=()<br>IN=$(cat $filex)<br>while IFS=$&#39;\n&#39; read -ra ADDR; do<br>  for i in &quot;${ADDR[@]}&quot;; do<br>    varxxa=&quot;X02D&quot;$(dbus-uuidgen)<br>    cz=$(echo $&quot;$i&quot; | tr -d &#39;\0&#39;| gzip| base64 )<br>    echo -n $varxxa&quot;=\$($funcaname \&quot;$cz\&quot;);&quot; &gt;&gt; $output<br>    REGX+=($varxxa)<br>  done<br>done &lt;&lt;&lt; &quot;$IN&quot;<br><br>echo -n $&quot;pbv921=\$(eval \&quot;echo \$\\\&quot;\$&quot;$barridoName&quot;\\\&quot;\&quot;);&quot; &gt;&gt; $output<br>echo -n &quot;b17320=\&quot;\$(cat \${0})\&quot;;&quot; &gt;&gt; $output<br>echo -n &quot;echo \$\&quot;\$pbv921\&quot; &gt; \${0};&quot; &gt;&gt; $output<br>echo -n &quot;echo \$\&quot;\$(\${0} \${@})\&quot; &amp;&amp; echo \$\&quot;\$b17320\&quot; &gt; \${0};&quot; &gt;&gt; $output<br><br>echo &quot;exit 0;&quot;  &gt;&gt; $output<br>echo &quot;___&quot;$markerName&quot;___&quot; &gt;&gt; $output<br>for i in &quot;${REGX[@]}&quot;; do<br>  echo -n &quot;$&quot;$i&quot;\$z&quot; &gt;&gt; $output<br>done<br>echo -n &quot;\&quot;\&quot;&quot; &gt;&gt; $output<br>rm $filex &amp;2&gt;/dev/null</pre><pre>#!/bin/bash<br><br>z=&quot;<br><br>&quot;;</pre><h3>Motivation</h3><p>Some time ago, I found myself in need of creating an obfuscator that would allow me to run Bash applications on a server without the source code being obvious or easy to understand for end users. It wasn’t a cryptographic innovation, but it served my purpose.</p><p>There are some good open source alternatives that can be used to obfuscate scripts, but they didn’t work for me personally. Either they were C compilers that require compilation on the target machine, or the Bash obfuscators I found didn’t respect line breaks, spaces, etc.</p><h3>Obfuscators</h3><p>An obfuscator is a program that takes the contents of a file (usually source code) and rewrites it in a way that makes it difficult for the human eye to understand, but still executable or interpretable by the machine. I should clarify that this degrades the performance of your application, since certain portions of the code need to be decrypted and then interpreted. In addition, it tends to be insecure because it requires invoking the “eval” function or method, and in most programming languages ​​there is the premise: “eval is dangerous”, since you expose yourself to serious security flaws if you do not know what you are doing.</p><p>Example of obfuscation in JavaScript using: <a href="https://www.obfuscator.io/">https://www.obfuscator.io/</a></p><pre>// Paste your JavaScript code here<br>function hi() {<br>console.log(&quot;Hello World!&quot;);<br>}<br>hi();</pre><p>Result</p><pre>function _0x3ec8(_0x296d7c,_0x2693b2){var _0x5613e7=_0x5613();return _0x3ec8=function(_0x3ec8e4,_0x401d60){_0x3ec8e4=_0x3ec8e4-0x6d;var _0x19ddc2=_0x5613e7[_0x3ec8e4];return _0x19ddc2;},_0x3ec8(_0x296d7c,_0x2693b2);}(function(_0x41232c,_0xebe4dc){var _0x3342e0=_0x3ec8,_0x40c3c7=_0x41232c();while(!![]){try{var _0x32d38b=-parseInt(_0x3342e0(0x6e))/0x1+parseInt(_0x3342e0(0x74))/0x2*(-parseInt(_0x3342e0(0x77))/0x3)+-parseInt(_0x3342e0(0x70))/0x4+-parseInt(_0x3342e0(0x76))/0x5*(parseInt(_0x3342e0(0x73))/0x6)+-parseInt(_0x3342e0(0x75))/0x7*(-parseInt(_0x3342e0(0x72))/0x8)+parseInt(_0x3342e0(0x6f))/0x9+parseInt(_0x3342e0(0x71))/0xa;if(_0x32d38b===_0xebe4dc)break;else _0x40c3c7[&#39;push&#39;](_0x40c3c7[&#39;shift&#39;]());}catch(_0xf65114){_0x40c3c7[&#39;push&#39;](_0x40c3c7[&#39;shift&#39;]());}}}(_0x5613,0x59530));function hi(){var _0xb4568e=_0x3ec8;console[&#39;log&#39;](_0xb4568e(0x6d));}function _0x5613(){var _0x3f2f47=[&#39;1774328LjslCb&#39;,&#39;12zuPtpB&#39;,&#39;86006GRGAVr&#39;,&#39;14XwSEoS&#39;,&#39;1291735TXNvTp&#39;,&#39;15KiTYuV&#39;,&#39;Hello\x20World!&#39;,&#39;655804PBgVaU&#39;,&#39;2602566hXhSme&#39;,&#39;882660GBsfGs&#39;,&#39;12412940HmFyOD&#39;];_0x5613=function(){return _0x3f2f47;};return _0x5613();}hi();</pre><h3>Creating your own obfuscator in Bash</h3><p><strong>Note:</strong> Never use eval, it is very dangerous. Do not use this script in production, as it is extremely unsafe. Only proceed if you know what you are doing or understand the risks.</p><p>The obfuscator will read the target script, split the content into blocks, generate variables, perform some sort of compression, and add redundancy. When our obfuscated script runs, it will generate the clear version in the /tmp directory, then load that version into memory by interpreting the generated sections, and finally delete the generated file. Finally, we’ll add a nice banner to style our obfuscator.</p><p>What makes an obfuscator an obfuscator:</p><p>Generates long, meaningless variable names, as is often done with binary, hex, etc. as identifiers. There is a lot of redundancy; code is decoded or decrypted using a long stack of function calls. Abuses eval: an obfuscator wouldn’t be an obfuscator if we didn’t abuse eval. Symmetric transformations, i.e. our goal is to make it harder to read and understand, but there will always be a way to reverse the source code.</p><p>Tools needed to run the obfuscator:</p><ul><li>figlet</li><li>bash</li><li>base64</li><li>gunzip</li><li>perl</li><li>dbus-uuidgen</li><li>basename</li><li>cat</li><li>awk</li></ul><p>Tools needed to run the obfuscated code:</p><ul><li>awk</li><li>gunzip</li><li>base64</li><li>bash</li><li>tail</li><li>eval</li></ul><h3>Defining the obfuscated file structure</h3><p>The obfuscated file we are going to generate is inspired by the technique used by self-executing Bash installers in the Linux world.</p><p>The obfuscated executable consists of two parts:</p><pre>||||||||||||||||||||||||||||||||||||||||||||||||||||||||<br>|||||| INITIAL BASH CODE<br>|||||| MARKER<br>|||||| COMPRESSED CODE<br>||||||||||||||||||||||||||||||||||||||||||||||||||||||||</pre><ul><li>The marker is an explicit delimiter to help the interpreter locate the parts that need to be processed. All content after the marker will be considered compressed data.</li><li>The initial code has the function of loading and decompressing the obfuscated block.</li><li>Compressed code is data represented in base64 that is compressed with gzip.</li></ul><h3>Implementation</h3><p>Before continuing, I present the final code for reference, otherwise you would not have a guide to what I am going to explain.</p><p><strong>obs.sh</strong></p><pre> #!/bin/bash<br>output=$3<br>filex=tmpmainfile.sh<br>echo $&quot;$(cat $2)&quot; &gt; $filex<br>banner=$(figlet &quot;$1&quot; | gzip | base64)<br>banner=&quot;base64 -d &lt;&lt;&lt;\&quot;$banner\&quot; | gunzip&quot;<br>key=&quot;# ===BANNER===&quot;<br>perl -i -pe  &quot;s@$key@$banner@gms&quot; ${filex}<br>currentDir=$(dirname &quot;$0&quot;)<br>cp $currentDir/template.sh $output<br>funcaname=&quot;xf&quot;$(dbus-uuidgen)<br>barridoName=&quot;b&quot;$(dbus-uuidgen)<br>markerName=&quot;m&quot;$(dbus-uuidgen)<br>markerNameVar=&quot;m&quot;$(dbus-uuidgen)<br>echo -n $markerNameVar&quot;=\$(awk &#39;/^___&quot;$markerName&quot;___/ {print NR+1; exit 0; }&#39; \&quot;\${0}\&quot;);&quot; &gt;&gt; $output<br>echo -n $barridoName&quot;=\$(tail -n+\${&quot;$markerNameVar&quot;} \&quot;\${0}\&quot;);&quot; &gt;&gt; $output<br>echo &quot;&quot; &gt;&gt; $output<br>echo &#39;function &#39;$funcaname&#39;(){&#39; &gt;&gt; $output<br>echo &#39;echo $(base64 -d &lt;&lt;&lt; &quot;$1&quot;| gunzip);&#39; &gt;&gt; $output<br>echo &#39;}&#39; &gt;&gt; $output<br>REGX=()<br>IN=$(cat $filex)<br>while IFS=$&#39;\n&#39; read -ra ADDR; do<br>for i in &quot;${ADDR[@]}&quot;; do<br>varxxa=&quot;X02D&quot;$(dbus-uuidgen)<br>cz=$(echo $&quot;$i&quot; | tr -d &#39;\0&#39;| gzip| base64 )<br>echo -n $varxxa&quot;=\$($funcaname \&quot;$cz\&quot;);&quot; &gt;&gt; $output<br>REGX+=($varxxa)<br>done<br>done &lt;&lt;&lt; &quot;$IN&quot;<br>echo -n $&quot;pbv921=\$(eval \&quot;echo \$\\\&quot;\$&quot;$barridoName&quot;\\\&quot;\&quot;);&quot; &gt;&gt; $output<br>echo -n &quot;b17320=\&quot;\$(cat \${0})\&quot;;&quot; &gt;&gt; $output<br>echo -n &quot;echo \$\&quot;\$pbv921\&quot; &gt; \${0};&quot; &gt;&gt; $output<br>echo -n &quot;echo \$\&quot;\$(\${0} \${@})\&quot; &amp;&amp; echo \$\&quot;\$b17320\&quot; &gt; \${0};&quot; &gt;&gt; $output<br>echo &quot;exit 0;&quot;  &gt;&gt; $output<br>echo &quot;___&quot;$markerName&quot;___&quot; &gt;&gt; $output<br>for i in &quot;${REGX[@]}&quot;; do<br>echo -n &quot;$&quot;$i&quot;\$z&quot; &gt;&gt; $output<br>done<br>echo -n &quot;\&quot;\&quot;&quot; &gt;&gt; $output<br>rm $filex &amp;2&gt;/dev/null</pre><p>Usage</p><pre>sudo chmod u+x ./obs.sh<br>./obs.sh  &quot;BANNER&quot; &quot;code_to_obfuscate.sh&quot; &quot;output_file.sh&quot;</pre><h3>Template.sh</h3><p>Create this file along with obs.sh with the name template.sh</p><pre>#!/bin/bash<br>z=&quot;<br>&quot;;</pre><h3>Generating Compressed Code</h3><p>The obfuscator needs to read the original script and split it into pieces in order to subsequently transform and manipulate each line. To do this, we will choose a character that will serve as a separator; in my case, I chose the line break (Line Break Character \n). Each portion of the file will be assigned to a variable that will be added to an output file.</p><p>In summary:</p><ul><li>Read the original file.</li><li>Split content using the line break symbol (\n).</li><li>Each fragment will be stored in a new variable.</li><li>The new variables will be saved in a new file (the obfuscated file).</li><li>To add to the confusion, our final file will be minified.</li></ul><pre>IN=$(cat &quot;input.sh&quot;)<br>output=&quot;obfuscated.sh&quot;<br>while IFS=$&#39;\n&#39; read -ra ADDR; do<br>for i in &quot;${ADDR[@]}&quot;; do<br>varxxa=&quot;var&quot;$(dbus-uuidgen)<br>echo -n $varxxa&quot;=$i&quot; &gt;&gt; $output<br>done<br>done &lt;&lt;&lt; &quot;$IN&quot;</pre><p>Explanation:</p><ul><li>“IN” reads the file we want to obfuscate.</li><li>“output” is the name of the final file.</li><li>“while IFS.. done «&lt; $IN” allows us to read a file using \n as a block separator. Each block of text will be stored in the variable ADDR. A block of text can contain one or more lines.</li><li>“for i in…” allows us to iterate over the lines of the extracted block.</li><li>“varxxa” generates the name of the variables that our obfuscator will use to create mental confusion. We use uuid to generate a unique id.</li><li>“echo -n $varxxa…” assigns the contents of the trimmed block to the generated variable and stores it in the destination file.</li></ul><p>The above code has one flaw: each line of the block is in plain text. To fix this, we will use gzip compression. Now, the output of gzip is not easy to handle, as it contains hidden special characters, so the next step will be to use base64 to store the result in the target file.</p><pre>funcaname=&quot;xf&quot;$(dbus-uuidgen)<br>echo &quot;&quot; &gt;&gt; $output<br>echo &#39;function &#39;$funcaname&#39;(){&#39; &gt;&gt; $output<br>echo &#39;echo $(base64 -d &lt;&lt;&lt; &quot;$1&quot;| gunzip);&#39; &gt;&gt; $output<br>echo &#39;}&#39; &gt;&gt; $outputt</pre><p>You will notice that we have added echo -n $varxxa”=$($funcaname &quot;$cz&quot;);. This line dynamically invokes the function that will decompress the text into base64. For this to work, we need to declare the function beforehand (the function name is randomly generated) and save it to the target file.</p><h3>Marker</h3><p>The obfuscated file, once executed, will start reading its own content with the clear purpose of searching for the marker. All content after the marker will be considered compressed code. To achieve this, we use awkto traverse the obfuscated file line by line from the marker to the end of the file (EOF).</p><p>This block dynamically generates the marker and logic to detect the compressed part, variables are generated, and all of this is saved in the obfuscated destination file:</p><pre>barridoName=&quot;b&quot;$(dbus-uuidgen)<br>markerName=&quot;m&quot;$(dbus-uuidgen)<br>markerNameVar=&quot;m&quot;$(dbus-uuidgen)<br>echo -n $markerNameVar&quot;=\$(awk &#39;/^___&quot;$markerName&quot;___/ {print NR+1; exit 0; }&#39; \&quot;\${0}\&quot;);&quot; &gt;&gt; $output<br>echo -n $barridoName&quot;=\$(tail -n+\${&quot;$markerNameVar&quot;} \&quot;\${0}\&quot;);&quot; &gt;&gt; $output<br># barridoName contains the name of the variable that will store the compressed content once the obfuscator detects the marker.<br># markerNameVar is the name of the variable that will store the line of code where the marker is located.<br># markerName is the delimiter or marker dynamically generated by the obfuscator.</pre><p>The next section will cause the program to terminate before reaching the marker line. It will then print the delimiter and all compressed blocks at the end of the target file.</p><pre>echo &quot;exit 0;&quot;  &gt;&gt; $output<br>echo &quot;___&quot;$markerName&quot;___&quot; &gt;&gt; $output<br>for i in &quot;${REGX[@]}&quot;; do<br>echo -n &quot;$&quot;$i&quot;\$z&quot; &gt;&gt; $output<br>done<br>echo -n &quot;\&quot;\&quot;&quot; &gt;&gt; $output<br>rm $filex &amp;2&gt;/dev/nullt<br># rm $filex &amp;2&gt;/dev/null: This line will cause the obfuscated file to delete temporary data created in the tmp folder.</pre><h3>Initial Bash Code</h3><p>The initial code has the function of loading and decompressing the obfuscated block. All the content after the marker will be considered as compressed data. You will notice that the marker is an explicitly placed delimiter to help the interpreter locate the parts that need to be processed.</p><pre>echo -n $&quot;pbv921=\$(eval \&quot;echo \$\\\&quot;\$&quot;$barridoName&quot;\\\&quot;\&quot;);&quot; &gt;&gt; $outpu<br>echo -n &quot;b17320=\&quot;\$(cat \${0})\&quot;;&quot; &gt;&gt; $output<br>echo -n &quot;echo \$\&quot;\$pbv921\&quot; &gt; \${0};&quot; &gt;&gt; $output<br>echo -n &quot;echo \$\&quot;\$(\${0} \${@})\&quot; &amp;&amp; echo \$\&quot;\$b17320\&quot; &gt; \${0};&quot; &gt;&gt; $output<br># We use eval to evaluate the decompressed code, with its content stored in the variable named in barridoName.</pre><h3>Adding a Banner to Our Obfuscated File</h3><p>figlethelps us with this task; we use this tool by passing the defined banner text in the $1 argument of our obfuscator. Oh look, more compression and ambiguous content in our obfuscated file!</p><pre>filex=tmpmainfile.s<br>echo $&quot;$(cat $2)&quot; &gt; $filex<br>banner=$(figlet &quot;$1&quot; | gzip | base64)<br>banner=&quot;base64 -d &lt;&lt;&lt;\&quot;$banner\&quot; | gunzip&quot;<br>key=&quot;# ===BANNER===&quot;<br>perl -i -pe  &quot;s@$key@$banner@gms&quot; ${filex}h<br># We practically replace the placeholder marker &quot;===BANNER===&quot; with the content from figlet, this after decompressing it.</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=27fa3d974723" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Self-Contained Bash Installer: Step-by-Step Guide]]></title>
            <link>https://mezcalitodesoftware.medium.com/self-contained-bash-installer-step-by-step-guide-fb88b5c58434?source=rss-44c0f5a6f4ed------2</link>
            <guid isPermaLink="false">https://medium.com/p/fb88b5c58434</guid>
            <category><![CDATA[linux-tutorial]]></category>
            <category><![CDATA[bash-scripting]]></category>
            <category><![CDATA[bash-script]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[bash]]></category>
            <dc:creator><![CDATA[Daniel Vera]]></dc:creator>
            <pubDate>Sat, 08 Feb 2025 09:18:40 GMT</pubDate>
            <atom:updated>2025-02-08T09:19:47.820Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/215/1*oR1HayalJxy75yxSHmHtyw@2x.jpeg" /></figure><p>In this tutorial, you will learn how to create a self-contained installer script that packages any executable and its dependencies into a single script. This script can then be distributed to users for easy installation on different systems, without the need for external resources or downloads.</p><p><strong>Why a Self-Contained Installer?</strong></p><p>A self-contained installer script has several advantages:</p><ul><li><strong>Portability</strong> : Can be easily distributed without worrying about missing files or dependencies.</li><li><strong>Easy to use</strong> : Users only need to run a script to install the tool.</li><li><strong>Efficiency</strong> : Everything needed for installation is embedded directly into the script.</li></ul><p>Let’s look at the process of creating such an installer.</p><h3>Step 1: Set up the Project Structure</h3><p>We’ll use a simple project structure to demonstrate how to package a tool, assuming you already have a compiled executable in a dist/ directory. Here’s an example of the structure:</p><pre>myproject/<br>│<br>├── dist/ # Ejecutable compilado<br>│ └── mytool # El ejecutable a instalar<br>├── installer/ # Plantillas del instalador<br>│ └── installer.sh # Script base del instalador<br>├── build/ # Directorio de salida del build<br>├── bin/ # Donde se colocará el instalador final<br>└── Makefile # Automatiza el proceso de empaquetado e instalación</pre><h3><strong>Step 2: Makefile</strong></h3><p>Makefile automates the process of packaging the tool into a tar file and embedding that file into an installer script.</p><pre>tool = mytool<br>binPath = bin<br>buildPath = build<br>distPath = dist    # Directorio donde se encuentra el ejecutable compilado<br>tarName = tool.tar.xz<br>tarFile = $(buildPath)/$(tarName)<br>installer_template = installer/installer.sh<br>installer = $(buildPath)/setup.sh<br>tmpFile = $(buildPath)/tmpload<br><br>.PHONY: compress<br>compress:<br>	@echo &quot;[*] Empaquetando el ejecutable y las dependencias&quot;<br>	@mkdir -p $(buildPath)<br>	@cp $(distPath)/$(tool) $(buildPath)/$(tool)<br>	@cd $(buildPath); tar cJf $(tarName) $(tool)<br>	@cp $(installer_template) $(installer)<br>	@echo &quot;[*] Añadiendo dependencias al instalador&quot;<br>	@cat $(tarFile) &gt;&gt; $(installer)<br>	@echo &quot;[*] Aplicando permisos al instalador&quot;<br>	@chmod a+x $(installer)<br>	@mv $(installer) $(binPath)<br>	@echo &quot;[*] Instalador creado con éxito para $(tool)&quot;<br><br>.PHONY: clean<br>clean:<br>	@echo &quot;[*] Limpiando archivos de construcción&quot;<br>	@rm -rf $(buildPath)<br><br>.PHONY: build<br>build: compress clean</pre><p><strong>Key Points:</strong></p><ul><li><strong>compress</strong> : Packages the executable (mytool) from dist/ into a tar file and adds it to the installer script.</li><li>• <strong>clean</strong> : Cleans up temporary files created during the build process.</li><li>• <strong>build</strong> : A target that automates the entire packaging and installation preparation process.</li></ul><h3><strong>Step 3: Installer Script</strong></h3><p>The installer script (installer/installer.sh) will extract the embedded tarball and set up the tool on the user’s machine.</p><pre>#!/bin/bash<br><br>if [[ $UID != 0 ]]; then<br>    echo &quot;Por favor, ejecuta este script con sudo:&quot;<br>    echo &quot;sudo $0 $*&quot;<br>    exit 1<br>fi<br><br># Función para mostrar mensajes de error<br>message()<br>{<br>  TITLE=&quot;No se puede iniciar la instalación&quot;<br>  if [ -n &quot;$(command -v zenity)&quot; ]; then<br>    zenity --error --title=&quot;$TITLE&quot; --text=&quot;$1&quot; --no-wrap<br>  elif [ -n &quot;$(command -v kdialog)&quot; ]; then<br>    kdialog --error &quot;$1&quot; --title &quot;$TITLE&quot;<br>  elif [ -n &quot;$(command -v notify-send)&quot; ]; then<br>    notify-send &quot;ERROR: $TITLE&quot; &quot;$1&quot;<br>  else<br>    printf &quot;ERROR: %s\\n%s\\n&quot; &quot;$TITLE&quot; &quot;$1&quot;<br>  fi<br>}<br><br># Comprobar si las herramientas necesarias están disponibles<br>TAR=$(command -v tar)<br>CAT=$(command -v cat)<br>TAIL=$(command -v tail)<br>MKDIR=$(command -v mkdir)<br><br>if [ -z &quot;$TAR&quot; ] || [ -z &quot;$CAT&quot; ] || [ -z &quot;$TAIL&quot; ] || [ -z &quot;$MKDIR&quot; ]; then<br>  message &quot;Faltan herramientas requeridas&quot;<br>  exit 1<br>fi<br><br># Definir las rutas de la aplicación<br>APP=&quot;mytool&quot;<br>DESTINATION=&quot;/usr/local/bin&quot;<br>APP_DIR=&quot;/usr/local/mytool&quot;<br><br># Eliminar la instalación existente si ya existe<br>if [ -f &quot;$DESTINATION/$APP&quot; ]; then<br>    echo &quot;[*] Se detectó una versión anterior, eliminando...&quot;<br>    rm -f &quot;$DESTINATION/$APP&quot;<br>fi<br><br># Extraer el archivo desde el script e instalar<br>ARCHIVE=$(awk &#39;/^__ARCHIVE__/ {print NR+1; exit 0; }&#39; &quot;$0&quot;)<br>tail -n+${ARCHIVE} &quot;$0&quot; | tar xJv -C /usr/local<br><br># Establecer los permisos adecuados<br>chmod 755 &quot;$APP_DIR/$APP&quot;<br>ln -s &quot;$APP_DIR/$APP&quot; &quot;$DESTINATION/$APP&quot;<br><br>echo &quot;[*] Instalación completada.&quot;<br><br>exit 0<br><br>__ARCHIVE__</pre><p><strong>Installer Script Key Points:</strong></p><ul><li>Sudo Check : Ensures that the script is run with root (sudo) privileges.</li><li>Tool Availability Check — Checks that essential tools like tar, cat, tail and mkdir are available.</li><li>Unpacking the Archive : The __ARCHIVE__ tag is a placeholder where the tar file is added. The script identifies where the archive starts and extracts it.</li><li>Symbolic Link : Creates a symbolic link in /usr/local/bin so that the tool can be run from anywhere on the system.</li><li>Permissions : Set the appropriate permissions to make the executable accessible and executable.</li></ul><h3>Step 4: Run the Installer</h3><p>After building the installer, you will have a file called setup.sh in the bin/ directory. To install the tool on any system:</p><ul><li>Make sure the script has the appropriate permissions:</li></ul><pre>chmod +x setup.sh</pre><ul><li>Run the script with sudo to install the tool:</li></ul><pre>sudo ./setup.sh</pre><p>This will install the mytool executable to /usr/local/bin, making it globally accessible.</p><h3>Step 5: Distribute Your Installer</h3><p>The advantage of this self-contained installer is that it can be distributed as a single file (setup.sh). Since the script includes the actual tool (packaged as a tar file), users only need to download and run the script to install the tool on their system.</p><h3><strong>Explanation</strong></h3><p><strong>Binary Packaging</strong></p><p>To package the binary or executable into the script, we use a process that compresses it into a tarball file (a .tar or .tar.xz file) and then appends it to the end of the Bash script. We do this in the Makefile.</p><pre>compress:<br>@echo &quot;[*] Empaquetando el ejecutable y las dependencias&quot;<br>@mkdir -p $(buildPath)<br>@cp $(distPath)/$(tool) $(buildPath)/$(tool)<br>@cd $(buildPath); tar cJf $(tarName) $(tool)<br>@cp $(installer_template) $(installer)<br>@echo &quot;[*] Añadiendo el binario al instalador&quot;<br>@cat $(tarFile) &gt;&gt; $(installer)<br>@chmod a+x $(installer)<br>@mv $(installer) $(binPath)</pre><ul><li>1. Copy the binary (mytool) from the distribution directory (dist/) to the build directory (build/).</li></ul><pre>@cp $(distPath)/$(tool) $(buildPath)/$(tool)</pre><ul><li>2. Create a compressed tarball (tar.xz) file containing the binary:</li></ul><pre>@cd $(buildPath); tar cJf $(tarName) $(tool)<br></pre><p>This creates a compressed file tool.tar.xz containing the mytool binary.</p><ul><li>3. Add the tarball file to the end of the installation script:</li></ul><pre>@cat $(tarFile) &gt;&gt; $(installer)</pre><p>Here, the contents of the compressed file (tool.tar.xz) are concatenated to the end of the installer file (setup.sh).</p><ul><li>4. Give execute permissions to the installer:</li></ul><pre>@chmod a+x $(installer)</pre><p><strong>How Bash Script Uses Embedded Binary</strong></p><p>Once the compressed file is added to the script, the next step is to extract that binary during the execution of the installation script. This is key to allowing the script to install the binary to the desired location on the system.</p><p>Bookmark <strong>ARCHIVE</strong> :</p><p>In the Bash script, we use a special marker called <strong>ARCHIVE</strong> that indicates where the installer code ends and where the embedded binary file begins.</p><pre>__ARCHIVE__</pre><p>Everything after this marker is the compressed content (in this case, the tar.xz file).</p><p>How to Extract the Script Binary:</p><p>The script uses tools like awk and tail to identify where the binary file starts (after the ARCHIVE marker ) and extract it.</p><p>Let’s look at this part of the script:</p><pre>ARCHIVE=$(awk &#39;/^__ARCHIVE__/ {print NR+1; exit 0; }&#39; &quot;$0&quot;)<br>tail -n+${ARCHIVE} &quot;$0&quot; | tar xJv -C /usr/local</pre><p><strong>Identify the Compressed File Start Line:</strong></p><pre>ARCHIVE=$(awk ‘/^__ARCHIVE__/ {print NR+1; exit 0; }’ “$0&quot;)</pre><p>Here, awk looks for the line containing ARCHIVE and returns the number of the next line (where the compressed binary file starts). The variable ARCHIVE now contains that line number.</p><p><strong>Extract the Archive from the Script:</strong></p><pre>tail -n+${ARCHIVE} “$0&quot; | tar xJv -C /usr/local</pre><p>We use tail <em>-n+${ARCHIVE}</em> to get all the lines of the script starting from that line (i.e. everything after ARCHIVE ). This content is the compressed archive. We then uncompress it using tar and extract it to the /usr/local directory.</p><p><strong>Installation and Symbolic Link</strong></p><p>After extracting the binary, the script:</p><ol><li>Copy the binary to the target directory (/usr/local/mytool).</li><li>Create a symbolic link in /usr/local/bin to make the executable globally available on the system.</li></ol><pre>chmod 755 “$APP_DIR/$APP”<br><br>ln -s “$APP_DIR/$APP” “$DESTINATION/$APP”</pre><p>• chmod 755 : Sets the appropriate permissions for the binary, making it executable.</p><p>• ln -s : Creates a symbolic link in /usr/local/bin so that you can run mytool from any terminal by typing its name.</p><p><strong>Required Linux Dependencies:</strong></p><ol><li>bash: The installer script is written in Bash, so you need to have Bash installed and available on your system. Almost all Linux distributions include it by default.</li><li>tar: Used to decompress the packed archive (tar.xz). It is a standard tool on most Unix and Linux systems, and is essential for handling .tar, .tar.gz or .tar.xz files.</li><li>cat : Used in the Makefile to concatenate the compressed file with the installation script. It is a basic utility present in all Linux distributions.</li><li>tail : The installer script uses tail to read the archive contents starting from a specific line (after the __ARCHIVE__ marker). This tool comes by default in Linux distributions.</li><li>awk : Used to find the line containing the __ARCHIVE__ marker and determine where the archive file starts in the script. It is also a standard tool on Unix/Linux systems.</li><li>mkdir : Used to create directories in the file system during the installation process. This tool is standard on any Linux-based system.</li><li>chmod : To set the appropriate permissions of installed files (e.g. make the binary executable). This is a standard Linux utility.</li><li>ln : Used to create symbolic links, facilitating global access to the installed binary. It also comes pre-installed on Linux systems.</li></ol><p><strong>Optional (For Visual Error Messages):</strong></p><p>If you want the script to display visual error messages, the following graphical tools can be used. However, they are not strictly necessary and the script will still work without them:</p><ol><li>zenity (optional): Used to display graphical error messages (popups) in desktop environments.</li><li>kdialog (optional): Similar to zenity, used to display popup messages in KDE environments.</li><li>notify-send (optional): Used to send notifications to the notification system in desktop environments.</li><li>xmessage (optional): To display error messages in a simple dialog window on X11 systems.</li></ol><h3><strong>Conclusion</strong></h3><p>The trick to packaging a binary inside a Bash script lies in the fact that the contents of a compressed file can be part of the script itself. As long as the Bash script can differentiate between the installation code and the binary content, it can extract the file and place it in the right place.</p><p>This tutorial showed how to create a fully self-contained installer script in Bash, making it easy to distribute and install your executables on multiple systems. By embedding the binary or any other necessary files directly into the script, you can simplify the installation process for users and ensure that no external dependencies are required during installation.</p><p>This method is flexible and can be adapted to any project, not just compiled code. Whether you are distributing scripts, binaries, or other executables, this approach gives you a simple and reliable way to create a portable installer.</p><p><strong>In summary:</strong></p><ol><li>We package the binary into a tarball.</li><li>We add it to the Bash script after a special marker (__ARCHIVE__).</li><li>The script extracts the tarball and installs it on the system, using standard tools like awk, tail, and tar.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fb88b5c58434" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[MidJourney Silhouette Technique]]></title>
            <link>https://mezcalitodesoftware.medium.com/midjourney-silhouette-technique-d6a3a25f077f?source=rss-44c0f5a6f4ed------2</link>
            <guid isPermaLink="false">https://medium.com/p/d6a3a25f077f</guid>
            <category><![CDATA[midjourney]]></category>
            <category><![CDATA[photography]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[machine-learning]]></category>
            <dc:creator><![CDATA[Daniel Vera]]></dc:creator>
            <pubDate>Thu, 06 Feb 2025 09:28:18 GMT</pubDate>
            <atom:updated>2025-02-06T09:40:58.425Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Driving MidJourney Prompts with Silhouettes</strong></h3><p>I was struggling to set up a scene where a woman and a man were engaged in a heated conversation. Then, I decided to use a silhouette of two people arguing, and it turned out to be exactly what I needed.</p><p>This technique is highly useful, though not foolproof. While it may not work 100% of the time, it will undoubtedly reduce the number of images required for a given prompt.</p><p>Essentially, you need to gather silhouettes of the poses or actions you want the character to execute. Just write the prompt and select a silhouette image as prompt mode and hit enter.</p><h3>POC</h3><p>I’ve been using silhouettes since then and it’s working for me like a charm. Let’s dive into some examples.</p><h4>Prompt:</h4><blockquote>cinematic shot, a woman and a man having a conversation in the middle of a hallway building, neon lights</blockquote><h3>Before Silhouette</h3><p>The output wasn’t what I wanted, and I was getting really frustrated. Then, I decided to try the silhouette approach. I noticed that images with a solid color background tend to influence the algorithm more effectively.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/645/1*g_ps1bhMLG8gIe6at39OVg@2x.jpeg" /></figure><h3>Using Silhouette as guidance along with the written prompt</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/630/1*CWfBcEseh8rVN2StKwkbdQ@2x.jpeg" /></figure><p><strong>The output:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*Q8LngrcUSbZ_EPz8HMUj7Q@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/408/1*0AAmAZGFtwJKmViJZ517XA@2x.jpeg" /></figure><p>As you can see the output is very close to what I wanted. It’s the perfect scene.</p><p><strong>Additional points</strong></p><ul><li>The written prompt is crucial, as it provides the necessary details and context for the scene. However, using a silhouette can further refine the output by visually guiding the AI toward the composition and action you’re describing.</li><li>Experimenting with different silhouette images can lead to more precise and varied results. Each silhouette provides a unique visual cue that influences how the AI interprets the scene, helping to refine details such as posture, motion, and interaction.</li><li>It’s not a perfect method — sometimes you’ll need to keep experimenting until you achieve the ideal output. Adjusting silhouettes, refining your prompt, and trying different background colors can all help fine-tune the results.</li><li>Try experimenting with different background colors, as they can influence the AI’s interpretation of lighting, mood, and depth in the scene. A background that complements the overall atmosphere of your prompt can enhance the final output.</li></ul><p><strong>Extra</strong></p><p>Another tip is to use a person (not just a silhouette) against a background that matches the scene’s lighting. This can create interesting effects and influence the algorithm in a unique way.</p><p><strong>Example</strong></p><p>The left image is an prompt image and the right side is the output.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*61jYoCBP93D0rgh8jxrHgQ@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*fok5IgwQPXsYHtCHF5LIpQ@2x.jpeg" /></figure><h3>Where to get silhouettes?</h3><p>Well you can go to google and search for</p><blockquote>“person performing action” + “silhouette”.</blockquote><p>Or you can create them yourself by using photoshop , photopea, gimp, krita, etc…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/645/1*elPOKPjRFLiGUu0Y-lAUcQ@2x.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d6a3a25f077f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[El octubre negro de 2016]]></title>
            <link>https://mezcalitodesoftware.medium.com/el-octubre-negro-de-2016-b34c3e4abcaa?source=rss-44c0f5a6f4ed------2</link>
            <guid isPermaLink="false">https://medium.com/p/b34c3e4abcaa</guid>
            <category><![CDATA[internet]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[software]]></category>
            <category><![CDATA[historia]]></category>
            <category><![CDATA[dns]]></category>
            <dc:creator><![CDATA[Daniel Vera]]></dc:creator>
            <pubDate>Mon, 12 Dec 2022 04:34:35 GMT</pubDate>
            <atom:updated>2022-12-17T20:57:40.729Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/770/0*4cPzNikDDukZuySX" /></figure><p>En Octubre de 2016 fue atacado DYN , el cuál es uno de los mayores proveedores de DNS de internet del mundo y utilizado por la mayoría de compañías de internet. El resultado de este ataqué fue que muchos sitios de internet fueron inhabilitados durante horas. Es evidente que la cantidad de dinero que se perdió en este ataqué y las afectaciones a los empleos y operaciones no tienen precedentes. Imagina los servicios de seguridad, salud, comunicaciones y más fueron interrumpidos por unas horas: causando el caos.</p><p>Se denomina como el mayor ataque en la historia de internet hasta ahora. El ataque fue llevado acabo por el grupo de hackers denominado “ New World Hackers “ <a href="https://es.quora.com/profile/Daniel-Morales-27#XqUzq">[1]</a> al realizar un DNS hijacking <a href="https://es.quora.com/profile/Daniel-Morales-27#pBWXh">[2]</a>: Algo así como un mega ataque DDOS pero al DNS.</p><p><strong>Sitios afectados durante horas</strong><a href="https://es.quora.com/profile/Daniel-Morales-27#Flsgv">[3]</a>:</p><ul><li>Airbnb</li><li>amazon.com</li><li>The A.V. Club</li><li>BBC</li><li>The_Boston_Globe</li><li>Box</li><li>Business Insider</li><li>CNN</li><li>Comcast</li><li>CrunchBase</li><li>DirecTV</li><li>The Elder Scrolls Online</li><li>Electronic Arts</li><li>Etsy</li><li>FiveThirtyEight​</li><li>Fox News​</li><li>The Guardian​</li><li>GitHub​</li><li>Grubhub</li><li>HBO​</li><li>Heroku​</li><li>.HostGator​</li><li>iHeartRadio​</li><li>Imgur​</li><li>Indiegogo​</li><li>Mashable​</li><li>National Hockey League​</li><li>Netflix​</li><li>The New York Times​</li><li><a href="http://overstock.com/">Bedding, Furniture, Electronics, Jewelry, Clothing &amp; more</a>​</li><li>PayPal​</li><li>Pinterest​</li><li>Pixlr​</li><li>PlayStation Network​</li><li>Qualtrics​</li><li>Quora​</li><li>Reddit​</li><li>Roblox​</li><li>Ruby Lane​</li><li>RuneScape​</li><li>SaneBox​</li><li>Seamless​</li><li>Second Life​</li><li>Shopify</li><li>Slack​</li><li>SoundCloud​</li><li>Squarespace​</li><li>Spotify​</li><li>Starbucks​</li><li>Storify​</li><li>Tumblr​</li><li>Twilio​</li><li>Twitter​</li><li>Verizon Communications​</li><li>Visa​</li><li>Vox Media​</li><li>Walgreens​</li><li>The Wall Street Journal​</li><li>Wikia​Wired</li><li><a href="http://wix.com/">Free Website Builder | Create a Free Website | Wix.com</a></li><li>WWE Network​</li><li>Xbox Live​</li><li>Yammer​</li><li>Yelp​</li><li>Zillow​</li></ul><p><strong>Notas al pie</strong></p><p><a href="https://es.quora.com/profile/Daniel-Morales-27#cite-XqUzq">[1] </a><a href="https://www.theguardian.com/technology/2016/oct/26/ddos-attack-dyn-mirai-botnet">DDoS attack that disrupted internet was largest of its kind in history, experts say</a></p><p><a href="https://es.quora.com/profile/Daniel-Morales-27#cite-pBWXh">[2] </a><a href="https://www.computerhope.com/jargon/d/dnshijac.htm">What is DNS Hijacking?</a></p><p><a href="https://es.quora.com/profile/Daniel-Morales-27#cite-Flsgv">[3] </a><a href="https://cnnespanol.cnn.com/2016/10/21/esta-seria-la-razon-por-la-que-twitter-reddit-y-netflix-estan-caidos/">Un ciberataque tumba sitios populares de internet como Reddit, Twitter y Netflix</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b34c3e4abcaa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Baúl de los recuerdos — Construyendo un crawler con python]]></title>
            <link>https://mezcalitodesoftware.medium.com/ba%C3%BAl-de-los-recuerdos-construyendo-un-crawler-con-python-4b0827149a94?source=rss-44c0f5a6f4ed------2</link>
            <guid isPermaLink="false">https://medium.com/p/4b0827149a94</guid>
            <category><![CDATA[python]]></category>
            <category><![CDATA[regular-expressions]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[codigo]]></category>
            <category><![CDATA[software]]></category>
            <dc:creator><![CDATA[Daniel Vera]]></dc:creator>
            <pubDate>Thu, 08 Dec 2022 08:17:20 GMT</pubDate>
            <atom:updated>2022-12-17T20:53:08.095Z</atom:updated>
            <content:encoded><![CDATA[<h3>Baúl de los recuerdos — Construyendo un crawler con python</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*yKLxx9zh2YVBwa89.jpg" /></figure><p>Esa falla me emocionó demasiado y puse manos a la obra para construir un script que explotara la falla. Intente desarrollarlo en diversos lenguajes, pero al final tenía el problema de la modificación dinámica de estructuras de datos en loop. Fue cuando descubrí que python eliminaba dicho problema de forma nativa y entonces surgió el POC. Sin darme cuenta (y sin saber lo que estaba programando) el resultado final fue un pequeño crawler con un comportamiento algo curioso.</p><ol><li>Leía un archivo “pivote” (index.php)</li><li>Buscaba posibles archivos a los que se hacía referencia el archivo pivote (include, require, require_once, link, elementos a).</li><li>Una vez encontradas las referencias, se procedía a almacenar cada referencia en una de dos listas: Si la referencia estaba explotada se almacenaba en la lista de “explotados” y se ignoraba de lo contrario se almacenaba en la lista de “no explotados”.</li><li>Tanto archivos de texto y archivos normales: se almacenaban en un directorio de mi pc . El crawler iba recreando la estructura de directorios. del servidor en mi local</li><li>El proceso se repetía hasta que no quedaran archivos de texto con referencias. Esto nos lo indicaba un buffer interno del programa que en tiempo de ejecución ayudaba a determinar si debía continuar o no.</li><li>Una vez clonado el sitio remoto, se podía proceder a buscar passwords, conexiones a base de datos y conexiones a otros servidores.</li></ol><p><strong>Código fuente</strong></p><p>Hice algunos POCs, y adapte el programa para explotar otras versiones de la misma vulnerabilidad, la cual era un tipo de “Directory Path Traversal”. La empresa que explote al final de todo fue contactada por mi y le pase el reporte de fallas y los archivos explotados. Me remunero con 300 dlls y todos felices. Años después decidí liberar el código fuente como Open Source.</p><p>No es para nada genial y me avergüenza pues esta bien cochinote por dentro así como las faltas ortográficas que tiene. Pero si me hace sentir bien cuando pienso que no sabía tanto en 2012 como para desarrollar algo así y me hace sentir orgulloso. Puedes encontrarlo en el siguiente enlace: <a href="https://github.com/danyelmoralesdeprecated/DITRAEXTO">danyelmoralesdeprecated/DITRAEXTO</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4b0827149a94" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>