[src/trunk]: src/share/man/man8 Refer to the generic ssp(3) instead of the sp...

[jruoho <jruoho%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/ba90cccb6217
branches:  trunk
changeset: 754123:ba90cccb6217
user:      jruoho <jruoho%NetBSD.org@localhost>
date:      Wed Apr 21 05:49:36 2010 +0000

description:
Refer to the generic ssp(3) instead of the specific __builtin_object_size(3).

diffstat:

 share/man/man8/security.8 |  8 +++++---
 1 files changed, 5 insertions(+), 3 deletions(-)

diffs (25 lines):

diff -r e9994b662441 -r ba90cccb6217 share/man/man8/security.8
--- a/share/man/man8/security.8 Wed Apr 21 05:40:59 2010 +0000
+++ b/share/man/man8/security.8 Wed Apr 21 05:49:36 2010 +0000
@@ -1,4 +1,4 @@
-.\" $NetBSD: security.8,v 1.23 2010/04/21 05:40:59 jruoho Exp $
+.\" $NetBSD: security.8,v 1.24 2010/04/21 05:49:36 jruoho Exp $
 .\"
 .\" Copyright (c) 2006 Elad Efrat <elad%NetBSD.org@localhost>
 .\" All rights reserved.
@@ -308,11 +308,13 @@
 .Nx .
 .Pp
 The underlying idea builds on the observation that there are cases where
-the compiler knows the size of a buffer (cf.
-.Xr __builtin_object_size 3 ) .
+the compiler knows the size of a buffer.
 If a buffer overflow is suspected in a function that does little or no
 bounds checking, either a compile time warning can be issued or a
 safer substitute function can be used at runtime.
+Refer to
+.Xr ssp 3
+for additional details.
 .Pp
 The
 .Em FORTIY_SOURCE