-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07/02/2014 11:22 AM, Stephen Gallagher wrote:
On 07/02/2014 11:19 AM, Kalev Lember wrote:
> On 07/02/2014 05:13 PM, Stephen Gallagher wrote:
>> This is not an official solution, but I am now providing a
>> COPR for Rawhide installs that provides a compatibility library
>> for libgcrypt.
> That's awesome, but can we get this in rawhide proper instead?
> I'd be happy to help get this through the review process if you
> need a reviewer.
Short answer: no. I don't have the time or inclination to attempt
to maintain a compat *crypto* library. There's far too much
possibility for disaster there.
To clarify: in my COPR, it's use-at-your-own-risk. If we moved it to
Rawhide, I'm on the hook to make sure it's constantly kept up-to-date
and keep track of vulnerabilities. I'm not prepared to take that level
of ownership on. I only built this COPR because I was updating to
Rawhide today and this bit me. I'm being nice and sharing it, with the
expectation that it's really only meant for this singular use-case,
which should be obsoleted as soon as Google moves to the newer
libgcrypt (or bundles their own, whatever).
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird -
http://www.enigmail.net/
iEYEARECAAYFAlO0JDcACgkQeiVVYja6o6NLSgCfQVvwmyK+szYOCSq8O35H/wtx
1J4An0VYxt3tSGteebrzwOWQMwy434GH
=jSLy
-----END PGP SIGNATURE-----