[Openswan dev] First pass README update

David McCullough david_mccullough at mcafee.com
Thu Oct 14 00:01:06 EDT 2010


Jivin D. Hugh Redelmeier lays it down ...
> | From: David McCullough <david_mccullough at mcafee.com>
> 
> | Jivin Harald Jenny lays it down ...
> | > On Wed, Oct 13, 2010 at 10:17:34AM +1000, David McCullough wrote:
> 
> | > *) SECURITY HOLES - None :-) sounds a bit to cocky to me - "Currently none
> | > know" maybe with a link to some site which holds a comprehensive list
> | > (http://openswan.org/support/vuln/ seems really outdated btw)?
> | 
> | Changed it to "Hopefully none :-)".
> 
> Please don't misuse "hopefully" this way.
> 
> The closest correct phrasing would be
> 	We hope there are none :-)
> or
> 	None, we hope!
> 
> While we're picking on this section, I would suggest slightly clearer
> GPG suggestion:
> 	Please use GPG (finger vuln at xelerance.com for GPG key) for this.
> =>
> 	Please encrypt your message with GPG using the public key shown by
> 	  "finger vuln at xelerance.com"

replaced all that with:

@@ -168,8 +179,10 @@ http://bugs.openswan.org
# SECURITY HOLES
#########################################################################
 
All security vulnerabilities found that require public disclosure will
receive proper CVE tracking numbers (see http://mitre.org/) and co-ordinated
via the vendor-sec mailing list. A complete list of known security
vulnerabilities is available at: http://www.openswan.org/security/ 


Cheers,
Davidm

-- 
David McCullough,      david_mccullough at mcafee.com,  Ph:+61 734352815
McAfee - SnapGear      http://www.mcafee.com         http://www.uCdot.org


More information about the Dev mailing list