Github messages for voidlinux
 help / color / mirror / Atom feed
From: jt0in3e <jt0in3e@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] e2e's feature in the nextcloud client
Date: Thu, 01 Oct 2020 07:29:15 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25216@inbox.vuxu.org> (raw)

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

New issue by jt0in3e on void-packages repository

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

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.11_1 x86_64 GenuineIntel notuptodate rrFFFF*
* package:  
  *affected package(s) including the version*: ``nextcloud-client-3.0.1_1``

### Expected behavior
Norma installation without warnings.

### Actual behavior
After package installation there is a message 
> NextCloud client end-to-end encryption (e2e) is currently unavailable
(LibreSSL 2.9.2 does not provide EVP_PKEY_CTX_set_rsa_oaep_md primitive)


### Steps to reproduce the behavior
Install nextcloud-client

***

After installation there is the above warning regarding unsupportale e2e's feature in the nextcloud client. This install message were introduced on [August 29, 2019](https://github.com/void-linux/void-packages/commits/master/srcpkgs/nextcloud-client/INSTALL.msg). Since then it seems the EVP_PKEY_CTX_set_rsa_oaep_md primitive was implemented in Libressl (see [here #547](https://github.com/libressl-portable/portable/issues/547)).

Is it still relevant message? Could it be ignored? @yopito 

             reply	other threads:[~2020-10-01  5:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-01  5:29 jt0in3e [this message]
2020-10-01 17:32 ` yopito
2020-10-01 17:33 ` yopito
2020-10-01 17:34 ` yopito
2020-10-02 20:14 ` yopito
2020-10-24 13:40 ` yopito
2020-10-24 14:13 ` Johnnynator
2020-10-24 14:13 ` [ISSUE] [CLOSED] " Johnnynator

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-25216@inbox.vuxu.org \
    --to=jt0in3e@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).