From owner-freebsd-doc  Tue Jul 18 12:24:49 1995
Return-Path: doc-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id MAA08406
          for doc-outgoing; Tue, 18 Jul 1995 12:24:49 -0700
Received: from grendel.csc.smith.edu ([131.229.222.23])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA08389
          for <doc@freebsd.org>; Tue, 18 Jul 1995 12:24:47 -0700
Received: from localhost (jfieber@localhost) by grendel.csc.smith.edu (8.6.5/8.6.5) id PAA03277; Tue, 18 Jul 1995 15:25:36 -0400
From: jfieber@grendel.csc.smith.edu (John Fieber)
Message-Id: <199507181925.PAA03277@grendel.csc.smith.edu>
Subject: Re: Documentation
To: mark@grondar.za (Mark Murray)
Date: Tue, 18 Jul 1995 15:25:36 -0400 (EDT)
Cc: doc@freebsd.org
In-Reply-To: <199507181850.UAA07570@grumble.grondar.za> from "Mark Murray" at Jul 18, 95 08:50:01 pm
Content-Type: text
Content-Length: 1363      
Sender: doc-owner@freebsd.org
Precedence: bulk

Mark Murray writes:
> I was wondering about that DES/MD5 section. :-).
> Point me at the problems and I'll fix it.

It starts off really good, but then gets a confusing when
discussing the libraries.  I started changing things but I don't
think there was a net improvement.  Then I've gotten busy.  (I'm
moving in a week and a half; major life transition type of thing.)

A plan C that might work is to reverse the order of topics and
start off with a brief overview checklist:

1. If you do not install *any* of the security distributions:
    * Password encryption is MD5
    * No kerberos support
    * No bdes(1) command
    * /usr/lib/libcrypt.* is a symbolic link to /usr/lib/(whatever it is)
    * ....   

2. If you install the des package:
    * Password encryption is DES
    * You get the bdes(1) command
    * You get new binaries for (....) (because they are statically linked)
    * /usr/lib/libcrypt.* is a symbolic link to....

3. If you install the kerberos package:
    * .....

and so on.  THEN, we can provide the more detailed information
about the implications of the different security packages.  The
text you supplied for the implications is great and can drop in
more or less unmodified.  The subsequent section on kerberos
falls nicely into line as well.

-john

=== jfieber@cs.smith.edu ========== Come up and be a kite!  --K. Bush ===