Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 28 Feb 2003 15:26:44 +0200
From:      Peter Pentchev <roam@ringlet.net>
To:        Kris Kennaway <kris@obsecurity.org>
Cc:        Matthias Andree <ma@dt.e-technik.uni-dortmund.de>, freebsd-ports@FreeBSD.ORG
Subject:   Re: General: crypto in ports vs. RESTRICTED=... in Makefile
Message-ID:  <20030228132644.GA907@straylight.oblivion.bg>
In-Reply-To: <20030217214540.GD71679@rot13.obsecurity.org>
References:  <m3znovdu3f.fsf@merlin.emma.line.org> <20030217214540.GD71679@rot13.obsecurity.org>

next in thread | previous in thread | raw e-mail | index | archive | help

--dDRMvlgZJXvWKvBx
Content-Type: text/plain; charset=windows-1251
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Feb 17, 2003 at 01:45:40PM -0800, Kris Kennaway wrote:
> On Mon, Feb 17, 2003 at 12:28:36PM +0100, Matthias Andree wrote:
> > Hi,
> >=20
> > I recently added a "RESTRICTED" tag to ports/databases/db41 and added a
> > db41-nocrypto port that uses the "nocrypto" version of DB 4.1.25.1.
> >=20
> > Christian "naddy" Weisgerber asked whether this was right, I replied
> > that I took that procedure from the Porter's Handbook (that says crypto
> > code is to be tagged RESTRICTED), and Christian suggested that I take
> > this up on ports then.
> >=20
> > So here we stand...
> >=20
> > What's the consensus on tagging ports that contain cryptographic code
> > with "RESTRICTED"? Is this necessary, as documented in the Porter's
> > handbook, or is this obsolete or incorrect (and if so, why, and where
> > documented)? Is the port split into crypto and non-crypto correct?
>=20
> See my reply on cvs-all.
>=20
> The handbook is out of date.

Would the attached patch be in order, then?

G'luck,
Peter

--=20
Peter Pentchev	roam@ringlet.net    roam@sbnd.net    roam@FreeBSD.org
PGP key:	http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint	FDBA FD79 C26F 3C51 C95E  DF9E ED18 B68D 1619 4553
I am the thought you are now thinking.

Index: doc/en_US.ISO8859-1/books/porters-handbook/book.sgml
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/porters-handbook/book.sgml,v
retrieving revision 1.286
diff -u -r1.286 book.sgml
--- doc/en_US.ISO8859-1/books/porters-handbook/book.sgml	27 Feb 2003 15:39:=
58 -0000	1.286
+++ doc/en_US.ISO8859-1/books/porters-handbook/book.sgml	28 Feb 2003 13:10:=
43 -0000
@@ -3177,18 +3177,8 @@
 	  FTP.</para>
=20
 	<para>Also set this if the application's license has general
-	  restrictions on who may use it.  Examples include:</para>
-
-	<itemizedlist>
-	  <listitem>
-	    <para>The application is for non-commercial use only.</para>
-	  </listitem>
-
-	  <listitem>
-	    <para>The application contains cryptography code which is
-	      forbidden in some countries.</para>
-	  </listitem>
-	</itemizedlist>
+	  restrictions on who may use it, e.g. the application is for
+	  non-commercial use only.</para>
       </sect2>
=20
       <sect2>

--dDRMvlgZJXvWKvBx
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (FreeBSD)

iD8DBQE+X2OU7Ri2jRYZRVMRAvjZAJ0V4i1ChGMZdSzgHvmQlXneFNEpewCgu36U
0wZwQ2EihwMLXvVcfvJySC8=
=ljpR
-----END PGP SIGNATURE-----

--dDRMvlgZJXvWKvBx--

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030228132644.GA907>