Bug 169096
Summary: | Review Request: libmcrypt: Encryption algorithms library | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Tom "spot" Callaway <tcallawa> |
Component: | Package Review | Assignee: | Aurelien Bompard <gauret> |
Status: | CLOSED NEXTRELEASE | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | fedora-extras-list, gauret |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://mcrypt.sourceforge.net/ | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-09-28 17:05:16 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 163779, 169098 |
Description
Tom "spot" Callaway
2005-09-22 23:17:15 UTC
Wasn't there some kind of legal export restriction on mcrypt ? Has it been resolved ? (see Cryptology item in http://fedoraproject.org/wiki/ForbiddenItems) When I audited the algorithms, I couldn't find anything. The US cryptographic export restrictions were significantly reduced in 2000, perhaps at one point, this would be bad, but it is now ok. You also can't "export" a product that wasn't developed in the US. The auhtor of mcrypt is a Greek citizen. Review for release 1: * RPM name is OK * Source libmcrypt-2.5.7.tar.gz is the same as upstream * This is the latest version * Builds fine in mock * rpmlint of libmcrypt looks OK * rpmlint of libmcrypt-devel looks OK * File list of libmcrypt looks OK * File list of libmcrypt-devel looks OK * Works with mcrypt Is this an approval? Just making sure. Yes (I changed the blocker bug to FE-ACCEPT) |