From owner-freebsd-questions@FreeBSD.ORG Wed Jun 15 23:07:05 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 96EB216A424 for ; Wed, 15 Jun 2005 23:07:05 +0000 (GMT) (envelope-from tshadwick@goinet.com) Received: from mail.goinet.com (mail.goinet.com [208.207.72.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A79E43D1D for ; Wed, 15 Jun 2005 23:07:04 +0000 (GMT) (envelope-from tshadwick@goinet.com) Received: from mail.goinet.com (localhost.goinet.com [127.0.0.1]) by mail.goinet.com (8.13.1/8.13.1) with ESMTP id j5FN6tPx044334 for ; Wed, 15 Jun 2005 18:06:55 -0500 (CDT) (envelope-from tshadwick@goinet.com) Received: from localhost (tshadwick@localhost) by mail.goinet.com (8.13.1/8.13.1/Submit) with ESMTP id j5FN6sjN044331 for ; Wed, 15 Jun 2005 18:06:54 -0500 (CDT) (envelope-from tshadwick@goinet.com) X-Authentication-Warning: mail.goinet.com: tshadwick owned process doing -bs Date: Wed, 15 Jun 2005 18:06:54 -0500 (CDT) From: Tony Shadwick To: freebsd-questions@freebsd.org Message-ID: <20050615180436.Q30082@mail.goinet.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: ClamAV version 0.85.1, clamav-milter version 0.85 on mail.goinet.com X-Virus-Status: Clean Subject: GnuPG in the enterprise X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Jun 2005 23:07:05 -0000 Are there any good documents out there on managing GnuPG in the enterprise? There are basic issues I need to be able to address, such as a situation when an employee leaves a company. The admin needs to have the rights to revoke that user's public key, and be able decrypt any old messages to that user, and be able to decrypt messages sent to that user that are now being redirected to someone else for handling. Are there established mechanisms for handling centralized key management in a company to where the Administrator has access to everything required?