From owner-freebsd-security Sun May 2 18:33:56 1999 Delivered-To: freebsd-security@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id BBF9014C34 for ; Sun, 2 May 1999 18:33:53 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id DAA40084; Mon, 3 May 1999 03:33:38 +0200 (CEST) (envelope-from des) To: Gustavo V G C Rios Cc: security@FreeBSD.ORG Subject: Re: security advisories References: <372B8ACA.764E20FD@tdnet.com.br> From: Dag-Erling Smorgrav Date: 03 May 1999 03:33:37 +0200 In-Reply-To: Gustavo V G C Rios's message of "Sat, 01 May 1999 20:14:18 -0300" Message-ID: Lines: 15 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Gustavo V G C Rios writes: > The page http://www.freebsd.org/security/ has some advisories, but how > can i work with them? How to read the *.asc files? Which softwares > should i use to read them ? The .asc files are not human-readable - they're cryptographic signatures intended to authenticate the originator of each advisory. I believe they're PGP signatures - to verify them, I guess you would first add the relevant PGP keys to your keyring, then submit the advisory and the signature to PGP. The PGP keys used by the FreeBSD security officers are included in the FreeBSD handbook. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message