Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 605460

Summary: app-crypt/easy-rsa is not compatible with libressl
Product: Gentoo Linux Reporter: Luca Barbato <lu_zero>
Component: Current packagesAssignee: Mikle Kolyada (RETIRED) <zlogene>
Status: RESOLVED FIXED    
Severity: normal    
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
URL: https://github.com/OpenVPN/easy-rsa/issues/76
Whiteboard:
Package list:
Runtime testing required: ---
Bug Depends on:    
Bug Blocks: 561854    
Attachments: openssl-1.0.cnf.patch

Description Luca Barbato gentoo-dev 2017-01-12 10:10:45 UTC
Upstream issue https://github.com/OpenVPN/easy-rsa/issues/76

Ideally they could generate on-the-fly the cnf file instead of using the environment.
Comment 1 fkater 2017-02-28 08:44:30 UTC
FYI: For people who cannot wait, here is a simple workaround that WFM:

Install easy-rsa as usual. Instead of creating the file vars from vars.example
and setting the variables there, edit openssl-xxx.cnf directly: Replace each
occurrence of $ENV::VARIABLE by $VARIABLE, thus removing ENV::, and set
VARIABLE=value at the beginning of this config file. Grab comments and default
values from vars.example.
Comment 2 Joerg Neikes 2017-12-12 17:02:42 UTC
Created attachment 509610 [details, diff]
openssl-1.0.cnf.patch

openssl-1.0.cnf.patch fixed settings for app-crypt/easy-rsa with liressl.
Comment 3 Joerg Neikes 2017-12-12 17:29:41 UTC
(In reply to Joerg Neikes from comment #2)
> Created attachment 509610 [details, diff] [details, diff]
> openssl-1.0.cnf.patch
> 
> openssl-1.0.cnf.patch fixed settings for app-crypt/easy-rsa with liressl.

change
+EASYRSA_PKI="$EASYRSA/pki"
with
+EASYRSA_PKI=${EASYRSA}"/pki"
Comment 4 Mikle Kolyada (RETIRED) archtester Gentoo Infrastructure gentoo-dev Security 2018-10-05 20:48:31 UTC
(In reply to Luca Barbato from comment #0)
> Upstream issue https://github.com/OpenVPN/easy-rsa/issues/76
> 
> Ideally they could generate on-the-fly the cnf file instead of using the
> environment.

3.0.5 (the latest in the tree) has the fix.