diff options
author | green <green@FreeBSD.org> | 1999-12-06 12:49:22 +0800 |
---|---|---|
committer | green <green@FreeBSD.org> | 1999-12-06 12:49:22 +0800 |
commit | 773b42136a4d992a6c1072a65c91bf2b5fcb8640 (patch) | |
tree | 737f2105eecdbbd3f68b885586710aba2e78424d /security/openssh | |
parent | dd11c53f4daa995014cb7748188da9c80b13d565 (diff) | |
download | freebsd-ports-gnome-773b42136a4d992a6c1072a65c91bf2b5fcb8640.tar.gz freebsd-ports-gnome-773b42136a4d992a6c1072a65c91bf2b5fcb8640.tar.zst freebsd-ports-gnome-773b42136a4d992a6c1072a65c91bf2b5fcb8640.zip |
Good-bye, RESTRICTED.
Reasons:
1. It's not crypto.
2. It links with crypto.
a. That crypto is in the public domain.
b. Linking with crypto does not constitute cryptography.
3. Even if it were crypto, the description of the entire protocol, etc.,
is in the public domain. The RFC is PD in the USA, and the white paper
in Europe.
4. Precedence? Even if it were crypto, the Bernstein case has set
precedence for allowing export of that. But it's not even crypto.
Diffstat (limited to 'security/openssh')
-rw-r--r-- | security/openssh/Makefile | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/security/openssh/Makefile b/security/openssh/Makefile index 914ad2c50097..0d965bf2e180 100644 --- a/security/openssh/Makefile +++ b/security/openssh/Makefile @@ -16,8 +16,6 @@ MAINTAINER= green@FreeBSD.org LIB_DEPENDS= crypto.1:${PORTSDIR}/security/openssl -RESTRICTED= "Links with cryptographic code." - .include <bsd.port.pre.mk> CAT?= /bin/cat DISTFILES!= ${CAT} ${FILESDIR}/distfiles |