<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Security on Evan Hoffman</title><link>https://evan.wtf/tags/security/</link><description>Recent content in Security on Evan Hoffman</description><generator>Hugo</generator><language>en-US</language><copyright>Evan Hoffman</copyright><lastBuildDate>Wed, 12 Feb 2014 11:06:07 +0000</lastBuildDate><atom:link href="https://evan.wtf/tags/security/index.xml" rel="self" type="application/rss+xml"/><item><title>Setting user Postgres passwords via MD5</title><link>https://evan.wtf/2014/02/12/setting-user-postgres-passwords-via-md5/</link><pubDate>Wed, 12 Feb 2014 11:06:07 +0000</pubDate><guid>https://evan.wtf/2014/02/12/setting-user-postgres-passwords-via-md5/</guid><description>&lt;p&gt;Say you want to create a Postgres account for a user but you don&amp;rsquo;t want them to have to reset it after logging in, and you don&amp;rsquo;t want to do the &amp;ldquo;come type in a password on my computer&amp;rdquo; routine. Well, here&amp;rsquo;s one way around this.&lt;/p&gt;&#10;&lt;ol&gt;&#10;&lt;li&gt;&#10;&lt;p&gt;Have the user generate an MD5 of their password on their local computer. Postgres uses the username as the salt for the hash, so the command to generate the md5 on a Mac would be (assuming a username of &amp;rsquo;ehoffman&amp;rsquo; and a password of &amp;lsquo;abcdefg&amp;rsquo;):&lt;/p&gt;</description></item><item><title>Super quick wordpress exploit stopper</title><link>https://evan.wtf/2013/10/25/super-quick-wordpress-exploit-stopper/</link><pubDate>Fri, 25 Oct 2013 09:27:38 +0000</pubDate><guid>https://evan.wtf/2013/10/25/super-quick-wordpress-exploit-stopper/</guid><description>&lt;p&gt;I got an email yesterday from my host (DigitalOcean) that I was running a phishing website. So, I&amp;rsquo;m not, but I quickly guessed what happened: my Wordpress got hacked. This is just one of the risks of running silly little PHP apps. I logged in, deleted the themes directories, reinstalled clean ones, and ensured this doesn&amp;rsquo;t happen again by doing the following:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;useradd apache_ro&lt;/li&gt;&#10;&lt;li&gt;chown -R apache_ro:apache_ro $WP/wp-content/themes&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;Now apache can&amp;rsquo;t write to those directories. This means you can&amp;rsquo;t update Wordpress via the web UI, but I&amp;rsquo;m ok with that.&lt;/p&gt;</description></item><item><title>Graphing SSH dictionary attacks with HighCharts</title><link>https://evan.wtf/2011/11/18/graphing-ssh-dictionary-attacks-with-highcharts/</link><pubDate>Fri, 18 Nov 2011 14:06:03 +0000</pubDate><guid>https://evan.wtf/2011/11/18/graphing-ssh-dictionary-attacks-with-highcharts/</guid><description>&lt;p&gt;After my 10-year-old basement Linux server died this week from a power outage, I took the sad step of giving up on it. It&amp;rsquo;s died before and I&amp;rsquo;ve patched it back together with a new power supply here or an addon PCI SATA card there, but I finally decided to throw in the towel since I had a newer old computer that had been idle for several years. The one that died was an Athlon K7 750 MHz with 512 MB ram. The new one is an Athlon 2 GHz (3200+) with 1 gig. For my uses, specs don&amp;rsquo;t really matter that much, but it&amp;rsquo;s nice to have more power for free.&lt;/p&gt;</description></item><item><title>Making sure SSLv2 is disabled in Apache (and Nginx)</title><link>https://evan.wtf/2011/09/20/making-sure-sslv2-is-disabled-in-apache/</link><pubDate>Tue, 20 Sep 2011 14:06:38 +0000</pubDate><guid>https://evan.wtf/2011/09/20/making-sure-sslv2-is-disabled-in-apache/</guid><description>&lt;p&gt;&lt;strong&gt;Edit Jan 24, 2012:&lt;/strong&gt; Deleted all the crap from this story and just left the recommended Apache and Nginx SSL cipher suites for maximum security without SSLv2 and without BEAST vulnerability (at least according to Qualys).&#10;&lt;strong&gt;Apache httpd&lt;/strong&gt;&lt;/p&gt;&#10;&lt;pre tabindex="0"&gt;&lt;code&gt;SSLProtocol -ALL +SSLv3 +TLSv1&#10;SSLCipherSuite ECDHE-RSA-AES256-SHA384:AES256-SHA256:RC4:HIGH:!MD5:!aNULL:!EDH:!AESGCM;&#10;SSLHonorCipherOrder on&#10;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;&lt;strong&gt;nginx&lt;/strong&gt;&lt;/p&gt;&#10;&lt;pre tabindex="0"&gt;&lt;code&gt;ssl_protocols SSLv3 TLSv1;&#10; ssl_ciphers ECDHE-RSA-AES256-SHA384:AES256-SHA256:RC4:HIGH:!MD5:!aNULL:!EDH:!AESGCM;&#10; ssl_prefer_server_ciphers on;&#10;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Source:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;a href="https://community.qualys.com/blogs/securitylabs/2011/10/17/mitigating-the-beast-attack-on-tls"&gt;Qualys&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://www.ssllabs.com/ssldb/"&gt;SSL checker&lt;/a&gt;&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;&lt;a href="http://affiliate.godaddy.com/redirect/5F43C3ECBA841ACFC3859F4F4E6CA7DA64C271385B2D61A3AD6F3CCE83EB1DD8235E60DCD7D63BCD92E2429E79A75FAC"&gt;&lt;img src="http://affiliate.godaddy.com/ads/5F43C3ECBA841ACFC3859F4F4E6CA7DA64C271385B2D61A3AD6F3CCE83EB1DD8235E60DCD7D63BCD92E2429E79A75FAC" alt="Go Daddy $12.99 SSL Sale!"&gt;&lt;/a&gt;&lt;/p&gt;</description></item><item><title>The Barracuda Spam Firewall VMware Appliance (Vx) finally exists!</title><link>https://evan.wtf/2010/10/04/the-barracuda-spam-firewall-vmware-appliance-vx-finally-exists/</link><pubDate>Mon, 04 Oct 2010 18:24:12 +0000</pubDate><guid>https://evan.wtf/2010/10/04/the-barracuda-spam-firewall-vmware-appliance-vx-finally-exists/</guid><description>&lt;p&gt;When I started at my current company, spam was handled with a separate server running SpamAssassin and a few other services. This sort of got the job done but required babysitting. I wasn&amp;rsquo;t part of the Sysadmin team at that point but I know they had to restart SpamAssassin relatively frequently, manually clear out the email queue when people noticed they weren&amp;rsquo;t receiving email, etc.&lt;/p&gt;&#10;&lt;p&gt;After a few months, someone wised up and purchased a Barracuda Spam Firewall. I assumed this was basically a pretty GUI wrapper around the same tools we had already been using, but it was certainly worth the money. In addition to the basic filtering of spam it filtered for viruses, performed recipient verification against AD via LDAP, had nice graphing and reporting.&lt;/p&gt;</description></item><item><title>Passwordless SSH Everywhere</title><link>https://evan.wtf/2010/03/30/passwordless-ssh-everywhere/</link><pubDate>Tue, 30 Mar 2010 15:18:22 +0000</pubDate><guid>https://evan.wtf/2010/03/30/passwordless-ssh-everywhere/</guid><description>&lt;p&gt;I&amp;rsquo;ve known about ssh keys for a long time and frequently use them, most frequently so that a script can transfer a file between two servers without having to do some mumbo-jumbo where I try to pipe a password into it or some other wacky thing. I hadn&amp;rsquo;t fully embraced ssh keys, though, because I didn&amp;rsquo;t like the idea that if I lost my laptop, I&amp;rsquo;d be losing a free key into my servers. Then I discovered ssh-agent. This isn&amp;rsquo;t new, so I&amp;rsquo;m kind of embarrassed I didn&amp;rsquo;t know about it, but I&amp;rsquo;ve been using it for a few months now and I can&amp;rsquo;t imagine going back.&lt;/p&gt;</description></item></channel></rss>