entire CA from
scratch and re-issuing all keys?
Thanks
--
Stephen Ellwood,
Embedded System Engineer,
Ogden Safety Systems Ltd,
Unit 6, Cliffe Park Way,
Bruntcliffe Road,
Morley,
Leeds,
LS27 0RY,
UK.
Tel: +44 (0)1937 835395
Email: step...@ogdenradar.com
URL: www.ogdenradar.com
On Wed, Jul 24, 2019 at 7:20 AM Jan Just Keijser wrote:
> On 24/07/19 12:29, Jan Just Keijser wrote:
>
> The openssl library on RHEL/CentOS 7 is indeed FIPS compliant, but FIPS
> mode still needs to be explicitly enabled inside an application, usually
> using FIPS_mode_set().
> You can check whet
On Wed, Jul 24, 2019 at 7:20 AM Jan Just Keijser wrote:
> just tried this on a "plain" CentOS 7 box and I am not seeing any seg
> faults upon client-connect; this is with the EPEL version of OpenVPN 2.4.7.
>
> Correct, after running the following commands on the host where OpenVPN
was segfaulting
> Let me dive into this deeper, but this did not use to happen - I've used
> CentOS 6+7 icw OpenVPN for years , including client-connect scripts and
> have never seen coredumps like that.
> Are you using selinux? auditing? what is your policy on those?
>
I had SELinux disabled (permissive) and di
;s/ fips=1//' /etc/default/grub
While this does fix the problem, I would prefer to keep FIPS enabled
though. Is there a way to support FIPS?
[1] https://github.com/plus3it/spel
On Mon, Jul 22, 2019 at 2:17 PM Gert Doering wrote:
> Hi,
>
> On Mon, Jul 22, 2019 at 12:05:09PM -0400, Step
I have a CentOS 7 system in which I have installed OpenVPN 2.4.7. When a
Tunnelbrick client connects, the OpenVPN service Segmentation faults.
Thoughts on how I can troubleshoot? I also tried the EPEL version and 2.4.6
as well as disabled SELinux and see the same symptoms. Tried the commercial
vers
I have yet to find a configuration for this box that works.
Could someone please explain to me why these differences should occur and,
hopefully, explain how to make the remaining bits work.
Cheers annd thanks,
Stephen
--
========
