+++ /dev/null
-Placehold that will explain how to build an agile server goes here.
-zephyr (3.0~rc.2544-1) notyet; urgency=low
+zephyr (3.0~rc.2544-1) unstable; urgency=low
* New upstream.
+ * Supplementary readme cleanup.
+ * Drop *-krb packages for real. Closes: #535099
* GC obsolete conffiles; Closes: #538028
+ * Up Standards-Version.
- -- Karl Ramm <kcr@1ts.org> Thu, 27 Aug 2009 14:50:04 -0400
+ -- Karl Ramm <kcr@debian.org> Wed, 02 Sep 2009 14:41:48 -0400
zephyr (3.0~beta.2483-2) unstable; urgency=low
Build-Depends: debhelper (>= 5), libc-ares-dev, libkrb5-dev (>= 1.2.2-4), comerr-dev, ss-dev,
libreadline5-dev, libx11-dev, libxt-dev, x11proto-core-dev, libncurses5-dev,
bison, libhesiod-dev, autotools-dev
-Standards-Version: 3.8.1.0
+Standards-Version: 3.8.2.0
Vcs-Svn: svn://svn.1ts.org/debian/branches/zephyr-reloaded/zephyr
Package: libzephyr4
.
This package provides the libraries without Kerberos support.
-Package: libzephyr4-krb
-Section: libs
-Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, krb4-config
-Conflicts: libzephyr4, libzephyr4-krb5, libzephyr4-krb45
-Replaces: libzephyr4, libzephyr4-krb5, libzephyr4-krb45
-Provides: libzephyr4
-Description: Project Athena's notification service - libraries with Kerberos
- Zephyr is derived from the original Project Athena 'Instant Message' system
- and allows users to send messages to other users or to groups of users.
- Users can view incoming Zephyr messages as windowgrams (transient X
- windows) or as text on a terminal.
- .
- This package provides libraries that use Kerberos 4 and is deprecated.
-
Package: libzephyr4-krb5
Section: libs
Architecture: any
clients. All zephyrgrams are sent to the server to be routed to the
intended recipient. Only one server is required for a group of clients.
-Package: zephyr-server-krb
-Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, debconf | debconf-2.0, libzephyr4-krb
-Conflicts: zephyr-server, zephyr-server-krb5, zephyr-server-krb45
-Replaces: zephyr-server, zephyr-server-krb5, zephyr-server-krb45
-Provides: zephyr-server
-Description: Project Athena's notification service - server with Kerberos
- Zephyr is derived from the original Project Athena 'Instant Message' system
- and allows users to send messages to other users or to groups of users.
- Users can view incoming Zephyr messages as windowgrams (transient X
- windows) or as text on a terminal.
- .
- This package provides the server for the messaging service. Only one
- server is needed for a group of client. The program consumes much memory,
- especially for very large sites.
- .
- The server maintains a location and subscription database for all the
- receiving clients. All zephyrgrams are sent to the server to be routed
- to the intended recipient.
- .
- This version of the server uses Kerberos 4 and is deprecated.
-
Package: zephyr-server-krb5
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}, debconf | debconf-2.0, libzephyr4-krb5
# Uncomment this to turn on verbose mode.
#export DH_VERBOSE=1
VARIETALS=krb5
-#VARIETALS=krb krb45 krb5
+#VARIETALS=krb45 krb5
PACKAGES:=-plibzephyr4 -pzephyr-clients -pzephyr-server -plibzephyr-dev $(foreach i,$(VARIETALS),-plibzephyr4-$(i) -pzephyr-server-$(i))
--with-ares=/usr --with-hesiod=/usr --enable-cmu-zwgcplus
CONFIGURE_krb5=--with-krb5=/usr
CONFIGURE_krb45=--with-krb4=/usr --with-krb5=/usr
-CONFIGURE_krb=--with-krb4=/usr
# see /usr/share/doc/autotools-dev/README.Debian.gz
export DEB_HOST_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE)
confflags += --build $(DEB_BUILD_GNU_TYPE) --host $(DEB_HOST_GNU_TYPE)
endif
+BUILD_VARIETALS=$(VARIETALS) no-krb
# The autotools target adds forced build-time dependencies on
# autotools-dev (for /usr/share/misc/config.*) and devscripts (for dch)
configure-stamp:
dh_testdir
# Add here commands to configure the package.
- for i in $(foreach i,$(VARIETALS),"$i:$(CONFIGURE_$i)"); do \
- IFS=: ; set $$i ; \
- mkdir $$1 || true; \
- (cd $$1 && CFLAGS="-g -O" ../configure $$2 $(CONFIGURE_ROOT)); \
- done
- -mkdir no-krb
- cd no-krb && CFLAGS="-g -O" ../configure $(CONFIGURE_ROOT)
+ mkdir -p $(BUILD_VARIETALS)
+ $(foreach VARIETY,$(BUILD_VARIETALS),(cd $(VARIETY) && CFLAGS="-g -O" ../configure $(CONFIGURE_$(VARIETY)) $(CONFIGURE_ROOT));)
touch configure-stamp
build: configure-stamp build-stamp
-rm -f build-stamp configure-stamp
# Add here commands to clean up after the build process.
- -rm -rf $(VARIETALS) no-krb debian/tmp-krb*
- -rm debian/zephyr-server-krb.files
- -rm debian/zephyr-server-krb.templates
- -rm debian/zephyr-server-krb.config
- -rm debian/zephyr-server-krb.postinst
- -rm debian/zephyr-server-krb5.*
- -rm debian/zephyr-server-krb45.*
- -rm debian/libzephyr4-krb.files debian/libzephyr4-krb5.files debian/libzephyr4-krb45.files
+ -rm -rf $(BUILD_VARIETALS) debian/tmp-krb*
+ -rm $(foreach v,$(VARIETALS),$(foreach s,files templates config postinst,debian/zephyr-server-$(v).$(s)))
+ -if test -n "$(filter-out krb5,$(VARIETALS))"; then \
+ rm $(foreach v,$(filter-out krb5,$(VARIETALS)),$(foreach s,docs init postrm,debian/zephyr-server-$(v).$(s))); \
+ fi
+ -rm debian/libzephyr4-krb5.files debian/libzephyr4-krb45.files
dh_clean
for dir in $(VARIETALS); do \
cp -rp debian/tmp/etc/zephyr/acl debian/tmp-$$dir/etc/zephyr; \
done
-
+
# Build architecture-independent files here.
# Pass -i to all debhelper commands in this target to reduce clutter.
binary-indep: build install
cp debian/zephyr-server.$$file debian/zephyr-server-$$dir.$$file; \
done; \
done
- for file in README.Debian docs init postrm; do \
- for dir in $(filter-out krb,$(VARIETALS)); do \
- cp debian/zephyr-server-krb.$$file debian/zephyr-server-$$dir.$$file; \
+ for file in docs init postrm; do \
+ for dir in $(filter-out krb5,$(VARIETALS)); do \
+ cp debian/zephyr-server-krb5.$$file debian/zephyr-server-$$dir.$$file; \
done; \
done
for dir in $(VARIETALS); do \
+++ /dev/null
-To run a zephyr server with MIT Kerberos support, you need to generate a
-Kerberos IV srvtab for the principal zephyr.zephyr@YOUR.REALM.NAME.
-
-Doing this with the MIT Kerberos V server is a somewhat convoluted process,
-but here we go:
-
-[Note that this presumes that you have Kerberos administrator privileges, if
-you don't, find someone who does.]
-
-At the kadmin prompt, type
-
-ank -randkey zephyr/zephyr
-
-this creates the Kerberos principal, with whatever key types and cryptosystems
-your realm defaults to. Next, also at the kadmin prompt, type the following
-substituting appropriately for your realm name and various file locations:
-
-xst -k /tmp/keytab -e des-cbc-crc:v4 zephyr/zephyr@YOUR.REALM.NAME
-
-The key type is necessary because zephyr uses an older version of Kerberos
-that used only single-DES. Now run ktutil:
-
-rkt /tmp/keytab
-wst /etc/zephyr/srvtab
-q
-
-You now want to make sure that the /tmp/keytab file is written-over and
-removed. Fortunately, you have Kerberos, you have kdestroy.
-
-env KRB5CCNAME=/tmp/keytab kdestroy
--- /dev/null
+To run a zephyr server with MIT Kerberos IV and V support, you need to
+generate a Kerberos V keytab and a Kerberos IV srvtab for the
+principal zephyr.zephyr@YOUR.REALM.NAME.
+
+Doing this with the MIT Kerberos V server is a somewhat convoluted
+process, but here we go:
+
+[Note that this presumes that you have Kerberos administrator privileges, if
+you don't, find someone who does.]
+
+At the kadmin prompt, type
+
+ank -randkey zephyr/zephyr
+
+this creates the Kerberos principal, with whatever key types and cryptosystems
+your realm defaults to. Next, also at the kadmin prompt, type the following
+substituting appropriately for your realm name and various file locations:
+
+xst -k /etc/zephyr/krb5.keytab -e des-cbc-crc:v4 zephyr/zephyr@YOUR.REALM.NAME
+
+The key type is necessary because zephyr Kerberos IV uses only
+single-DES. Now run ktutil:
+
+rkt /etc/zephyr/krb5.keytab
+wst /etc/zephyr/srvtab
+q
+
+The krb5.keytab and srvtab files need to be the same on all of your
+zephyr servers; note that with the MIT kerberos server, xst changes
+the key each time, invalidating previously-extracted keytabs.
--- /dev/null
+To run a zephyr server with MIT Kerberos support, you need to generate
+a keytab for the principal zephyr/zephyr@YOUR.REALM.NAME.
+
+Doing this with the MIT Kerberos V server is a slightly convoluted
+process, but here we go:
+
+[Note that this presumes that you have Kerberos administrator
+privileges, if you don't, find someone who does.]
+
+At the kadmin prompt, type
+
+ank -randkey zephyr/zephyr
+
+this creates the Kerberos principal, with whatever key types and
+cryptosystems your realm defaults to. Next, also at the kadmin
+prompt, type the following substituting appropriately for your realm
+name and various file locations:
+
+xst -k /etc/zephyr/krb5.keytab zephyr/zephyr@YOUR.REALM.NAME
+
+The keytab files need to be the same on all of your zephyr servers;
+note that with the MIT kerberos server, xst changes the key each time,
+invalidating previously-extracted keytabs.
start)
if test ! -f /etc/zephyr/srvtab
then
- echo 'You need to get a srvtab before the kerberized zephyr server will function'
- echo 'correctly. Get a srvtab for zephyr/zephyr and put it in /etc/zephyr/srvtab.'
+ echo 'You need to get a keytab before the kerberized zephyr server will function'
+ echo 'correctly. Get a keytab for zephyr/zephyr and put it in /etc/zephyr/krb5.keytab.'
exit 0
fi
echo -n "Starting $DESC: "