On 2016-11-26 13:38, Christian Hesse wrote: > Hello everybody, > > a new OpenVPN stable release is being prepared, namely version 2.4.0. > Currently we have 2.4_beta2. I think about making changes to our package that > require user intervention. > > We shipped a systemd unit file before OpenVPN upstream had one. Upstream now > has unit files, but two (for server and client) instead of just one. I did > backport some security features for our unit, but refused to migrate to the > upstream solution within the 2.3.x branch. > > That could change with 2.4.0. Instead of [email protected] we would have > [email protected] and [email protected]. Additionally the > 'daemon' option is no longer allowed with the upstream units. > > Any opinion about this change? Who can post news about this on the website? > > Stumbled about another fact... We define PLUGIN_LIBDIR, that allows to use > relative paths from that directory in configuration to call the plugins. This > path is '/usr/lib/openvpn' - plugins are installed to > '/usr/lib/openvpn/plugins', though. Any reason for that? >
I don't really use OpenVPN outside NetworkManager nowadays. Your proposed changes sound reasonable even without a news item (I guess post_upgrade message would be sufficient; let's raise our cups for correct usage of that). Bartłomiej
signature.asc
Description: OpenPGP digital signature
