OSX, mail.app, and dovecot

OSX's mail.app can't seem to read files in /var/mail sent by, you guessed it: OSX itself. So, one can install dovecot from MacPorts and do a little configuration. First, set up a self-signed cert.

sudo mkdir -p /opt/local/etc/ssl/certs
sudo mkdir -p /opt/local/etc/ssl/private
sudo openssl req -new -x509 -nodes -config dovecot-openssl.cnf -out /opt/local/etc/ssl/certs/dovecot.pem -keyout /opt/local/etc/ssl/private/dovecot.pem -days 3650

Then, copy the example configuration

sudo cp /opt/local/etc/dovecot/dovecot-example.conf /opt/local/etc/dovecot/dovecot.conf

and make minor mods to dovecot.conf

sudo cp /opt/local/etc/dovecot/dovecot-example.conf /opt/local/etc/dovecot/dovecot.conf
sudo rcsdiff /opt/local/etc/dovecot/dovecot.conf
Password:
===================================================================
RCS file: /opt/local/etc/dovecot/dovecot.conf,v
retrieving revision 1.1
diff -r1.1 /opt/local/etc/dovecot/dovecot.conf
224c224
< #mail_location = 
---
> mail_location = /var/mail/%u
907c907
<     #args = dovecot
---
>     args = login
993c993
<     #args = 
---
>     args = 

And fire dovecot up

sudo port load dovecot

pulledpork lameness

All over the snort.org site it says "In order to manage rules we officially recommend and depend on the user using PulledPork." Well they must assume everyone is registered instead of subscribed as pulledpork doesn't work for subscribers. Lame. Here are the patches to make it work.

# rcsdiff ./pulledpork.pl 
===================================================================
RCS file: ./RCS/pulledpork.pl,v
retrieving revision 1.1
diff -r1.1 ./pulledpork.pl
368c368
<           getstore( "https://www.snort.org/reg-rules/$rule_file/$oinkcode",
---
>           getstore( "https://www.snort.org/sub-rules/$rule_file/$oinkcode",
435c435
<           getstore( "https://www.snort.org/reg-rules/$rule_file.md5/$oinkcode",
---
>           getstore( "https://www.snort.org/sub-rules/$rule_file.md5/$oinkcode",

Eucalyptus 3 notes

Changes made to /etc/eucalyptus/eucalyptus.conf

# rcsdiff -r1.1 eucalyptus.conf
===================================================================
RCS file: RCS/eucalyptus.conf,v
retrieving revision 1.1
diff -r1.1 eucalyptus.conf
55c55
< NODES=""
---
> NODES="172.19.0.2"
157c157
< VNET_MODE="SYSTEM"
---
> VNET_MODE="MANAGED-NOVLAN"
163c163
< VNET_PRIVINTERFACE="eth0"
---
> VNET_PRIVINTERFACE="eth1"
180c180
< VNET_BRIDGE="xenbr0"
---
> VNET_BRIDGE="virbr0"
191c191
< #VNET_PUBLICIPS="your-free-public-ip-1 your-free-public-ip-2 ..."
---
> VNET_PUBLICIPS="my public ips"
196,197c196,197
< #VNET_SUBNET="192.168.0.0"
< #VNET_NETMASK="255.255.0.0"
---
> VNET_SUBNET="172.19.0.0"
> VNET_NETMASK="255.255.0.0"
202c202
< #VNET_ADDRSPERNET="32"
---
> VNET_ADDRSPERNET="256"
206c206
< #VNET_DNS="your-dns-server-ip"
---
> VNET_DNS="my dns server"
211,212c211,212
< #VNET_BROADCAST="192.168.1.255"
< #VNET_ROUTER="192.168.1.1"
---
> VNET_BROADCAST="172.19.255.255"
> VNET_ROUTER="172.19.0.1"

I preferred to use a real class B private IP address as 192.168.0.0 with a subnet mask of 255.255.0.0 isn't a proper private network address.  I set up a simple system: a front end with the CC, SC, etc., and one NC via a crossover cable.

Note: as of this writing, one cannot create bundles on OS X boxen and have them work correctly.  You'll get a 'bad superblock' error...

Also note that that on page 28, there is essentially a typo.  For a MANAGED-NOVLAN setup, there is no need to create a bridge of any sort; xen will do that automatically.  And the "TYPE=Bridge" does not work under CentOS.

To find the latest release of euca2ools, look at http://downloads.eucalyptus.com/software/euca2ools/
For Eucalyptus itself: http://downloads.eucalyptus.com/software/eucalyptus/

Scrollbars in Ubuntu 11++

Here's how one really gets back to the original scrollbars:

sudo bash -c "echo export LIBOVERLAY_SCROLLBAR=0 > /etc/X11/Xsession.d/80overlayscrollbars"

Logout, log back in.

Linux and OS X OCR

Mostly for my notes:

pdftoppm -f 2 -gray AmericanLegion.pdf AL

for i in *.pgm
do
    pnmtotiff $i > ${i%%.pgm}.tif
    rm $i
done


for i in *.tif
do
    tesseract $i ${i%%.tif}
done

Tesseract needs images of decent resolution; e.g.: in PowerPoint it's better to "Save as Pictures" at higher than the default resolution:

iCal alarms for recurring subscribed events

iCal won't alarm on events in subscribed to calendars, such as Facebook.  I guess the originator of the event has to set whether to alarm or not.  So I spent a little time leaning AppleScript, and here's a script that does it.

on run the_calendars
    try
        length of calendars
    on error
        set the_calendars to {"Facebook"}
    end try
    
    set today to (current date)
    set this_day to day of today
    set this_month to month of today
    set to_display to ""
    
    tell application "Calendar"
        repeat with the_calendar in the_calendars
            log the_calendar
            tell calendar the_calendar
                repeat with the_event in every event
                    set the_date to start date of the_event
                    set the_day to day of the_date
                    set the_month to month of the_date
                    
                    if (the_month = this_month and the_day = this_day) then
                        set to_display to (to_display & summary of the_event as string) & return
                    end if
                end repeat
            end tell
        end repeat
    end tell
    
    if (length of to_display > 0) then
        tell application "Finder"
            activate
            with timeout of 86400 seconds
                display dialog to_display
            end timeout
        end tell
    end if
end run

Open up you AppleScript Editor, copy and paste, and save somewhere. Now, you'll need to have it run every day. So I learned a little about launchctl. Save the following script to ~/Library/LaunchAgents. I called mine 'edu.ucar.icalsubscriptions.plist'. You'll need to modify the Program path to where you saved your script, and possibly the time it runs if you don't like 0900. You might also need to change the name of the calendar to match the name of the calendar in iCal -- mine is called Facebook -- and you can have a list of them if you want.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC
     "-//Apple//DTD PLIST 1.0//EN"
     "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
    <dict>
        <key>Label</key>
            <string>edu.ucar.icalsubscriptions</string>

        <key>Program</key>
            <string>/Users/beaty-admin/iCalRecurring.app/Contents/MacOS/applet</string>
            

        <key>ProgramArguments</key>
            <array>
                <string>Facebook</string>
            </array>

        <key>StartCalendarInterval</key>
            <dict>
                <key>Hour</key>
                    <integer>9</integer>
                <key>Minute</key>
                    <integer>0</integer>
            </dict>

        <key>Debug</key>
            <true/>
    </dict>
</plist>

Passwords

People ask me about security, and much of it is based on having good passwords.  In general, one-time passwords are best.  These change each time one logs in; yubikeys and RSA ids are examples.  Two factor -- typically one reusable and one ephemeral (e.g.: SMS text your cell phone) -- are good too.  When we're stuck with reusable (using the same one again and again), then picking good ones is critical.  Good ones are both long and difficult to guess.  Random is best, as we humans aren't as random as we first appear.  As long and random passwords aren't memorable, we need password keepers.  Firefox will remember passwords for you; I recommend you allow it to do this, but: set a master password!  I also recommend using keepass from http://keepass.info/ for whichever platform you have.

So, let's do a little math.  26 lower case letters, 26 upper case, 10 digits, and 10 symbols equals 72 characters.  Let's say you have 8 character random passwords using each of the character classes and no repeated characters.  So, 72*71*70*69*68*67*66*65 -= 482,590,739,030,400 possible passwords.  Not bad.  Now let's go to 20.  72*71*70*69*68*67*66*65*64*63*62*61*60*59*58*57*56*55*54*53 = 759,184,772,617,383,139,127,116,820,643,840,000 possible passwords.  Good enough for the time being.

Below is a password generator written in JavaScript. This assures the password is generated on you machine, in your browser. Choose how long you want your password to be, and what type of characters it needs to contain. Click "Generate!" and then you can cut and paste it into a password field. I recommend against sites that generate passwords on their server -- they have your address and a password of yours. And remember: you don't have to remember it, have your computer do that for you.

Number of characters	12 13 14 15 16 17 18 19 20
Include lowercase
Include uppercase
Include numbers
Include symbols

Password: