[Pkg-utopia-maintainers] Bug#1024275: Bug#1024275: network-manager-openvpn: can't connect to vpn after last update: can't set proper cipher.

[Daniel Serpell]

Hi Michael,

I don't know what changed, but now I can set the cypher option back to
"default" and the connection works fine, so this means this bug was
fixed. Please, you can close this bug.

Thank you, and regards.

    Daniel.

On Tue, Nov 22, 2022 at 2:44 PM Michael Biebl <biebl at debian.org> wrote:
>
> Control: severity -1 normal
> Control: notforwarded -1
>
> Am 16.11.22 um 22:54 schrieb Daniel Serpell:
> > Package: network-manager-openvpn
> > Version: 1.10.2-1
> > Severity: normal
> >
> > Dear maintainer,
> >
> > After upgrading to 1.10.2-1, I can't connect to the VPN anymore.
> >
> > This is the logs from NetworkManager:
> >
> >    nm-openvpn[]: [<vpn name>] Peer Connection Initiated with [AF_INET]<IP>:<PORT>
> >    nm-openvpn[]: OPTIONS ERROR: failed to negotiate cipher with server.  Add the server's cipher ('AES-256-CBC') to --data-ciphers (currently 'AES-256-GCM') if you want to connect to this server.
> >    nm-openvpn[]: ERROR: Failed to apply push options
> >    nm-openvpn[]: Failed to open tun/tap interface
> >    nm-openvpn[]: SIGUSR1[soft,process-push-msg-failed] received, process restarting
> >
> > Trying to change the cipher to AES-256-CBC in network properties does not work, it reverts back to AES-256-GCM.
>
> I recreated the failing OpenVPN connection and I can't reproduce the
> problem anymore.
> I thus closed the upstream issue and dropped the forwarded meta data.
>
> My recommendation, if you can still reproduce the issue, is to file the
> issue upstream [1] yourself. It's likely that upstream has further question.
>
> Regards,
> Michael
> [1] https://gitlab.gnome.org/GNOME/NetworkManager-openvpn/
>