From: Dave Young <dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Baoquan He <bhe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [Patch] 01fips/module-setup.sh: add libssl.so.10 to make kdump work with fips mode
Date: Fri, 10 May 2013 11:24:41 +0800 [thread overview]
Message-ID: <518C6879.5070204@redhat.com> (raw)
In-Reply-To: <bccc4bdfbdbdb14122cf83819a7ba16334348acc.1368088634.git.bhe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
On 05/09/2013 04:38 PM, Baoquan He wrote:
> FIPS can work well in 1st kernel, but failed in kdump kernel. the
> libssl.so.10 and related hmac file are needed. Now add it and it
> works.
This patch looks good to me.
Explain a bit about why do we need this extra libssl.so.10:
libcrypto.so dlopens libssl.so.10 only in FIPS mode, so ldd does now
show the dependency automaticlly.
>
> Signed-off-by: Baoquan He <bhe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> ---
> modules.d/01fips/module-setup.sh | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/modules.d/01fips/module-setup.sh b/modules.d/01fips/module-setup.sh
> index a7f5be8..6013318 100755
> --- a/modules.d/01fips/module-setup.sh
> +++ b/modules.d/01fips/module-setup.sh
> @@ -38,7 +38,7 @@ install() {
>
> inst_libdir_file libsoftokn3.so libsoftokn3.so \
> libsoftokn3.chk libfreebl3.so libfreebl3.chk \
> - libssl.so 'hmaccalc/sha512hmac.hmac'
> + libssl.so 'hmaccalc/sha512hmac.hmac' libssl.so.10
>
> dracut_install -o prelink
> }
>
--
Thanks
Dave
prev parent reply other threads:[~2013-05-10 3:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 8:38 [Patch] 01fips/module-setup.sh: add libssl.so.10 to make kdump work with fips mode Baoquan He
[not found] ` <bccc4bdfbdbdb14122cf83819a7ba16334348acc.1368088634.git.bhe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-05-10 3:24 ` Dave Young [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=518C6879.5070204@redhat.com \
--to=dyoung-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=bhe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.