<?xml version="1.0" encoding="iso-8859-1" ?>
<rss version="2.0" 
   xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule" 
   xmlns:html="http://www.w3.org/1999/html" 
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" 
   xmlns:slash="http://purl.org/rss/1.0/modules/slash/">
<channel>
   <title>Phil Groce</title>
   <link>http://philgroce.com/blog</link>
   <description>programming, computing and vanity blogging</description>
   <language>en</language>
   <copyright>Copyright 2006-2008 Phil Groce. All Rights Reserved.</copyright>
   <ttl>60</ttl>
   <pubDate>Mon, 17 Nov 2008 15:53 GMT</pubDate>
   <managingEditor>p.groce+blog@gmail.com</managingEditor>
   <generator>PyBlosxom http://pyblosxom.sourceforge.net/ 1.4.3 01/10/2008</generator>
<item>
   <title>SSH: "open failed: administratively prohibited"</title>
   <guid isPermaLink="false">geekery/ssh-administratively-prohibited</guid>
   <link>http://philgroce.com/blog/geekery/ssh-administratively-prohibited.pg</link>
   <description><![CDATA[
<p>Apparently, you can get this error for a <a href="http://jimbojw.com/wiki/index.php?title=Channel_5:_Open_Failed:_Administratively_Prohibited">number</a> <a href="http://muzso.hu/2008/10/13/open-failed-administratively-prohibited-error-with-ssh-dynamic-port-forwarding">of</a> <a href="http://readlist.com/lists/redhat.com/fedora-list/33/167275.html">reasons</a> . The obvious one is that you don&#8217;t have <code>AllowTCPForwarding</code> set in your <code>sshd_config</code>. A less obvious but probably more common one&#8212;which bit me earlier today, which is why I write this&#8212;is that you&#8217;ve misspelled a host name. To wit, this:</p>

<pre>
<code>
ssh example.com -L8000:locahost:80
</code>
</pre>

<p>&#8230;is not the same as:</p>

<pre>
<code>
ssh example.com -L8000:localhost:80
</code>
</pre>

<p>(Discussing this with my colleagues prompted a joke about living &#8220;La Vida Local.&#8221; Finally, a Ricky Martin song for shut-ins.)</p>
]]></description>
   <category domain="http://philgroce.com/blog"></category>
   <pubDate>Mon, 17 Nov 2008 15:53 GMT</pubDate>
</item>
<item>
   <title>PyBlosxom Recent Posts Plugin</title>
   <guid isPermaLink="false">geekery/python/pyrecentposts</guid>
   <link>http://philgroce.com/blog/geekery/python/pyrecentposts.pg</link>
   <description><![CDATA[
<p>I&#8217;ve been using <a href="http://pyblosxom.sourceforge.net/">PyBlosxom</a> to run this blog and, increasingly, the static content of the site.</p>

<p>PyBlosxom tries to do as little as possible in the core, saving most features for its plugin framework. Nice technically, but leaving features up to &#8220;the community&#8221; to implement sometimes leaves some frustrating holes, as I discovered when I searched in vain for a plugin to implement &#8220;recent posts&#8221; functionality.</p>

<p>The upside is that it was really easy to implement&#8212;about 100 lines of Python. It&#8217;s available from the <a href="/static/software">software</a> page if you want to run it yourself; if you have any questions about it, feel free to contact me. about it.</p>

<p><strong>Update</strong>: I posted about my plugin to <a href="http://news.gmane.org/gmane.comp.web.pyblosxom.devel">pyblosxom-devel</a> and they added it to the <a href="http://pyblosxom.sourceforge.net/registry/display/pyrecentposts.html">plugins list</a>. w00t, as the kids say. If you&#8217;re coming here looking for more information on the plugin, I suggest you read the docstring comments of the  <a href="/software/pyrecentposts.py">plugin itself</a>.</p>
]]></description>
   <category domain="http://philgroce.com/blog">python</category>
   <pubDate>Thu, 05 Jun 2008 02:22 GMT</pubDate>
</item>
<item>
   <title>Update your Flash Plugins!</title>
   <guid isPermaLink="false">geekery/security/update-your-flash</guid>
   <link>http://philgroce.com/blog/geekery/security/update-your-flash.pg</link>
   <description><![CDATA[
<p>Flash is a dangerous little piece of software. It&#8217;s ubiquitous enough that an attacker can get quite a return from exploiting it, but (like most other browser plugins, sadly) it&#8217;s not always on people&#8217;s radar to keep updated.</p>

<p>As if that wasn&#8217;t bad enough, Will Dormann from <span class="caps">CERT</span> points out that even when you think to do it, <a href="https://www.cert.org/blogs/vuls/2008/05/is_your_adobe_flash_player_upd.html">keeping Flash updated can be tricky</a>:</p>

<blockquote>
<p>It is important to realize that a system may contain several instances of the Adobe Flash Player. The Adobe Flash Player plug-in installer for Windows will install only the Netscape-style plug-in for Flash, which is used by Mozilla Firefox, Opera, and other browsers that support plug-ins. The Adobe Flash Player ActiveX installer for Windows will install only the ActiveX version of Flash, which is used by Internet Explorer and other programs that use Internet Explorer components.</p>
</blockquote>

<p>Firefox&#8217;s plugin flexibility further complicates matters:</p>

<blockquote>
<p>Another cause for confusion is that Firefox allows plug-ins to be installed either system-wide or in a specific user&#8217;s profile. As a result, a Flash plug-in that was installed in one manner may not be updated properly if the new version of Flash is installed in a different manner. Other browsers may have similar issues.</p>
</blockquote>

<p>Will concludes by advocating that you, &#8221;[a]t the very least, make sure that you have attempted to upgrade to the latest version of Adobe Flash.&#8221; And while you&#8217;re at it, Lord Cardigan, could you just <a href="http://www.poetryarchive.org/poetryarchive/singlePoem.do?poemId=1570">ride your horses through that valley over there</a> ?</p>

<p>At any rate, make the effort, like the man said. Flash is a dangerous little piece of software.</p>
]]></description>
   <category domain="http://philgroce.com/blog">security</category>
   <pubDate>Fri, 30 May 2008 02:26 GMT</pubDate>
</item>
</channel>
</rss>
