shishi-commit
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

shishi-debian copyright


From: Simon Josefsson
Subject: shishi-debian copyright
Date: Wed, 03 Apr 2013 17:47:57 +0000

CVSROOT:        /sources/shishi
Module name:    shishi-debian
Changes by:     Simon Josefsson <jas>   13/04/03 17:47:57

Modified files:
        .              : copyright 

Log message:
        Update copyright file.

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/shishi-debian/copyright?cvsroot=shishi&r1=1.27&r2=1.28

Patches:
Index: copyright
===================================================================
RCS file: /sources/shishi/shishi-debian/copyright,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -b -r1.27 -r1.28
--- copyright   3 Apr 2013 17:40:47 -0000       1.27
+++ copyright   3 Apr 2013 17:47:57 -0000       1.28
@@ -74,25 +74,40 @@
 License: GPL-3+
 
 Files: lib/kerberos.asn1
-Copyright: Copyright (C) 2002-2012 Simon Josefsson
+Copyright: Copyright (C) 2002-2013 Simon Josefsson
 License: GPL-3+
--- This rest of this file is taken from appendix A of RFC 4120,
--- http://www.ietf.org/rfc/rfc4120.txt (MD5
--- f95332f70f18eb9252756c7e2accc141), with two minor modifications
--- marked with "libtasn1 bug" below.  RFC 4120 exhibit the ISOC
--- copyright, althought it does not cover the ASN.1 schema, see
--- discussions in the IETF IPR WG.  I have acquired permission to use
--- the ASN.1 schema from RFC 4120 under the MIT/X11 license from all
--- authors but Tom Yu (as of April 2006).  For prudence, asking the
--- Kerberos WG whether anyone else contributed significantly to the
--- ASN.1 schema also remains.  Further, it seems the IETF IPR WG tend
--- to believe that code extracted from RFCs was intended to be
--- modifiable under RFC 3978, which would be sufficient for an ASN.1
--- schema such as this file, compare ipr-rules-update-07 and
--- <address@hidden>.
--- The IETF lawyer Jorge Contreras has said the following on this
--- topic: "Under RFC 3978, it is currently OK to modify code extracts
--- from RFCs.", see <address@hidden>.
+ - Shishi is free software; you can redistribute it and/or modify it
+ - under the terms of the GNU General Public License as published by
+ - the Free Software Foundation; either version 3 of the License, or
+ - (at your option) any later version.
+
+ - Shishi is distributed in the hope that it will be useful, but
+ - WITHOUT ANY WARRANTY; without even the implied warranty of
+ - MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
+ - General Public License for more details.
+
+ - You should have received a copy of the GNU General Public License
+ - along with Shishi; if not, see http://www.gnu.org/licenses or write
+ - to the Free Software Foundation, Inc., 51 Franklin Street, Fifth
+ - Floor, Boston, MA 02110-1301, USA
+
+ - This rest of this file is taken from appendix A of RFC 4120,
+ - http://www.ietf.org/rfc/rfc4120.txt (MD5
+ - f95332f70f18eb9252756c7e2accc141), with two minor modifications
+ - marked with "libtasn1 bug" below.  RFC 4120 exhibit the ISOC
+ - copyright, althought it does not cover the ASN.1 schema, see
+ - discussions in the IETF IPR WG.  I have acquired permission to use
+ - the ASN.1 schema from RFC 4120 under the MIT/X11 license from all
+ - authors but Tom Yu (as of April 2006).  For prudence, asking the
+ - Kerberos WG whether anyone else contributed significantly to the
+ - ASN.1 schema also remains.  Further, it seems the IETF IPR WG tend
+ - to believe that code extracted from RFCs was intended to be
+ - modifiable under RFC 3978, which would be sufficient for an ASN.1
+ - schema such as this file, compare ipr-rules-update-07 and
+ - <address@hidden>.
+ - The IETF lawyer Jorge Contreras has said the following on this
+ - topic: "Under RFC 3978, it is currently OK to modify code extracts
+ - from RFCs.", see <address@hidden>.
 
 Files: gl/*
 Files: db/gl/*



reply via email to

[Prev in Thread] Current Thread [Next in Thread]