IMPORTANT NOTE: This is not an official release of Pine, and will not be supported by the Pine development team or help@cac. It is a modified version of version 4.40 which includes a small amount of code from a 4.41 prerelease, and as such it may be unstable or dangerous. I personally think it should be ok to use, but you use it at your own risk.

If you would like to test my build of Pine 4.40 with ssl, ldap and kerberos supportfor OS X 10.1 (this will almost certainly not work on 10.0 - 10.0.4), here are some quick steps:

1) download pine4.40-jdl.tar.gz
2) download ssl-certs.tar.gz
3) In a terminal window, go to the directory where you downloaded the files. This will probably be /Users/YOURUSERNAME/Desktop/
4) Type the following command:

sudo tar zxvPf ssl-certs.tar.gz

tar zxvf pine4.40-jdl.tar.gz
sudo mv pine pico pilot /usr/bin

These are notes I took while I was trying to get Pine to build. I cleaned them up a bit after I got it working, but not an awful lot. They may or may not be useful for you if you want to build Pine yourself.

Note: I'm using the tcsh shell which came with 10.1, so if (like any sane person would) you've installed and switched to bash, look for any tcsh-isms in the instructions below and translate them to bash. "setenv" becomes "export", for example.

A number of these steps seem to expect perl to be in /usr/local/bin/. Let's make a symlink so they don't fail:

sudo mkdir -p /usr/local/bin
sudo ln -s /usr/bin/perl /usr/local/bin/perl

+ First thing, fix the openssl installation.

get and unpack openssl-0.9.6b.tar.gz from http://www.openssl.org/source/

Go into the openssl source directory:

cd openssl-0.9.6b

sudo cp -r include /System/Library/OpenSSL/

sudo ln -s /System/Library/OpenSSL/include/openssl /usr/include/openssl

ln -s /usr/bin/openssl apps/

make rehash

tar -cf - certs/ | ( cd /System/Library/OpenSSL/ ; sudo tar -xvf - )

+ Let's try building some ldap libraries, so we can enable ldap support

Ok, we're going to need some outside help for this step. Let's grab ltconfig and ltmain.sh (we'll be using them shortly) from http://fink.sourceforge.net/doc/porting/libtool.php

get and unpack openldap from http://www.openldap.org/software/download/ (I'm using openldap-stable-20010926.tgz, which corresponds to version 2.0.15, because that's what was current when I started).

cd openldap-2.0.15

cp /PATH/TO/ltconfig /PATH/TO/ltmain.sh build/

./configure --disable-slapd --disable-slurpd
make depend

make

sudo make install

+ Whee, on to Pine!

Download and unpack the pine source. I'm using 4.40. 4.41 should be out soon; if there are tricks required to get it working, I'll write up a new document once it's released.

cd pine4.40

chmod +w imap/src/osdep/unix/Makefile.ssl
emacs imap/src/osdep/unix/Makefile.ssl

SSLDIR=/System/Library/OpenSSL
SSLLIB=/usr/lib

Now, make a symlink to the openldap source in your pine directory:

ln -s /PATH/TO/openldap-2.0.15 ldap

Let's see if I can get kerberos support working. (This is fixed in 4.41; I got it working in 4.40 by stealing all the gss files from a prerelease 4.41 and using them in the 4.40 tree. This won't work for those of you playing along at home.)

First thing, download the latest package from MIT at http://web.mit.edu/network/kerberos-form.html. We want the "MIT Kerberos for Macintosh 4.0a19 Release", or whatever's current.

Ok, filled out the form, downloaded 4.0.a19 from MIT, installed it.

Make a symlink from /usr to pine4.40/krb5, as per contrib/krb5-setup Woop, except the include files aren't in /usr/include, they're in /usr/include/Kerberos (the libraries are in /usr/lib, though). Bah.

Ok, edit imap/src/osdep/unix/Makefile.gss and add that path to the CFLAGS:

GSSCFLAGS= -I$(GSSDIR)/include -I/usr/include/Kerberos

EXTRALDFLAGS="-flat_namespace"

setenv LDFLAGS "-flat_namespace"

./build osx SSLTYPE=unix

I know very little about kerberos. I'm amazed that I got it working here. Heh. I borrowed this configuration file from another machine, one where kerberos worked. I don't know what any of this means, but it seems to make things work on my machine. This is the file "/Library/Preferences/edu.mit.Kerberos" from my OS X machine:

[logging]
 default = FILE:/var/log/krb5libs.log
 kdc = FILE:/var/log/krb5kdc.log
 admin_server = FILE:/var/log/kadmind.log

[libdefaults]
 ticket_lifetime = 24000
 default_realm = u.washington.edu
 dns_lookup_realm = false
 dns_lookup_kdc = false
 default_tkt_enctypes = des-cbc-crc
 default_tgs_enctypes = des-cbc-crc

[realms]
	u.washington.edu = {
		kdc = k5-kdc1.u.washington.edu
		kdc = k5-kdc2.u.washington.edu
		admin_server = k5-admin.u.washington.edu
		kpasswd_server = k5-admin.u.washington.edu
		default_domain = u.washington.edu
		v4_instance_convert = {
			u = u.washington.edu
		}
	}

[domain_realm]
	.cac.washington.edu = u.washington.edu
	.u.washington.edu = u.washington.edu
	.alumni.washington.edu = u.washington.edu
	.washington.edu = u.washington.edu


[login]
	krb5_get_tickets = false

[kdc]
 profile = /var/kerberos/krb5kdc/kdc.conf

kinit jdlarios@u.washington.edu

klist

In my pine configuration, I have a mailbox set up as:

{jdlarios.deskmail.washington.edu/ssl/user=jdlarios}

That's pretty much all I know about kerberos. Here's what I know about ldap:

From the Pine main menu, hit "S" to go to Setup and "D" to go to Directory. Hit "A" to add a new directory. For "ldap-server" enter "directory.washington.edu". For "search-base" enter "o=University of Washington, c=US". Give it a nickname (mine is uw-ldap), and check the "use-implicitly-from-composer" feature.

Now when you compose mail, you can type a partial address, or a name, and pine will search the ldap directory and give you a list of possible matches. Pretty neat.

And that's about all I know about ldap.