From: Randy Dunlap <rdunlap@infradead.org>
To: David Howells <dhowells@redhat.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-crypto@vger.kernel.org
Subject: Re: linux-next: Tree for Oct 31 (crypto, rsa, mpi)
Date: Fri, 01 Nov 2013 11:21:54 -0700 [thread overview]
Message-ID: <5273F142.3090608@infradead.org> (raw)
In-Reply-To: <5808.1383318971@warthog.procyon.org.uk>
On 11/01/13 08:16, David Howells wrote:
> Randy Dunlap <rdunlap@infradead.org> wrote:
>
>> crypto/built-in.o: In function `RSA_verify_signature':
>> rsa.c:(.text+0x1d347): undefined reference to `mpi_get_nbits'
>> rsa.c:(.text+0x1d354): undefined reference to `mpi_get_nbits'
>> ...
>
> Does the attached patch fix it for you?
Yes, thanks.
Acked-by: Randy Dunlap <rdunlap@infradead.org>
>
> David
> ---
> KEYS: The RSA public key algorithm needs to select MPILIB
>
> The RSA public key algorithm needs to select MPILIB directly in Kconfig as the
> 'select' directive is not recursive and is thus MPILIB is not enabled by
> selecting MPILIB_EXTRA.
>
> Without this, the following errors can occur:
>
> crypto/built-in.o: In function `RSA_verify_signature':
> rsa.c:(.text+0x1d347): undefined reference to `mpi_get_nbits'
> rsa.c:(.text+0x1d354): undefined reference to `mpi_get_nbits'
> rsa.c:(.text+0x1d36e): undefined reference to `mpi_cmp_ui'
> rsa.c:(.text+0x1d382): undefined reference to `mpi_cmp'
> rsa.c:(.text+0x1d391): undefined reference to `mpi_alloc'
> rsa.c:(.text+0x1d3b0): undefined reference to `mpi_powm'
> rsa.c:(.text+0x1d3c3): undefined reference to `mpi_free'
> rsa.c:(.text+0x1d3d8): undefined reference to `mpi_get_buffer'
> rsa.c:(.text+0x1d4d4): undefined reference to `mpi_free'
> rsa.c:(.text+0x1d503): undefined reference to `mpi_get_nbits'
>
> Reported-by: Randy Dunlap <rdunlap@infradead.org>
> Signed-off-by: David Howells <dhowells@redhat.com>
> ---
> diff --git a/crypto/asymmetric_keys/Kconfig b/crypto/asymmetric_keys/Kconfig
> index 82e7d6b0c276..03a6eb95ab50 100644
> --- a/crypto/asymmetric_keys/Kconfig
> +++ b/crypto/asymmetric_keys/Kconfig
> @@ -23,6 +23,7 @@ config ASYMMETRIC_PUBLIC_KEY_SUBTYPE
> config PUBLIC_KEY_ALGO_RSA
> tristate "RSA public-key algorithm"
> select MPILIB_EXTRA
> + select MPILIB
> help
> This option enables support for the RSA algorithm (PKCS#1, RFC3447).
>
>
--
~Randy
prev parent reply other threads:[~2013-11-01 18:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20131031210027.cb3604b9589e0b7a1599dbd2@canb.auug.org.au>
2013-10-31 21:02 ` linux-next: Tree for Oct 31 (crypto, rsa, mpi) Randy Dunlap
2013-11-01 15:16 ` David Howells
2013-11-01 18:21 ` Randy Dunlap [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5273F142.3090608@infradead.org \
--to=rdunlap@infradead.org \
--cc=dhowells@redhat.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).