Github messages for voidlinux
 help / color / mirror / Atom feed
From: reedts <reedts@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] OpenVPN cannot connect with server using AES-256-CBC cipher
Date: Tue, 03 Nov 2020 10:32:42 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26100@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1071 bytes --]

New issue by reedts on void-packages repository

https://github.com/void-linux/void-packages/issues/26100

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System

* xuname:  
  *Void 5.8.18_1 x86_64 GenuineIntel uptodate hold rrrmDFFFFF*
* package:
  *openvpn-2.4.9_3*

### Expected behavior
OpenVPN should be able to connect to server using cipher AES-256-CBC
### Actual behavior
OpenVPN fails with error:
```
Tue Nov  3 10:21:38 2020 us=722261 Cipher algorithm 'aes-256-cbc' not found
Tue Nov  3 10:21:38 2020 us=722275 Cipher aes-256-cbc not supported
Tue Nov  3 10:21:38 2020 us=722282 Exiting due to fatal error
```

### Steps to reproduce the behavior
Use `cipher aes-256-cbc` in your `config.ovpn` and try to start `openvpn --config config.ovpn`

Full log of `openvpn --verb 4 --config /etc/openvpn/config.ovpn`:
[ovpn.txt](https://github.com/void-linux/void-packages/files/5480342/ovpn.txt)


             reply	other threads:[~2020-11-03  9:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-03  9:32 reedts [this message]
2020-11-06  3:36 ` cryptorick
2020-11-06  3:40 ` cryptorick
2022-04-23  2:07 ` github-actions
2022-05-08  2:11 ` [ISSUE] [CLOSED] " github-actions

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26100@inbox.vuxu.org \
    --to=reedts@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).