public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Marty E. Plummer" <hanetzer@startmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: mcrypt status (Re: [gentoo-dev] Idea for a new project: gentoo-libs)
Date: Sat, 4 Aug 2018 13:05:56 -0500	[thread overview]
Message-ID: <20180804180554.vdzinpcbqsh7s2ol@proprietary-killer> (raw)
In-Reply-To: <20180804114328.d4b31c885eba7cb98a1b5fd2@gentoo.org>

On Sat, Aug 04, 2018 at 11:43:28AM +0300, Andrew Savchenko wrote:
> On Mon, 25 Jun 2018 07:59:47 +0200 Hanno Böck wrote:
> > On Fri, 22 Jun 2018 21:50:50 -0500
> > "Marty E. Plummer" <hanetzer@startmail.com> wrote:
> > 
> > > So, as you may be aware I've been doing some work on moving bzip2 to
> > > an autotools based build. Recently I've ran into app-crypt/mhash,
> > > which is in a semi-abandoned state (talking with the maintainer on
> > > twitter atm), and I was thinking it may be a good idea to set up a
> > > project for keeping these semi-abandoned and really-abandoned
> > > libraries and projects up to date and such.
> > 
> > This is a common problem, however if you want to make this reasonable
> > you wouldn't make it a gentoo thing, but a cross-distro effort. The
> > idea has been tossed around a lot, but noone yet started implementing
> > it.
> > 
> > However keeping things alive may not always be the right option.
> > There's a reason mcrypt is abandoned. It's an ancient crypto library,
> > crypto is moving forward, there are better options.
> 
> Do you have any evidence that mcrypt should not be used?
> 
> Symmetric cryptography is quite conservative and it took years and
> even decades for algorithms and their implementations to become
> trusted, so there is nothing wrong in using good old verified
> software.
> 
> Actually for local symmetric encryption this is the best tool I
> know.
> 
> Best regards,
> Andrew Savchenko
It seems that every last person commenting on this is talking mcrypt,
not mhash, which is what I mentioned in the first place. As far as I can
tell, these are entirely differnt projects which just happen to have a
similar name.



  parent reply	other threads:[~2018-08-04 18:07 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-23  2:50 [gentoo-dev] Idea for a new project: gentoo-libs Marty E. Plummer
2018-06-23  2:57 ` Marty E. Plummer
2018-06-23 13:05   ` Jonas Stein
2018-08-05 16:55     ` Richard Yao
2018-06-23  7:22 ` Michał Górny
2018-06-23  7:30   ` Marty E. Plummer
2018-06-23  7:37     ` Michał Górny
2018-06-23 10:59     ` Alec Warner
2018-08-05 16:45       ` Richard Yao
2018-08-05 17:01         ` Alec Warner
2018-08-05 17:16           ` M. J. Everitt
2018-08-05 17:24           ` Rich Freeman
2018-08-05 17:31             ` M. J. Everitt
2018-08-05 18:12             ` Richard Yao
2018-08-05 18:35               ` Rich Freeman
2018-08-05 20:49                 ` Richard Yao
2018-08-05 18:06           ` Richard Yao
2018-06-23  7:43 ` Mikle Kolyada
2018-06-23  8:15   ` Paweł Hajdan, Jr.
2018-06-23  8:55     ` Marty E. Plummer
2018-06-23 11:06       ` Roy Bamford
2018-06-23 23:52 ` Kent Fredric
2018-06-25  5:59 ` Hanno Böck
2018-06-27  0:03   ` Marty E. Plummer
2018-08-04  8:43   ` mcrypt status (Re: [gentoo-dev] Idea for a new project: gentoo-libs) Andrew Savchenko
2018-08-04  9:51     ` [gentoo-dev] Re: mcrypt status Martin Vaeth
2018-08-04 10:22       ` Andrew Savchenko
2018-08-04 14:29     ` mcrypt status (Re: [gentoo-dev] Idea for a new project: gentoo-libs) Hanno Böck
2018-08-04 15:25       ` Thomas Deutschmann
2018-08-05  4:57       ` Andrew Savchenko
2018-08-04 18:05     ` Marty E. Plummer [this message]
2018-08-04 19:22       ` Andrew Savchenko

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=20180804180554.vdzinpcbqsh7s2ol@proprietary-killer \
    --to=hanetzer@startmail.com \
    --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