Bug 1802299 - openvpn cannot seem to load updated lzo
Summary: openvpn cannot seem to load updated lzo
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: openvpn
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: David Sommerseth
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1806566 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-12 20:29 UTC by Kevin Fenzi
Modified: 2020-03-26 21:55 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-26 21:55:50 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1807737 0 unspecified CLOSED lzo 2.10-1 violates ISO C alias rules 2023-09-14 05:53:28 UTC

Description Kevin Fenzi 2020-02-12 20:29:27 UTC
The lzo package was recently updated in rawhide from lzo-2.08-16.fc31 to lzo-2.10-1.fc32. 

After updating, my connections that use lzo fail with: 

Feb 10 10:21:17 taim.scrye.com nm-openvpn[8635]: Cannot initialize LZO compression library
Feb 10 10:21:17 taim.scrye.com nm-openvpn[8635]: Exiting due to fatal error

There's no so name bump, so I am unsure why it doesn't work.

Comment 1 David Sommerseth 2020-02-12 20:42:20 UTC
Sounds like openvpn needs to be rebuilt on Fedora Rawhide.  I suspect the lzo library should have done a so name bump but didn't.


Fedora Rawhide - openvpn-2.4.8-3: https://koji.fedoraproject.org/koji/taskinfo?taskID=41472040

Comment 2 Kevin Fenzi 2020-02-18 18:00:24 UTC
Alas, the rebuild does not help. ;( 

Perhaps it cannot deal with this new version of lzo?

It jumped from 2.08 to 2.10...

Comment 3 David Sommerseth 2020-02-18 20:47:38 UTC
Confirmed.  Just got a chance to test this on a F32 "pre-release" now.  Using --comp-lzo breaks it.

I've filed an upstream ticket related to this issue: https://community.openvpn.net/openvpn/ticket/1255

With that said, using compression is really not recommended.  I don't recall the complete compatibility matrix for --compress, but you might want to consider using '--compress stub' or '--compress stub-v2' instead of --comp-lzo.  This will have enable the "compression framing", but no data sent from the client will be compressed - and the server should normally catch that the client doesn't want compression and not do that.

Otherwise, there is also the openvpn3 package, currently available from my Copr repository ;-)
https://copr.fedorainfracloud.org/coprs/dsommers/openvpn3/
(the v8_beta is really stable now, we're on a good path moving out of beta releases)

Comment 4 Matt Fagnani 2020-02-25 00:34:53 UTC
I've seen the same error messages as Kevin when I used openvpn-2.4.8-2.fc32.x86_64 to connect to an openvpn server with comp-lzo in the configuration file and lzo-2.10-1.fc32.x86_64 installed. I installed lzop-1.04-3.fc32.x86_64. Running lzop with or without a input file and lzo-2.10-1 showed that lzo failed to start due to a library version conflict.

lzop
                          Lempel-Ziv-Oberhumer Packer
                           Copyright (C) 1996 - 2017
lzop v1.04         Markus Franz Xaver Johannes Oberhumer         Aug 10th 2017

lzo_init() failed - check your LZO installation !
library version conflict (2080, 20a0) - check your LZO installation !

Downgrading to lzo-2.08-16.fc31.x86_64 fixed the openvpn and lzop errors.

Comment 5 Beniamino Galvani 2020-02-26 21:01:29 UTC
*** Bug 1806566 has been marked as a duplicate of this bug. ***

Comment 6 Matt Fagnani 2020-03-02 03:40:07 UTC
Julian Sikorski found that building lzo with the gcc flag -fno-strict-aliasing fixed the problem of lzo-2.10-1 failing to start with lzop https://bugzilla.redhat.com/show_bug.cgi?id=1807737#c5 openvpn ran normally with the lzo-2.10-2 rpm I built after adding Julian's changes and comp-lzo in the openvpn configuration file. Applying Julian's patch to the lzo repo could fix this problem. Thanks.

Comment 7 David Sommerseth 2020-03-26 21:55:50 UTC
Based on further research, it looks like this is an lzo library issue more than an openvpn issue.  Since this is already tracked in bug #1807737, I'm closing this one.


Note You need to log in before you can comment on or make changes to this bug.