From: Georgy Yakovlev <ya@sysdump.net>
To: gentoo-dev@lists.gentoo.org, gentoo-dev-announce@lists.gentoo.org
Subject: [gentoo-dev] Last-rites: =net-dns/dnscrypt-proxy-1.9.5-r1
Date: Tue, 13 Mar 2018 22:09:32 -0700 [thread overview]
Message-ID: <1521004172.61202.37.camel@sysdump.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 899 bytes --]
# Georgy Yakovlev <ya@sysdump.net> (13 Mar 2018)
# 1.x version is no longer maintained by upstream
# 2.x is in the tree and is better in almost every way
# Removal in 90 days. Bug #650464
=net-dns/dnscrypt-proxy-1.9.5-r1
I feel proper mask and last-rite is needed because 2.x is a complete
rewrite in another language, full re-implementation of the client.
Give users a bit more time to migrate to 2.x.
A fork of 1.x exists[1] on life support mode with no intentions of
adding new functionality and will be retired in a year anyway.
Also one of 1.x plugins is vulnerable [2].
I see no reason keeping old version in the tree anymore.
PR submitted: https://github.com/gentoo/gentoo/pull/7455
[1]https://github.com/dyne/dnscrypt-proxy/commit/45912417738ce38ce6dd04
cc4173d276a17ef2d8
[2]https://github.com/dyne/dnscrypt-proxy/issues/5
--
Georgy Yakovlev <ya@sysdump.net>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2018-03-14 5:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1521004172.61202.37.camel@sysdump.net \
--to=ya@sysdump.net \
--cc=gentoo-dev-announce@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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