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, 2 insertions, 4 deletions

diff --git a/archivers/zip1/Makefile b/archivers/zip1/Makefile
index b14b53bf3f9..70272424fea 100644
--- a/archivers/zip1/Makefile
+++ b/archivers/zip1/Makefile
@@ -1,4 +1,4 @@
-# $NetBSD: Makefile,v 1.8 2000/08/18 22:46:29 hubertf Exp $
+# $NetBSD: Makefile,v 1.9 2000/09/09 19:40:17 fredb Exp $
 #
 
 DISTNAME=	zip1-1.1
@@ -28,9 +28,7 @@ BUILD_DEFS+=	ZIP_ENCRYPTION
 .if defined(ZIP_ENCRYPTION)
 DISTFILES+=	zcrypt10.zip
 ALL_TARGET+=	zipcloak
-RESTRICTED=	crypto
-NO_SRC_ON_FTP=	${RESTRICTED}
-NO_SRC_ON_CDROM=	${RESTRICTED}
+CRYPTO=		yes
 .endif
 
 do-install: