Re: ITP: pptpd
> Is it okay to go into the primary distribution, or would it be forced
> into nonus? If it's okay for ftp.debian.org, I can sponsor it for you.
I am not sure about this. pptpd itself should be ok in main, but the
modified ppp and kernel packages (these are needed for the data
encryption) contain RC4, MD4, MD5 and SHA codes with a key length of up
to 128 bit. Please excuse my total ignorance of the algorithms at this
point. I only know from the source codes that these algorithms are used
and that MPPE (Microsoft Point-to-Point Encryption) is used with up to
128 bit encryption.
Another problem is that the Microsoft-crypto patches for pppd and the
kernel ppp implementation contain code with this license:
/* crypto/sha/sha.h */
/* Copyright (C) 1995-1997 Eric Young (email@example.com)
* All rights reserved.
* This package is an SSL implementation written
* by Eric Young (firstname.lastname@example.org).
* The implementation was written so as to conform with Netscapes SSL.
* Added Microsoft's Get_Key() per mppe draft by mag
* This library is free for commercial and non-commercial use as long as
* the following conditions are aheared to. The following conditions
* apply to all code found in this distribution, be it the RC4, RSA,
* lhash, DES, etc., code; not just the SSL code. The SSL documentation
* included with this distribution is covered by the same copyright
* except that the holder is Tim Hudson (email@example.com).
* Copyright remains Eric Young's, and as such any Copyright notices in
* the code are not to be removed.
* If this package is used in a product, Eric Young should be given
* as the author of the parts of the library used.
* This can be in the form of a textual message at program startup or
* in documentation (online or textual) provided with the package.
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
* 1. Redistributions of source code must retain the copyright
* notice, this list of conditions and the following disclaimer.
* 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in
* documentation and/or other materials provided with the
* 3. All advertising materials mentioning features or use of this
* must display the following acknowledgement:
* "This product includes cryptographic software written by
* Eric Young (firstname.lastname@example.org)"
* The word 'cryptographic' can be left out if the rouines from the
* being used are not cryptographic related :-).
* 4. If you include any Windows specific code (or a derivative thereof)
* the apps directory (application code) you must include an
* "This product includes software written by Tim Hudson
* THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND
* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
* ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE
* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY
* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY
* SUCH DAMAGE.
* The licence and distribution terms for any publically available
* derivative of this code cannot be changed. i.e. this code cannot
* copied and put under another distribution licence
* [including the GNU Public Licence.]
I think it will have to go into non-free, but I am not sure about
non-US. I am CC-ing this to debian-devel in th hope that somebody can
answer if the codes have to go into non-US.