<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Go on Jordan Wright</title><link>https://jordan-wright.com/blog/tags/go/</link><description>Recent content in Go on Jordan Wright</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 02 Sep 2018 22:01:01 -0500</lastBuildDate><atom:link href="https://jordan-wright.com/blog/tags/go/index.xml" rel="self" type="application/rss+xml"/><item><title>Building Gophish Healthcheck: Part One</title><link>https://jordan-wright.com/blog/post/2018-09-02-building-email-healthcheck/</link><pubDate>Sun, 02 Sep 2018 22:01:01 -0500</pubDate><guid>https://jordan-wright.com/blog/post/2018-09-02-building-email-healthcheck/</guid><description>&lt;img src="https://jordan-wright.com/blog/images/headers/gophish_healthcheck.png" alt="" class="pure-img" &gt;

&lt;p&gt;One of the questions I see most often from Gophish users is &amp;ldquo;how do I get past my spam filter?&amp;rdquo; Generally, my answer to this is something along the lines of &amp;ldquo;just whitelist the IP address,&amp;rdquo; since it&amp;rsquo;s my opinion that phishing simulations should be a test of the &lt;em&gt;people&lt;/em&gt; and &lt;em&gt;processes&lt;/em&gt;, not the email infrastructure.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;But what if we do want to test the email infrastructure?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This post is the first in a two-part series about how I&amp;rsquo;m creating the &lt;a href="https://github.com/gophish/healthcheck"&gt;email healthcheck&lt;/a&gt; service for Gophish. This post talks about how I handle DNS programmatically, and the next post will describe the actual architecture being used.&lt;/p&gt;</description></item><item><title>Introducing elastichoney - an Elasticsearch Honeypot</title><link>https://jordan-wright.com/blog/2015/03/23/introducing-elastichoney-an-elasticsearch-honeypot/</link><pubDate>Mon, 23 Mar 2015 00:00:00 +0000</pubDate><guid>https://jordan-wright.com/blog/2015/03/23/introducing-elastichoney-an-elasticsearch-honeypot/</guid><description>&lt;img src="https://jordan-wright.com/blog/images/headers/elastichoney.png" alt="" class="pure-img" &gt;

&lt;h3 id="introduction"&gt;Introduction&lt;/h3&gt;
&lt;p&gt;I recently &lt;a href="https://jordan-wright.com/blog/2015/03/08/elasticsearch-rce-vulnerability-cve-2015-1427/"&gt;wrote&lt;/a&gt; about an Elasticsearch RCE vulnerability that is being heavily exploited in the wild. To see what kind of attacks are taking place, I decided to write a simple honeypot designed to mimic a vulnerable Elasticsearch (ES) instance. Say hello to &lt;a href="http://github.com/jordan-wright/elastichoney"&gt;elastichoney&lt;/a&gt;!&lt;/p&gt;</description></item><item><title>Gophish Update: Getting Closer to Alpha!</title><link>https://jordan-wright.com/blog/2015/02/26/gophish-update-getting-closer-to-alpha/</link><pubDate>Thu, 26 Feb 2015 00:00:00 +0000</pubDate><guid>https://jordan-wright.com/blog/2015/02/26/gophish-update-getting-closer-to-alpha/</guid><description>&lt;img src="https://jordan-wright.com/blog/images/headers/gophish_purple.png" alt="" class="pure-img" &gt;

&lt;h3 id="introduction"&gt;Introduction&lt;/h3&gt;
&lt;p&gt;It&amp;rsquo;s been a busy couple of months!&lt;/p&gt;
&lt;p&gt;I thought it would be worth providing a long-overdue update into the development status of &lt;a href="http://github.com/jordan-wright/gophish"&gt;gophish&lt;/a&gt;. Overall, the project is getting closer to beta status every day, and I&amp;rsquo;m hoping to see a &lt;a href="https://github.com/jordan-wright/gophish/milestones"&gt;0.1 release&lt;/a&gt; at the end of March.&lt;/p&gt;
&lt;p&gt;Without further ado, let&amp;rsquo;s dive in and see where we&amp;rsquo;re at.&lt;/p&gt;</description></item><item><title>Building GoPhish - How to Send Email with Go</title><link>https://jordan-wright.com/blog/2014/01/03/building-gophish-how-to-send-email-with-go/</link><pubDate>Fri, 03 Jan 2014 00:00:00 +0000</pubDate><guid>https://jordan-wright.com/blog/2014/01/03/building-gophish-how-to-send-email-with-go/</guid><description>&lt;img src="https://jordan-wright.com/blog/images/headers/go_email.png" alt="" class="pure-img" &gt;

&lt;h3 id="introduction"&gt;Introduction&lt;/h3&gt;
&lt;p&gt;I&amp;rsquo;ve been playing around with Go for about a month now, and I&amp;rsquo;ve &lt;em&gt;really&lt;/em&gt; grown to like it. After getting used to the syntax and remembering what a pointer is for (thanks, Python), Go has become a favorite language to develop with. I&amp;rsquo;m even using it for the &lt;a href="http://www.matasano.com/articles/crypto-challenges/"&gt;Matasano Crypto Challenges&lt;/a&gt; (which are &lt;em&gt;awesome&lt;/em&gt;).&lt;/p&gt;
&lt;p&gt;While the standard library in Go is definitely robust, being a young language, there are a few niceties that aren&amp;rsquo;t yet included. Sending email is one of them. Don&amp;rsquo;t get me wrong, Go has a wonderful &lt;a href="http://golang.org/pkg/net/smtp/"&gt;SMTP&lt;/a&gt; package, &lt;a href="http://golang.org/pkg/mime/"&gt;MIME&lt;/a&gt; package, and even a &lt;a href="http://golang.org/pkg/net/mail/"&gt;Mail&lt;/a&gt; package (which &lt;em&gt;only&lt;/em&gt; parses existing email messages). However, there is no library to actually &lt;strong&gt;create&lt;/strong&gt; emails in a meaningful way. Since &lt;a href="https://github.com/jordan-wright/gophish"&gt;Gophish&lt;/a&gt; relies heavily on sending emails, I&amp;rsquo;ve sought to change this. And, after reading more RFC&amp;rsquo;s than I normally prefer, I believe I&amp;rsquo;ve created a package that provides intuitive, robust, and flexible email creation and sending called &lt;a href="https://github.com/jordan-wright/email"&gt;email&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Let&amp;rsquo;s see how to use it.&lt;/p&gt;</description></item><item><title>Building Gophish - Day 1</title><link>https://jordan-wright.com/blog/2013/11/29/building-gophish-day-1/</link><pubDate>Fri, 29 Nov 2013 00:00:00 +0000</pubDate><guid>https://jordan-wright.com/blog/2013/11/29/building-gophish-day-1/</guid><description>&lt;img src="https://jordan-wright.com/blog/images/headers/gophish.png" alt="" class="pure-img" &gt;

&lt;h3 id="introduction"&gt;Introduction&lt;/h3&gt;
&lt;p&gt;Since the &lt;a href="http://sptoolkit.com/the_end.php"&gt;Simple Phishing Toolkit (SPT)&lt;/a&gt; was discontinued, I&amp;rsquo;ve wanted to create a simple, effective, and open-source phishing toolkit. In recent years, we&amp;rsquo;ve seen a rise in spear-phishing attacks targeting large organizations, most of which are largely successful. The goal of this toolkit will be to provide businesses and penetration testers with the ability to quickly and easily perform in-house or contracted phishing engagements, and track the responses to see where improvements can be made. This toolkit will be called &lt;a href="https://github.com/jordan-wright/gophish"&gt;gophish&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;In addition to this, I&amp;rsquo;ve been casually poking around at &lt;a href="http://golang.org/"&gt;&lt;code&gt;go&lt;/code&gt;&lt;/a&gt; for a while now, and have decided it would be good to finally put it to use in a larger project. I&amp;rsquo;m a fan of seeing the steady development and updates of projects as they are created. I believe it can help keep the developer motivated and the users informed and involved, so this is what I&amp;rsquo;m going to do. Hopefully, these posts will allow others to learn alongside me, as well as spur improvements from experienced &lt;code&gt;go&lt;/code&gt; developers so that &lt;a href="https://github.com/jordan-wright/gophish"&gt;gophish&lt;/a&gt; can be the best product possible.&lt;/p&gt;
&lt;p&gt;With that being said - let&amp;rsquo;s get started!&lt;/p&gt;</description></item></channel></rss>