sync with OpenBSD -current

lib/libcrypto/man/RSA_check_key.3

@@ -1,4 +1,4 @@
-.\"	$OpenBSD: RSA_check_key.3,v 1.9 2023/05/01 07:28:11 tb Exp $
+.\"	$OpenBSD: RSA_check_key.3,v 1.10 2023/11/19 21:06:15 tb Exp $
 .\"	OpenSSL 6859cf74 Sep 25 13:33:28 2002 +0000
 .\"
 .\" This file was written by Ulf Moeller <ulf@openssl.org> and
@@ -49,7 +49,7 @@
 .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
 .\" OF THE POSSIBILITY OF SUCH DAMAGE.
 .\"
-.Dd $Mdocdate: May 1 2023 $
+.Dd $Mdocdate: November 19 2023 $
 .Dt RSA_CHECK_KEY 3
 .Os
 .Sh NAME
@@ -92,27 +92,6 @@ key structure must contain all the private key data too.
 Therefore, it cannot be used with any arbitrary
 .Vt RSA
 key object, even if it is otherwise fit for regular RSA operation.
-.Pp
-Unlike most other RSA functions, this function does
-.Sy not
-work transparently with any underlying
-.Vt ENGINE
-implementation because it uses the key data in the
-.Vt RSA
-structure directly.
-An
-.Vt ENGINE
-implementation can override the way key data is stored and handled,
-and can even provide support for HSM keys - in which case the
-.Vt RSA
-structure may contain
-.Sy no
-key data at all!
-If the
-.Vt ENGINE
-in question is only being used for acceleration or analysis purposes,
-then in all likelihood the RSA key data is complete and untouched,
-but this can't be assumed in the general case.
 .Sh RETURN VALUES
 .Fn RSA_check_key
 returns 1 if