From owner-freebsd-doc@FreeBSD.ORG Thu Feb 27 17:44:39 2014 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E1F2DA34 for ; Thu, 27 Feb 2014 17:44:38 +0000 (UTC) Received: from mail.f5.com (mail.f5.com [208.85.209.139]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A81001198 for ; Thu, 27 Feb 2014 17:44:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=f5.com; i=@f5.com; q=dns/txt; s=seattle; t=1393523079; x=1425059079; h=date:from:to:cc:message-id:in-reply-to:references: subject:mime-version; bh=o95Rc9c8XFPAnQj0moBxtC55wZfU6frZMd0wDXakE0w=; b=sCrc0lU0aJAr91386lFJrjH1z2ip5gyzy8mdoY+C9AgI+DKcjHzNTnzS vvaHN/rwrECDr/g0FYEMuN2y/Ja6PXyniVzrOBP3ogiUre3+PQo7lH3PG +SZjr/Qd41neu7nBrY8dlMl4qx/kNF4PsDEa5jiVtcBj016EnrxPFeAXT E=; X-IronPort-AV: E=Sophos;i="4.97,556,1389744000"; d="scan'208,217";a="101593378" X-IPAS-Result: AmsWABd4D1PAqArr/2dsb2JhbABagkKBVoMDiFO1NYExdIIlAQEBAQIBAQIgVgULCw01AgIoLwYBDQWHcaoQoHYXjlUHgm6BSQSJSoYChhaCVoZyjwWCCg Received: from unknown (HELO exchmail.f5net.com) ([192.168.10.235]) by mail.f5.com with ESMTP/TLS/AES128-SHA; 27 Feb 2014 17:44:24 +0000 Received: from shiny.int.lineratesystems.com (192.168.16.250) by exchmail.f5net.com (192.168.16.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 27 Feb 2014 09:44:23 -0800 Date: Thu, 27 Feb 2014 10:44:21 -0700 From: Joe To: , Lowell Gilbert Message-ID: In-Reply-To: <444n3kvhsy.fsf@lowell-desk.lan> References: <44fvn64qaf.fsf@lowell-desk.lan> <444n3kvhsy.fsf@lowell-desk.lan> Subject: Re: how to read security advisories X-Mailer: Airmail (231) MIME-Version: 1.0 X-Originating-IP: [192.168.16.250] Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: freebsd-doc@freebsd.org X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Feb 2014 17:44:39 -0000 =46or the patch level field, it would be informative to have a note indic= ating that the absence of a patch level field is itself information, rath= er than just an indication that the user is looking in the wrong place. =C2= =A0I think that's really the critical bit that I was missing. =46or example: ... 4.3-RELEASE-p39 (7) ... (7) The=C2=A0Corrected=C2=A0field indicates the date, time, time offset, = and release that was corrected. =C2=A0The -p suffix indicates a security = branch patch level. =C2=A0Builds which do not have the -p suffix in their= release string do not have a patch level. ... I think it would also be nice to have a link to a page describing the bra= nching and/or build-naming strategy, but the above would've been plenty t= o have pointed me in the right direction. Thanks, -joe On =46ebruary 27, 2014 at 5:52:54 AM, Lowell Gilbert (freebsd-lists=40be-= well.ilk.org) wrote: Joe writes: =20 > I'd like to point out that neither of these resources are of much help = =20 > for someone trying to figure out what the -p means, though. =20 That makes sense. What would you suggest as additional text for the =20 how-to-read-a-security-advisory chapter=3F =20