From: eli-schwartz <eli-schwartz@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: lurch / libomemo: 12-byte IVs patch
Date: Mon, 30 Nov 2020 05:25:12 +0100 [thread overview]
Message-ID: <20201130042512.DHyvwGA7nZT2_rw4-5kPBuS7VIHL_q2PGU2r9TNV21I@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26757@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1048 bytes --]
New comment by eli-schwartz on void-packages repository
https://github.com/void-linux/void-packages/issues/26757#issuecomment-735536652
Comment:
Note this is based on https://github.com/xsf/xeps/pull/894 which got NACKed by the author and closed without merging.
@Neustradamus has proceeded to trick various people into applying this specific patch, including at https://bugs.archlinux.org/task/68766 by claiming it's a critical security vulnerability (the severity got corrected prior to the bug being rejected), and the actual discussion in https://github.com/gkdr/libomemo/issues/24 seems to consist of more or less everyone being mad at @Neustradamus for circumventing actual development processes and pushing, randomly and inconsistently, at select distributors to use downstream patches that are under dispute.
I recommend reverting it and seeking upstream guidance. e.g.
https://github.com/gkdr/libomemo/issues/24#issuecomment-735408224
> please stop pushing downstream changes, it makes the whole situation even more confusing.
next parent reply other threads:[~2020-11-30 4:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26757@inbox.vuxu.org>
2020-11-30 4:25 ` eli-schwartz [this message]
2020-11-30 4:31 ` ericonr
2020-11-30 7:32 ` Neustradamus
2020-11-30 12:26 ` ericonr
2020-11-30 12:30 ` leahneukirchen
2020-11-30 12:42 ` ericonr
2020-11-30 14:11 ` Neustradamus
2020-11-30 14:22 ` q66
2020-11-30 14:30 ` leahneukirchen
2020-11-30 14:36 ` ericonr
2020-11-30 14:49 ` Neustradamus
2021-01-14 1:29 ` Neustradamus
2021-01-14 1:44 ` the-maldridge
2021-01-14 1:46 ` Neustradamus
2021-01-14 1:51 ` Neustradamus
2021-01-14 1:52 ` the-maldridge
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=20201130042512.DHyvwGA7nZT2_rw4-5kPBuS7VIHL_q2PGU2r9TNV21I@z \
--to=eli-schwartz@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).