<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Apache on</title><link>https://dawning.ca/tags/apache/</link><description>Recent content in Apache on</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Copyright © James Snell</copyright><lastBuildDate>Sun, 13 Nov 2016 14:18:51 +0000</lastBuildDate><atom:link href="https://dawning.ca/tags/apache/index.xml" rel="self" type="application/rss+xml"/><item><title>Battle against injected PHP</title><link>https://dawning.ca/posts/battle-against-injected-php/</link><pubDate>Sun, 13 Nov 2016 14:18:51 +0000</pubDate><guid>https://dawning.ca/posts/battle-against-injected-php/</guid><description>
&lt;p>My main personal web server became infected with some effin malware that was injected it very nearly every single .php script on the server. The injected code was basically:&lt;/p>
&lt;p>//###=CACHE START=###
@error_reporting(E_ALL);
@ini_set(&amp;ldquo;error_log&amp;rdquo;,NULL);
&amp;hellip;etc&lt;/p>
&lt;p>$strings = &amp;ldquo;as&amp;rdquo;; $strings .= &amp;ldquo;se&amp;rdquo;; $strings .= &amp;ldquo;rt&amp;rdquo;; $strings2 = &amp;ldquo;st&amp;rdquo;; $strings2 .= &amp;ldquo;r_r&amp;rdquo;; $strings2 .= &amp;ldquo;ot13&amp;rdquo;; $gbz = &amp;ldquo;riny(&amp;rdquo;.$strings2(&amp;ldquo;base64_decode&amp;rdquo;);
$light = $strings2($gbz.&amp;rsquo;(&amp;ldquo;nJLtX&amp;hellip;.&amp;rdquo;));&amp;rsquo;); $strings($light);
//###=CACHE END=###&lt;/p>
&lt;p>This is kind of beautiful to me, it took me a little while to figure out what it does. In effect it causes basic system info for anyone browsing sites on that server to be sent off to some other php script on another server. At first I altered the server and my network to prevent any traffic from reaching the intended target. Instead I captured the traffic so I could get a look at the volume of it. Here&amp;rsquo;s an example apache log message generated by someone browsing an infected site:&lt;/p></description></item><item><title>Dear Diary: Running Trac and upgrading to Ubuntu Server 14.04</title><link>https://dawning.ca/posts/dear-diary-running-trac-and-upgrading-ubuntu-server-14-04/</link><pubDate>Wed, 17 Sep 2014 17:17:20 +0000</pubDate><guid>https://dawning.ca/posts/dear-diary-running-trac-and-upgrading-ubuntu-server-14-04/</guid><description>
&lt;p>I&amp;rsquo;m a fairly heavy user of trac. I&amp;rsquo;ve got various software projects I organize using trac. I decided to upgrade one of my Ubuntu 12.04 servers to Ubuntu 14.04 and of course ran in to the typical apache2 headaches that are born out of this particular transition.&lt;/p>
&lt;p>After remembering to rename my virtual host files with .conf extensions (I find that change annoying as hell on its own), I kept running aground with an Internal Server Error message to which I couldn&amp;rsquo;t even find a hint in my logs, even after cranking up the verbosity.&lt;/p></description></item><item><title>Trac Authenticating Through Active Directory</title><link>https://dawning.ca/posts/trac-auth-via-centrifyad/</link><pubDate>Mon, 26 Sep 2011 10:06:18 +0000</pubDate><guid>https://dawning.ca/posts/trac-auth-via-centrifyad/</guid><description>
&lt;p>A minor post - mostly for my own notes..&lt;/p>
&lt;p>I was setting up an instance of &lt;a href="http://trac.edgewall.org/">Trac&lt;/a> and I wanted &lt;a href="http://en.wikipedia.org/wiki/Active_Directory">Active Directory&lt;/a> authentication going. I&amp;rsquo;ve had this before, but I recently learned of &lt;a href="http://en.wikipedia.org/wiki/Active_Directory#Unix_integration">Centrify&lt;/a> which provides a VERY easy means to setup system authentication with AD. This meant I needed to find a Centrify-specific way to get AD authentication going in Trac.&lt;/p>
&lt;p>I was close to an obvious simple solution for a fair while, but I kept running in to error messages like:&lt;/p></description></item><item><title>Dawning.ca Spruced Up</title><link>https://dawning.ca/posts/dawning-ca-spruced-up/</link><pubDate>Fri, 15 Jan 2010 03:12:36 +0000</pubDate><guid>https://dawning.ca/posts/dawning-ca-spruced-up/</guid><description>
&lt;figure style="float: right; margin: 0 0 1em 1em; max-width: 272px;">
&lt;img src="https://dawning.ca/uploads/2010/01/OldDawning.png" alt="">
&lt;figcaption>Previous Dawning.ca Layout&lt;/figcaption>
&lt;/figure>
&lt;p>I&amp;rsquo;ve just spent a few hours re-designing the layout of Dawning.ca. The &lt;a href="http://wordpress.org/extend/themes/oriental">old one&lt;/a> served me very well and I really liked it. I had heavily modified the previous theme to work for me and work it did. I may tap it some time in the future as a backup&amp;hellip; As you can see to the right, the new style is fairly different compared to the image. Although I kept the workflow as I think it was already pretty good.&lt;/p></description></item><item><title>YouTube Grabber App</title><link>https://dawning.ca/posts/youtube-grabber-app/</link><pubDate>Tue, 24 Nov 2009 12:06:27 +0000</pubDate><guid>https://dawning.ca/posts/youtube-grabber-app/</guid><description>
&lt;p>I&amp;rsquo;ve whipped up this little YouTube video grabber for myself and I&amp;rsquo;ve opened it up for the moment. If I see it getting spammed or abused in some way, I&amp;rsquo;ll probably password protect it, nevertheless, you can check it out &lt;strong>&lt;a href="https://dawning.ca/youtube/">here&lt;/a>&lt;/strong>.&lt;/p>
&lt;h2 id="what-it-does">&lt;a href="https://dawning.ca/youtube/">&lt;figure>
&lt;picture>
&lt;img
loading="lazy"
decoding="async"
alt=""
class="image_figure image_internal image_unprocessed"
src="https://dawning.ca/uploads/2009/11/ytGrabber.png"
/>
&lt;/picture>
&lt;/figure>
&lt;/a>What it does&lt;/h2>
&lt;p>This little app takes a YouTube video link and then adds the reference in a database. A seperate script then polls that database and looks for new URLs. It then uses another script (that I did not write), called yt-download, to fetch each video and dump it to my fileserver.&lt;/p></description></item><item><title>Webserver replaced, again..</title><link>https://dawning.ca/posts/webserver-replaced-again/</link><pubDate>Sun, 13 Sep 2009 12:14:26 +0000</pubDate><guid>https://dawning.ca/posts/webserver-replaced-again/</guid><description>
&lt;p>Howdy, so I&amp;rsquo;ve returned to hosting my site on a professional connection rather than over my lameo home setup. I&amp;rsquo;ve grown tired of n00bful downtime due to power outages, ISP outages, people tripping over cables or gnomes screwin around.&lt;/p>
&lt;p>As such, dawning.ca is now hosted on a server I&amp;rsquo;ve got running down in Texas with the valuable help of &lt;a href="http://linode.com">Linode&lt;/a>. That&amp;rsquo;s all for now folks.&lt;/p>
&lt;h2 id="update">Update&lt;/h2>
&lt;p>I ran in to some interesting configuration problems with this new server that was causing it to frequently run out of memory. I &lt;em>think&lt;/em> I&amp;rsquo;ve resolved those matters with some real help of &lt;a href="http://library.linode.com/troubleshooting/memory-networking">this article&lt;/a>.&lt;/p></description></item><item><title>The Anti-Epic Tale of Making IIS Play Nice with Apache</title><link>https://dawning.ca/posts/iis-and-apache/</link><pubDate>Wed, 24 Jun 2009 14:04:56 +0000</pubDate><guid>https://dawning.ca/posts/iis-and-apache/</guid><description>
&lt;figure style="float: right; margin: 0 0 1em 1em; max-width: 226px;">
&lt;img src="https://dawning.ca/uploads/2009/06/MattDamon.png" alt="">
&lt;figcaption>&lt;/figcaption>
&lt;/figure>
&lt;h2 id="the-mission">The Mission&lt;/h2>
&lt;p>To run an &lt;a href="http://en.wikipedia.org/wiki/Apache_HTTP_Server">Apache&lt;/a> server (on Windows) on the same machine that was already hosting &lt;a href="http://en.wikipedia.org/wiki/Internet_Information_Services">IIS&lt;/a>.&lt;/p>
&lt;h2 id="the-strategy">The Strategy&lt;/h2>
&lt;p>The plan was to alter each virtual host defined in IIS to not bind to the typical HTTP/HTTPS ports (80 &amp;amp; 443), but instead have it use arbitrary ports (was to be 8080 &amp;amp; 4433). With that in place, I could then run Apache normally. In order to get traffic to hit the right sites as hosted by IIS, the apache server would have it&amp;rsquo;s own virtual host definitions for each IIS site. In those definitions, there would be a Reverse Proxy config to get Apache to pass the traffic internally over to the arbitrary ports.&lt;/p></description></item><item><title>Ubuntu Samba Apache Active Directory Authentication</title><link>https://dawning.ca/posts/ubuntu-samba-apache-active-directory-authentication/</link><pubDate>Wed, 16 Jul 2008 07:16:25 +0000</pubDate><guid>https://dawning.ca/posts/ubuntu-samba-apache-active-directory-authentication/</guid><description>
&lt;p>So I&amp;rsquo;ve spent some time for something at work figuring out how to get an Ubuntu server to authenticate users with a Windows 2003 Server Active Directory. Using the process I&amp;rsquo;ve found by combining various sources, my instructions show how to get a machine setup such that users logging in to the shell, accessing a samba share and checking out a website (or sub-directory of one) can all be authenticated using credentials centrally stored in a separate Active Directory server.&lt;/p></description></item></channel></rss>