Reorganize crypto handling, as discussed on tech-pkg. Remove all

RESTRICTED= variables that were predicated on former U.S. export
regulations. Add CRYPTO=, as necessary, so it's still possible to
exclude all crypto packages from a build by setting MKCRYPTO=no
(but "lintpkgsrc -R" will no longer catch them).

Specifically,

- - All packages which set USE_SSL just lose their RESTRICTED
    variable, since MKCRYPTO responds to USE_SSL directly.
- - realplayer7 and ns-flash keep their RESTRICTED, which is based
    on license terms, but also gain the CRYPTO variable.
- - srp-client is now marked broken, since the distfile is evidently
    no longer available. On this, we're no worse off than before.
    [We haven't been mirroring the distfile, or testing the build!]
- - isakmpd gets CRYPTO for RESTRICTED, but remains broken.
- - crack loses all restrictions, as it does not evidently empower
    a user to utilize strong encryption (working definition: ability
    to encode a message that requires a secret key plus big number
    arithmetic to decode).

1 files changed, 3 insertions, 7 deletions

diff --git a/security/gnupg/Makefile b/security/gnupg/Makefile
index f226abdd2f9..96264348292 100644
--- a/security/gnupg/Makefile
+++ b/security/gnupg/Makefile
@@ -1,4 +1,4 @@
-# $NetBSD: Makefile,v 1.13 2000/08/18 22:46:47 hubertf Exp $
+# $NetBSD: Makefile,v 1.14 2000/09/09 19:40:21 fredb Exp $
 # FreeBSD Id: Makefile,v 1.20 1997/08/27 13:06:01 ache Exp
 #
 
@@ -11,13 +11,9 @@ HOMEPAGE=	http://www.gnupg.org/
 
 DEPENDS+=	gettext>=0.10.35nb1:../../devel/gettext
 
-USE_GMAKE=	yes
-
+CRYPTO=		yes
 GNU_CONFIGURE=	yes
-
-RESTRICTED=	"Cryptographic software"
-NO_SRC_ON_FTP=	${RESTRICTED}
-MIRROR_DISTFILE=no
+USE_GMAKE=	yes
 
 .include "../../mk/bsd.prefs.mk"