BN_new: zap an anachronistic admonition

-This type should be considered opaque and fields should not be modified
-or accessed directly.

The type has long been opaque and reasonable people will not do things
that permit them to access the fields of opaque types directly. Of course,
in the vicinity of OpenSSL code and API all sorts of insanity actually exist.

1 files changed, 2 insertions, 4 deletions

diff --git a/src/lib/libcrypto/man/BN_new.3 b/src/lib/libcrypto/man/BN_new.3
index 088048c622..26a2a7d68a 100644
--- a/src/lib/libcrypto/man/BN_new.3
+++ b/src/lib/libcrypto/man/BN_new.3
@@ -1,4 +1,4 @@
-.\" $OpenBSD: BN_new.3,v 1.31 2023/07/26 20:08:59 tb Exp $
+.\" $OpenBSD: BN_new.3,v 1.32 2025/04/25 12:11:17 tb Exp $
 .\" full merge up to: OpenSSL man3/BN_new 2457c19d Mar 6 08:43:36 2004 +0000
 .\" selective merge up to: man3/BN_new 681acb31 Sep 29 13:10:34 2017 +0200
 .\" full merge up to: OpenSSL man7/bn 05ea606a May 20 20:52:46 2016 -0400
@@ -50,7 +50,7 @@
 .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
 .\" OF THE POSSIBILITY OF SUCH DAMAGE.
 .\"
-.Dd $Mdocdate: July 26 2023 $
+.Dd $Mdocdate: April 25 2025 $
 .Dt BN_NEW 3
 .Os
 .Sh NAME
@@ -91,8 +91,6 @@ memory allocation error has occurred.
 The basic object in this library is a
 .Vt BIGNUM .
 It is used to hold a single large integer.
-This type should be considered opaque and fields should not be modified
-or accessed directly.
 .Pp
 .Fn BN_new
 allocates and initializes a