From owner-freebsd-doc@FreeBSD.ORG Fri Dec 21 16:50:03 2007 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D85C616A418 for ; Fri, 21 Dec 2007 16:50:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id B5C0C13C448 for ; Fri, 21 Dec 2007 16:50:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id lBLGo3E4024065 for ; Fri, 21 Dec 2007 16:50:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id lBLGo3Fi024064; Fri, 21 Dec 2007 16:50:03 GMT (envelope-from gnats) Date: Fri, 21 Dec 2007 16:50:03 GMT Message-Id: <200712211650.lBLGo3Fi024064@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org From: "Simon L. Nielsen" Cc: Subject: Re: bin/118902: wrong signatures in d2i_RSAPublicKey man pages X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Simon L. Nielsen" List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Dec 2007 16:50:03 -0000 The following reply was made to PR docs/118902; it has been noted by GNATS. From: "Simon L. Nielsen" To: Pietro Cerutti Cc: FreeBSD gnats submit Subject: Re: bin/118902: wrong signatures in d2i_RSAPublicKey man pages Date: Fri, 21 Dec 2007 17:33:24 +0100 On 2007.12.20 21:30:34 +0100, Pietro Cerutti wrote: > the signatures for the following functions: > > d2i_RSAPublicKey > d2i_RSA_PUBKEY > d2i_RSAPrivateKey > d2i_Netscape_RSA > > are wrong in our man pages. [...] The manual pages are actually generated from the upstream POD documentation (openssl/doc/crypto/d2i_RSAPublicKey.pod) so the changes need to be made to the POD files. Otherwise they will simply vanish after next import. Any chance you could submit the changes directly to the OpenSSL project [1]? Then we would get the fixes when the next version of OpenSSL is imported. Does the source changes fix actual bugs or is it just style/warning? If they don't fix real bugs I would prefer for them also to go via OpenSSL to not divert from upstream more than needed. [1] http://www.openssl.org/support/rt.html -- Simon L. Nielsen