From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH bluetooth-next 2/4] openssl: allow to install openssl.cnf
Date: Mon, 12 Jan 2015 15:36:08 +0100 [thread overview]
Message-ID: <20150112143608.GA26436@pengutronix.de> (raw)
In-Reply-To: <1419701935-28132-3-git-send-email-alex.aring@gmail.com>
On Sat, Dec 27, 2014 at 06:38:53PM +0100, Alexander Aring wrote:
> For doing some certificates magic the openssl tool requires some
> openssl.cnf files. This patch adds an option to install the default one.
>
> Signed-off-by: Alexander Aring <alex.aring@gmail.com>
> ---
> rules/openssl.in | 5 +++++
> rules/openssl.make | 6 ++++++
> 2 files changed, 11 insertions(+)
>
> diff --git a/rules/openssl.in b/rules/openssl.in
> index 096b398..d1c085d 100644
> --- a/rules/openssl.in
> +++ b/rules/openssl.in
> @@ -28,4 +28,9 @@ config OPENSSL_BIN
> help
> Whether to build and install OpenSSL binary.
>
> +config OPENSSL_CNF
> + bool "install openssl.cnf"
> + help
> + Install openssl.cnf config file.
> +
> endif
> diff --git a/rules/openssl.make b/rules/openssl.make
> index 56cd6b7..ec32fe5 100644
> --- a/rules/openssl.make
> +++ b/rules/openssl.make
> @@ -100,6 +100,12 @@ ifdef PTXCONF_OPENSSL_BIN
> @$(call install_copy, openssl, 0, 0, 0755, -, \
> /usr/bin/openssl)
> endif
> +
> +ifdef PTXCONF_OPENSSL_CNF
> + @$(call install_copy, openssl, 0, 0, 0644, -, \
> + /usr/lib/ssl/openssl.cnf)
> +endif
I think we should always install this, unless there is a good reason to
make this optional?
Michael
> +
> @$(call install_lib, openssl, 0, 0, 0644, libssl)
> @$(call install_lib, openssl, 0, 0, 0644, libcrypto)
>
> --
> 2.2.0
>
>
> --
> ptxdist mailing list
> ptxdist@pengutronix.de
>
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2015-01-12 14:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-27 17:38 [ptxdist] [PATCH bluetooth-next 0/4] openvpn: cleanups, extras and version bumps Alexander Aring
2014-12-27 17:38 ` [ptxdist] [PATCH bluetooth-next 1/4] liblzo: rework and version bump Alexander Aring
2014-12-27 17:38 ` [ptxdist] [PATCH bluetooth-next 2/4] openssl: allow to install openssl.cnf Alexander Aring
2015-01-12 14:36 ` Michael Olbrich [this message]
2015-01-18 18:43 ` Alexander Aring
2014-12-27 17:38 ` [ptxdist] [PATCH bluetooth-next 3/4] easy-rsa: initial commit Alexander Aring
2014-12-27 17:38 ` [ptxdist] [PATCH bluetooth-next 4/4] openvpn: rework and version bump Alexander Aring
2015-01-12 14:38 ` Michael Olbrich
2015-01-18 19:12 ` Alexander Aring
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=20150112143608.GA26436@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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