Debian Services for the Debian Developper
This is my step-by-step guide of setting up typical work environment as a Debian developer (DD).
Following is not tested contents. This is under contraction.
When we became Debian Developper (DD), we knew we obtained few privilages:
- your GPG key in official Debian keyring (This is your source of power)
- package upload privilage,
a cute debian.org mail address, like <username>@debian.org, on MX=master.debian.org
subscription to firstname.lastname@example.org mailing list
- shell accounts on many fast/strange architecture machines.
Well, there is more to it. Let me go through them step-by-step to set up Debian services.
Step 1: New password
You must set your new password through [http://db.debian.org/doc-mail.html mail gateway] first.
$ echo "Please change my Debian password" | gpg --clearsign | mail email@example.com
After validating the request the daemon will generate a new random password, set it in the LDAP directory and respond with an encrypted message containing the new password. (The password can be changed using one of the other interface methods later.)
Please note many of the Debian service have similar [http://db.debian.org/doc-mail.html mail based configuration].
Step 2: Set up your Debian account LDAP data
Configuration of your Debian account can be done through the web interface of [https://db.debian.org/login.html LDAP Debian server] after loging in with your password with "Update my info" button.
- Change password
- Street address
- Postal code
- Latitude / Longitude
- ICQ UIN
- Jabber ID
- Preferred shell
- email forwarded to
- debian-private subscript addr
- IRC nickname
- Web page
- Vacation message
Here you can set your password to a memorable one.
Here you can set up your forwarding mail address for "<yourname>@debian.org" and the subscription mail address for "firstname.lastname@example.org" mailing list, too.
Step 3: Set up your shell accounts
Debian offers shell accounts to the developer using SSH service. See sshd(8) and set up your SSH setup locally on your PC.
The virtual .ssh/authorized_keys file for each user can be set by the Debian LDAP server through [http://db.debian.org/doc-mail.html mail gateway]. For example:
$ gpg --clearsign < .ssh/id_rsa.pub | mail email@example.com
Multiple keys per user are supported, but they must all be sent at once.
Step 4: Setup your email
Although "<yourname>@debian.org" is most common e-mail address used by the DD on Debian system, there are many available mail addresses for you.
<yourname>@debian.org on MX=master.debian.org
<yourname>-<suffix>@debian.org on MX=master.debian.org
<yourname>@people.debian.org on MX=people.debian.org
<yourname>-<suffix>@people.debian.org on MX=people.debian.org
The email to "<yourname>@debian.org" address is forwarded by the data on [http://db.debian.org/ the Debian LDAP server]. This can be easily (re)configured through [http://db.debian.org/doc-mail.html mail gateway]:
$ echo "emailforward: firstname.lastname@example.org" | gpg --clearsign | mail email@example.com
or through the web interface of [https://db.debian.org/login.html LDAP Debian server] as in Step 2. If email forwarding is setup then $HOME/.forward files on the relaying hosts are NOT considered. See also [http://db.debian.org/forward.html Debian GNU/Linux -- Email Forwarding] and Debian DNS set up to figure out exactly how you use all these.
You can test the email routing by using the command
$ /usr/sbin/exim -bt firstname.lastname@example.org
If you set the forwarding address to be a specific Debian machine, e.g., master.debian.org or people.debian.org and do not create a .forward file then that machine will spool the mail to /var/spool/mail instead of creating a mail loop.
Extension addresses <yourname>-<suffix>@debian.org are always routed directly to master.debian.org for processing.
Extension addresses <yourname>-<suffix>@people.debian.org are always routed directly to people.debian.org for processing.
As I see, people.debian.org is less busy than master.debian.org.
If you use procmail for your main mailbox, PLEASE, erase your .forward file and put a .procmailrc in its place instead. This feature has been supported on debian.org machines for a good while now, and will continue to be supported. .procmailrc files won't be synchronised to all hosts in the LDAP directory.
The correct way to invoke procmail for extension addresses is "|/usr/bin/procmail [options]" Ignore the IFS=".." stuff in the procmail man page. ?MailBox formats Email can be saved to mailboxes or maildirs by using the correct lines in a .forward file:
Mailbox format files "/debian/home/foo/Mbox" Maildir format files "/debian/home/foo/MDir/"
To deliver to /var/spool/mail/foo use a construct like '|/usr/bin/procmail -m /dev/null'. Putting the mailbox path will not work. You must use absolute paths for mailboxes, qmail-like ./ paths are not supported by Exim.
Also, 'Exim Filter' files are deliberately turned off.
See /etc/exim4/* on master.debian.org and people.debian.org:
... # Special Features for users: # .forward-foo - is understood as an extension address for email@example.com # .forward-default - is understood to be a catch all for firstname.lastname@example.org # .procmailrc - with no .forward file invokes procmail for delivery # automatically. # For virtual domains the first lookup is done against a linear text # database called 'aliases', then .forward files are consulted. Exim # filtering is available for these .forward files only. .forward-default # is the universal catch all for everything not handled. # For virtual domains the first lookup is done against a linear text # database called 'aliases', then .forward files are consulted. Exim # filtering is available for these .forward files only. .forward-default # is the universal catch all for everything not handled. ...
Step 5: Set up your <yourname>.debian.net domain
Requests can take three forms:
foo in a 22.214.171.124
foo in cname bar.baz.
foo in mx 10 bar.baz.
Here, please note:
- The precise form is critical and must not be deviated from.
- The name collisions are prevented automatically. (Please be considerate to avoid using other DD's account name.)
There is no trailing "debian.net" after "foo".
The trailing dot after "bar.baz".
- You cannot combine CNAME with any other record types.
- Zone entries for multiple hosts are supported, but they must all be sent at once.
- The debian.net zone is only reloaded once per day at midnight -0700.
For example, the followings will to point http://osamu.debian.net to point to the web server of my home machine:
$ cat osamu.txt osamu IN CNAME osamuaoki.dyndns.org $ gpg --clearsign <osamu.txt | mail email@example.com
Although there was neat BSMTP setup in klecker.debian.org described in [http://lists.debian.org/debian-devel/2001/debian-devel-200102/msg00965.html BSMTP on debian.net], this klecker.debian.org is currently restricted machine without SSH access. The alternative seems to be gluck.debian.org (alias: klecker.debian.org ), so far I could not get BSMTP working on this host.
Step 5: Set up your PC to accept mail to <yourname>.debian.net domain
You need to set your local PC to accept mails addressed to "<yourname>.debian.net" including ones for "root".
See exim4 configuration.
$ sudo dpkg-reconfigure exim-config
Then, under "Configuring Exim v4 (exim4-config)" menu, you add "<yourname>.debian.net" to the list separated by colon.
Step 6: Set up script to do BSMTP
You obtain BSMTP script run on Debian server from:
I have modified it to be host name neutral ($FILE can be set from argument).
set -e DIR="$HOME/bsmtp" FILE="$1" TRANSIT="$FILE.transit" cd "$DIR" || exit 0 # Is there anything to send? [ -s "$FILE" ] || exit 0 lockfile-create "$FILE" lockfile-touch "$FILE" & TOUCH="$!" trap 'kill "$TOUCH"; lockfile-remove "$FILE"' EXIT ERR HUP INT QUIT TERM if [ -f "$TRANSIT" ]; then cat "$FILE" >> "$TRANSIT" && rm -f "$FILE" else mv -f "$FILE" "$TRANSIT" fi cat "$TRANSIT" rm -f "$TRANSIT" exit 0
You obtain BSMTP script run on your local PC from:
Here I adjusted to match above change.
# Depends: lockfile-progs, ssh set -e if [ -z "$1" ]; then echo "Usage: $0 hostname" 2>&1 exit 1 fi DIR="$HOME/tmp/.bsmtp" mkdir -p "$DIR" cd "$DIR" HOST="$1" VHOST="$2" # TODO: Note that this scheme may currently lose mail if the local disk # fills up! This is obviously very bad. Fix this. # By default, lockfile-create gives up after three minutes, so don't cron # this any more frequently than that without supplying a --retry argument. lockfile-create "$HOST" # Race condition pointed out by pjb: this doesn't guarantee that the lock is # held before the critical section starts. lockfile-touch "$HOST" & TOUCH="$!" trap 'kill "$TOUCH"; lockfile-remove "$HOST"' EXIT ERR HUP INT QUIT TERM #ssh -2 -i "$HOME/.ssh/id-bsmtp-$HOST" -C "$HOST" bsmtp-pull-server "$VHOST" > "$HOST" # Since above did not work for me I tried ssh -2 -C "$HOST" bsmtp-pull-server "$VHOST" > "$HOST" [ -s "$HOST" ] || exit 0 /usr/sbin/sendmail -bS -odq < "$HOST" rm -f "$HOST" exit 0
FIXME: I do not see $HOME/bsmtp directory in gluck I am stack here!
Now you can invoke following to retrieve your message.
$ ~/bin/bsmtp-pull <yourname>@people.debian.org <yourname>.debian.net
Now you have mail address on which you do not rely any external resorces.
These days, the value of this setup has been more for the security and stability.
If it is just to get subscription to high volume Debian ML, I would use free (commercial) service such as gmail.com.
Since above script is designed to work with SSH key named "$HOME/.ssh/id-bsmtp-$HOST", we make link:
$ cd ~/.ssh $ ln -f id_dsa id-bsmtp-gluck.debian.org
Here I assumed you have set up $HOME/id_dsa.pub as the SSH public key described in Step 3. If you make custom SSH keys for Debian activity, that is even better.
Let's login to debian machine to see how other people are doing. (Here, people.debian.org.)
Let's see how people uses this host for BSMTP by "cat /etc/exim/bsmtp" and check their domain set up. (I am not publishing exact content of these and hiding some contents here Try these command yourself.):
osamu@gluck:exim$ cat bsmtp r****.debian.net: user=d** group=Debian file=/home/d**/bsmtp/r*****.debian.net s*****.debian.net: user=b** group=Debian file=/home/b**/bsmtp/s*****.debian.net ... r***.debian.net: user=c******* group=Debian file=/home/c*******/bsmtp/r***.debian.net ... osamu@gluck:exim$ dig r***.debian.net ANY ... ;; QUESTION SECTION: ;r***.debian.net. IN ANY ;; ANSWER SECTION: r***.debian.net. 3600 IN MX 0 gluck.debian.org. ... osamu@gluck:exim$ dig s*****.debian.net ANY ... ;; QUESTION SECTION: ;s*****.debian.net. IN ANY ;; ANSWER SECTION: s*****.debian.net. 3600 IN MX 10 s*****.a****.org .au. s*****.debian.net. 3600 IN MX 20 s*****.m****** u*****.com.au. s*****.debian.net. 3600 IN MX 30 alts*****.m***** o*********.com.au. s*****.debian.net. 3600 IN MX 0 gluck.debian.org. s*****.debian.net. 3600 IN TXT "PGP ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** **" s*****.debian.net. 3600 IN TXT "PGP **** **** **** **** **** **** **** **** ****" s*****.debian.net. 3600 IN TXT "******** <firstname.lastname@example.org>" s*****.debian.net. 3600 IN A 2**.1**.1**.8* ...
The first one is for one with just fast internet connection without any SMTP mail hosts to get BSMTP service via Debian host as described above.
The second one is for you with semi-stable fixed IP SMTP mail hosts. This ensures mail delivary to the home PC on Cable/DSL/Optical connection (with some risk).
[:OsamuAoki: Osamu Aoki]