> >> How about if we create a uci default script and check on the running
> >> system what is installed?
> >> And then we could generate a file and add or remove an include line
> >> form
> >> the openssl.cnf [1]?
> >
> > I think we can manage something like that. The .include option can
> > load
Hello Eneas
How about if we create a uci default script and check on the running
system what is installed?
And then we could generate a file and add or remove an include line
form
the openssl.cnf [1]?
Hi Florian, Daniel
I think we can manage something like that. The .include option can
On Fri, Apr 23, 2021 at 3:11 AM Florian Eckert wrote:
> How about if we create a uci default script and check on the running
> system what is installed?
> And then we could generate a file and add or remove an include line form
> the openssl.cnf [1]?
Hi Florian, Daniel
I think we can manage
Hello Daniel,
Hello Eneas,
On 2021-04-23 01:36, Eneas U de Queiroz wrote:
On Thu, Apr 22, 2021 at 3:55 AM Daniel Danzberger
wrote:
Automatically enable an engine in the openssl.cnf if it has been
build.
Before this change, /etc/openssl.cnf had to be edited manually on the
system to enable
On Thu, Apr 22, 2021 at 3:55 AM Daniel Danzberger wrote:
>
> Automatically enable an engine in the openssl.cnf if it has been build.
> Before this change, /etc/openssl.cnf had to be edited manually on the
> system to enable the engine.
>
> +define Package/libopenssl-conf/enable
> + $(if
Automatically enable an engine in the openssl.cnf if it has been build.
Before this change, /etc/openssl.cnf had to be edited manually on the
system to enable the engine.
Signed-off-by: Daniel Danzberger
---
package/libs/openssl/Makefile | 7 +++
1 file changed, 7 insertions(+)
diff --git
