From owner-freebsd-current  Wed Dec  1 12:20:25 1999
Delivered-To: freebsd-current@freebsd.org
Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54])
	by hub.freebsd.org (Postfix) with ESMTP id 07999150CB
	for <freebsd-current@freebsd.org>; Wed,  1 Dec 1999 12:20:11 -0800 (PST)
	(envelope-from sgk@troutmask.apl.washington.edu)
Received: (from sgk@localhost)
	by troutmask.apl.washington.edu (8.9.3/8.9.3) id MAA06160
	for freebsd-current@freebsd.org; Wed, 1 Dec 1999 12:20:19 -0800 (PST)
	(envelope-from sgk)
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
Message-Id: <199912012020.MAA06160@troutmask.apl.washington.edu>
Subject: removing enigma(1)
To: freebsd-current@freebsd.org (FreeBSD Current)
Date: Wed, 1 Dec 1999 12:20:19 -0800 (PST)
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

[Donning asbestos underwear]

With the FreeBSD 4.0 code freeze fast approaching, are there any
compelling reasons to keep enigma (src/usr.bin/enigma) in the 
source tree?  Yes, I know it is a *small* utility, but
1. it provides rather weak encryption,
2. the crypto-distribution is available with stronger encryption, and
3. src/ports/security contains stronger encryption schemes.

-- 
Steve


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message