Thanks for clarification. I had that wrong idea about that beecrypt is completed :( I saw that latest commits adds libgcrypt support to RPM. Do you think that switching to libgcrypt may give us some benefits ?
wt., 24 wrz 2019 o 23:34 Neal Gompa <[email protected]> napisał(a): > On Tue, Sep 24, 2019 at 5:27 PM Tomasz Gajc <[email protected]> wrote: > > > > Hi, > > > > why our RPM uses external crypto engine which is set to OpenSSL ? > > Isn't this a overkill ? > > > https://github.com/OpenMandrivaAssociation/rpm/blob/e8e84444006f608eee038c4acb7484943f50e439/rpm.spec#L555 > > > > I'd like to suggest ti use RPM's internal beecrypt as a crypto engine. > WDYT ? > > No. BeeCrypt is completely unmaintained these days. And RPM does not > bundle beecrypt either. You still need to ship the library. > > We use OpenSSL because it's currently the fastest and best maintained > crypto backend. I explicitly picked it because of that. In the future, > we may switch to the newer gcrypt backend, but for now, we're using > OpenSSL. > > NSS is a ridiculous pain to deal with these days with constant ABI/API > breaks, so it's not a reasonable option for RPM. > > > -- > 真実はいつも一つ！/ Always, there's only one truth! > -- > Cooker mailing-list > https://www.openmandriva.org/lists > > >
