<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>ptone &#187; sysadmin</title>
	<atom:link href="http://ptone.com/dablog/tag/sysadmin/feed/" rel="self" type="application/rss+xml" />
	<link>http://ptone.com/dablog</link>
	<description>Hodgepodge of thoughts, technical notes, and random observations</description>
	<lastBuildDate>Mon, 10 May 2010 18:27:56 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Launching OE-Cake</title>
		<link>http://ptone.com/dablog/2009/09/launching-oe-cake/</link>
		<comments>http://ptone.com/dablog/2009/09/launching-oe-cake/#comments</comments>
		<pubDate>Wed, 09 Sep 2009 17:24:25 +0000</pubDate>
		<dc:creator>ptone</dc:creator>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[osx]]></category>
		<category><![CDATA[sysadmin]]></category>

		<guid isPermaLink="false">http://ptone.com/dablog/2009/09/launching-oe-cake/</guid>
		<description><![CDATA[OE-Cake is still expired for OS X &#8211; lets work around that



So OE-Cake now has a beta for windows &#8211; but not OS X.

We still have the binary from their old version that expired some time ago &#8211; we were launching it with ARD with the below trick, but now I&#8217;ve moved it into a [...]]]></description>
			<content:encoded><![CDATA[<p>OE-Cake is still expired for OS X &#8211; lets work around that</p>

<p><span id="more-86"></span></p>

<p>So OE-Cake now has a beta for windows &#8211; but not OS X.</p>

<p>We still have the binary from their old version that expired some time ago &#8211; we were launching it with ARD with the below trick, but now I&#8217;ve moved it into a read-only applescript application that the students can launch themselves:</p>

<pre><code>try
    do shell script "sudo date 1103100008" user name "admin" password "*****" with administrator privileges
end try

do shell script "open /Applications/OE-CAKE\\!.app"
delay 10
do shell script "launchctl stop org.ntp.ntpd" user name "admin" password "*****" with administrator privileges
do shell script "launchctl start org.ntp.ntpd" user name "admin" password "*****" with administrator privileges
</code></pre>
]]></content:encoded>
			<wfw:commentRss>http://ptone.com/dablog/2009/09/launching-oe-cake/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Making Google Earth work for us</title>
		<link>http://ptone.com/dablog/2009/09/making-google-earth-work-for-us/</link>
		<comments>http://ptone.com/dablog/2009/09/making-google-earth-work-for-us/#comments</comments>
		<pubDate>Wed, 09 Sep 2009 00:02:07 +0000</pubDate>
		<dc:creator>ptone</dc:creator>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[osx]]></category>
		<category><![CDATA[sysadmin]]></category>

		<guid isPermaLink="false">http://ptone.com/dablog/2009/09/making-google-earth-work-for-us/</guid>
		<description><![CDATA[In our school environment, we had a couple issues with Google Earth&#8217;s default behaviors &#8211; here are my workarounds.



First off we have a student web proxy that works based on a whitelist concept.  So we have to allow any web traffic explicitly.  With the help of little snitch and one incomplete help page [...]]]></description>
			<content:encoded><![CDATA[<p>In our school environment, we had a couple issues with Google Earth&#8217;s default behaviors &#8211; here are my workarounds.</p>

<p><span id="more-84"></span></p>

<p>First off we have a student web proxy that works based on a whitelist concept.  So we have to allow any web traffic explicitly.  With the help of little snitch and one incomplete help page from google, here is what I&#8217;ve added to our global whitelist and seems to be allowing all the features:</p>

<ul>
<li>kh.google.com</li>
<li>www.keyhole.com</li>
<li>mw2.google.com</li>
<li>earth.google.com</li>
<li>auth.keyhole.com</li>
<li>maps.google.com</li>
<li>khmdb.google.com</li>
</ul>

<p>It also want access to www.google.com &#8211; but we don&#8217;t allow students to full google access &#8211; but Google Earth still seems to run fine.</p>

<p>The next annoyance was Google&#8217;s softwareupdate which wants to run for all users and update Google Earth on launch.</p>

<p>Adding the following to our loginhook fixed that:</p>

<pre><code>mkdir -P $nethomedir/Library/Google/
touch $nethomedir/Library/Google/GoogleSoftwareUpdate
chown root $nethomedir/Library/Google/GoogleSoftwareUpdate
chmod 644 $nethomedir/Library/Google/GoogleSoftwareUpdate
</code></pre>

<p>the $nethomedir var is fetched from dscl earlier in the script</p>

<p>Students need to have stored the proxy password in their keychain &#8211; but most have already done that when visiting a web page earlier.  They then just need to allow Google Earth to access their keychain.</p>
]]></content:encoded>
			<wfw:commentRss>http://ptone.com/dablog/2009/09/making-google-earth-work-for-us/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>simple weak password generator</title>
		<link>http://ptone.com/dablog/2009/09/simple-weak-password-generator/</link>
		<comments>http://ptone.com/dablog/2009/09/simple-weak-password-generator/#comments</comments>
		<pubDate>Thu, 03 Sep 2009 21:04:39 +0000</pubDate>
		<dc:creator>ptone</dc:creator>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[sysadmin]]></category>

		<guid isPermaLink="false">http://ptone.com/dablog/2009/09/simple-weak-password-generator/</guid>
		<description><![CDATA[There are times I need to create some easy to remember weak initial passwords for students &#8211; here is a quick script



Note that these are not strong passwords as they are the definition of &#8220;dictionary&#8221; passwords&#8230;

import sys
import os
import random

dfile = '/usr/share/dict/web2'

def main():
    for x in range(130):
       [...]]]></description>
			<content:encoded><![CDATA[<p>There are times I need to create some easy to remember weak initial passwords for students &#8211; here is a quick script</p>

<p><span id="more-83"></span></p>

<p>Note that these are not strong passwords as they are the definition of &#8220;dictionary&#8221; passwords&#8230;</p>

<pre><code>import sys
import os
import random

dfile = '/usr/share/dict/web2'

def main():
    for x in range(130):
        winner = False
        MAX = 234936
        suffix = random.randint (10,100)
        while not winner:
            choice = random.randint(1,MAX)
            f = open(dfile)
            for i,l in enumerate(f):
                l = l.strip()
                length = len(l)
                if i &lt; choice:
                    continue
                if length &gt; 3 and length &lt; 7:
                    winner = '%s%d' % (l,suffix)
                    break
        f.close()
        print winner.lower()


if __name__ == '__main__':
    main()
</code></pre>
]]></content:encoded>
			<wfw:commentRss>http://ptone.com/dablog/2009/09/simple-weak-password-generator/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Managing mailman on the command line</title>
		<link>http://ptone.com/dablog/2009/08/managing-mailman-on-the-command-line/</link>
		<comments>http://ptone.com/dablog/2009/08/managing-mailman-on-the-command-line/#comments</comments>
		<pubDate>Mon, 24 Aug 2009 17:14:00 +0000</pubDate>
		<dc:creator>ptone</dc:creator>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[sysadmin]]></category>

		<guid isPermaLink="false">http://ptone.com/dablog/2009/08/managing-mailman-on-the-command-line/</guid>
		<description><![CDATA[Even though we moved our email from OS X server to google apps for education &#8211; we still manage our lists with a local mailman instance (still on 10.4).  However the web based interface for adding new members can be a bit of a pain as it never seems to remember the right authorization [...]]]></description>
			<content:encoded><![CDATA[<p>Even though we moved our email from OS X server to google apps for education &#8211; we still manage our lists with a local mailman instance (still on 10.4).  However the web based interface for adding new members can be a bit of a pain as it never seems to remember the right authorization when switching between lists &#8211; luckily mailman has some great command line tools.</p>

<p><span id="more-82"></span></p>

<p>These are documented here:</p>

<p><a href="http://www.list.org/site.html">http://www.list.org/site.html</a></p>

<p>They are located in /usr/share/mailman/bin/</p>

<p>so you may want to add that to your path in .bash_profile</p>

<p>most have decent help summary with &#8211;help arg at command line</p>

<p>while the remove_members command accepts addresses on the command line itself:</p>

<pre><code>remove_members [options] [listname] [addr1 ...]

remove_members staff frank@foo.com
</code></pre>

<p>The add_members command specifically wants file input.  Sometimes I just want to add 2-3 so I use this trick:</p>

<pre><code>add_members -r - staff &lt;&lt;-EOF
&gt;sue@foo.com
&gt;bob@bar.com
&gt; &lt;cntl-d&gt;
</code></pre>
]]></content:encoded>
			<wfw:commentRss>http://ptone.com/dablog/2009/08/managing-mailman-on-the-command-line/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
