charm-crypto-framework 0.60__tar.gz

charm_crypto_framework-0.60/CHANGELOG

@@ -0,0 +1,100 @@
+v0.60 release (Python 3.8+ and OpenSSL 3.x compatibility)
+---------------------------------------------------------
+- Updated to require Python 3.8+ (dropped Python 2.x support)
+- Full OpenSSL 3.x compatibility across all C extension modules
+- Added PY_SSIZE_T_CLEAN macro to all C modules for Python 3.10+ compatibility
+- Fixed PyLongObject internal structure changes for Python 3.12+
+- Modernized CTR counter module (_counter.c) to use Python 3 Bytes API
+- Updated MIRACL pairing module to use EVP API instead of deprecated OpenSSL functions
+- Modern Python packaging with pyproject.toml (PEP 517/518)
+- Added GitHub Actions CI/CD workflow for automated testing
+- Added type stubs (.pyi files) for C extension modules
+- Upgraded to PBC library 1.0.0
+- Fixed segmentation faults in EC and pairing modules
+- Added new cryptographic scheme implementations and documentation
+- Removed deprecated platform.linux_distribution() usage
+- Removed obsolete distribute_setup.py
+- Updated configure.sh to detect Python 3.8-3.12
+- Various bug fixes and improvements
+
+v0.50 beta release (major release with many changes)
+-------------------------------------------
+- error handling updates to base modules
+- CL03: length of e is now verified, verifyCommit() and header added
+- SHA1(m_i) for doctest (verifyCommit) added
+- added implementation of private aggregate of time series data by Marc Joye et al.
+- added Abe's blind signature scheme [AO00, A01]
+- updated to install file for windows and nsis script.
+- fixed typo in protocol_a00.py and protocol_ao00.py
+- added hibenc_lew11.py
+- added Goldwasser-Micali pkenc scheme
+- added Leontiadis-Elkhyiaoui-Molva scheme
+- added four more ABE schemes
+- re-added Time-based proxy re-encryption scheme implementation for py3
+- added non-monotonic CP-ABE scheme by Yamada, Attrapadung, Hanaoka, Kunihiro
+- update libtomcrypt headers to v1.17
+- fix configure.sh: detect python better. thanks to Neal H. Walfield
+- fix decrypt error when plaintext=0 for Paillier scheme. Closes #97
+- added BBS98 proxy re-encryption scheme
+- added omplementation of AFGH06 scheme
+- interface for Proxy Re-Encryption schemes (charm.toolbox.PREnc)
+- adapted BBS98 to PREnc interface
+- added first NAL16 scheme
+- added NAL16b (CCA_21 version of NAL16a)
+- added scheme from Rouselakis and Waters (maabe_rw12.py)
+- added hash support to wrapped pbc ecc elements (pairingmodule.c)
+- added support for uncompressed curves elements (de)serialization.
+- improved arguments management in (de)serialize methods of the c pairingmodule.
+- improved error management in deserialize c pairingmodule
+- improved error management in pairing product routine of pairinggroup.c
+- improved error handling for initialize and initPP, new preproc attribute.
+- changed hash function from sha1 to sha256 everywhere appropriate
+- simplified encode/decode of messages in ECGroups. Squashed some bugs related to BN_bin2bn/BN_bn2bin
+- updated configure.sh to support ARM (android, raspberry pi, include armv7l support)
+- renamed sha1 to sha2 and update version to v0.5
+- added py2.7 compatibility for pairing group serialize/deserialize
+- added Dockerfile to document installation process
+- fixed compilation errors with OpenSSL 1.1.0 caused by API change
+- ciphertext-policy ABE schemes implemented under asymmetric pairing groups. Any policy represented as a monotone span program can be handled.
+- added support for Mac OS X 10.11+
+- added documentation
+- scheme contributions, bug fixes and/or various improvements from @adelapie, @leontiad, @nikosft, @0xwille, @artjomb, @cygnusv, @lferr, @denniss17, @locksmithone, @leafac, @ElectroSuccess, @sagrawal87. Thanks to all!
+
+v0.43 beta release (infrastructure changes) 
+-------------------------------------------
+- simplified benchmarking interface -- breaks compatibility and see docs
+- added new schemes (some external contributions from Nikos Fotiou, Fan Zhang, Hoeteck Wee)
+- added pre-computation optimization for group exponentiation in pairing-based modules -- see docs 
+- fixed several memory leaks and segmentation faults
+- switched from SHA1 to SHA2 for hashing operations
+- improved serialization -- now using JSON instead of Pickle (security vulnerability)
+- significant improvements to all base modules -- several fixes to integer and ecmodule functions
+- more robust Android build for Charm
+- significant fixes to 2.7 version of Charm
+
+v0.42 beta release (infrastructure changes)
+-------------------------------------------
+- Several bug fixes to base modules (mem leaks, interface issues): pairing (PBC & Miracl), ecc, and integer
+- Added new base module for RELIC and fixed bugs for MIRACL (Note: unified abstract interface for base modules coming in v0.43)
+- Refactored charm package structure. This affects schemes, toolbox, adapters, etc.
+- setup.py now creates Python egg
+- Integrated pytest to replace unit testing framework
+- Added doctests to all Charm schemes
+- Updated documentation 
+
+v0.4 beta release
+-----------------
+- Several bug fixes to base modules: pairing (PBC & Miracl), ecc, and integer
+- Major changes to base module API. Recommend using the group abstraction wrappers: PairingGroup, ECGroup, and IntegerGroup
+- Removed pairing curve params in favor of a unified 'toolbox/pairingcurve.py' with curve identifiers (e.g., SS512, MNT224, etc)
+- Deleted the 'params' dir (See previous bullet)
+- Added high-level serialization API to simplify managing ciphertexts and keys in applications
+- Added PKCS #7 padding to toolbox
+- Added public key encryption schemes: 2 new IBE schemes (ibenc_ckrs09, ibenc_lsw08)
+- Added signature schemes: CL04 (anony. creds)
+- Added verifiable random function (VRF) scheme
+- Updates to KPABE scheme with new adapter
+- Improved protocol engine: automatically store data transmitted between parties and more flexibility in state transition map  
+- Updated CNS07 scheme 
+- Name updates to authenticated crypto abstraction
+- Updated documentation for generating group parameters and using our serialization interface

charm_crypto_framework-0.60/INSTALL

@@ -0,0 +1,349 @@
+Charm-Crypto: Installation Documentation
+-------------------------------------------------------------------------------------------
+
+Charm has automated the installation process such that the end-user
+does not have to directly handle dependencies, linking, compiler flag setting, and the
+like.  However, there is always the corner case in which an end-user is using a currently
+unsupported platform, and thus may need to build and install using a very manual process.
+
+We would like to support you in this case, and have written this documentation to get 
+you started on your path using Charm.  This installation file will contain some
+installation blocks highlighting each respective implementation.  
+
+Before we begin, please note the current dependencies:
+    
+- Python 3.8 or later (Python 2 is no longer supported)
+
+- Pyparsing http://pyparsing.wikispaces.com/
+
+- GMP 5.x http://gmplib.org/ 
+
+- PBC 0.5.14 http://crypto.stanford.edu/pbc/news.html
+
+- OPENSSL http://www.openssl.org/
+
+See ./configure.sh --help for other options.
+	
+	
+BUILDING IN LINUX
+------------------------
+
+Note that the entire compilation process is supported by the Charm configure/make scripts.
+The steps for building in linux this way are:
+	1. In a terminal, run configure.sh
+    2. sudo make
+    3. sudo make install
+	
+[Ubuntu 20.04/22.04/24.04 LTS]
+
+1. Before installing Charm, there are a few prerequisites that need to be installed on your system:
+	1. Git
+		sudo apt-get install git
+	2. Python 3 and header files
+		sudo apt-get install python3 python3-dev python3-pip
+	3. Build tools
+		sudo apt-get install build-essential m4 flex bison
+	4. Required libraries
+		sudo apt-get install libgmp-dev libssl-dev
+
+2. Now we need to obtain a copy of Charm:
+	git clone https://github.com/JHUISI/charm.git
+
+3. Next, we will install Charm. Navigate to the Charm directory.
+	1. We must first run the configuration script:
+		./configure.sh
+	2. Now we will build and install Charm:
+		make
+		sudo make install
+	3. And finally we must rebuild the searchpath for libraries
+		sudo ldconfig
+
+[Fedora] 
+
+1. Before installing Charm, there are a few prerequisites that need to be installed on your system. These are:
+	1. m4
+		su -c "yum install m4"
+    2. Python 3
+        su -c "yum install python3"
+	3. Header files/static library
+		su -c "yum install python3-devel"
+	4. openssl-devel
+		su -c "yum install openssl-devel"
+
+2. Red Hat/Fedora has decided not to support ECC in OpenSSL due to patent concerns, so we now need to remove their restriction, manually import the required files, and build new shared libraries.
+	1. Remove the ECC restriction
+		1. Navigate to /usr/include/openssl
+			cd /usr/include/openssl
+		2. Open the OpenSSL configuration file for editing using your editor of choice
+			su -c "vi opensslconf-i386.h"
+		3. Remove the flags that restrict the use of ECC
+			Delete (at the beginning of file)
+				#ifndef OPENSSL_NO_EC
+				# define OPENSSL_NO_EC
+				#endif
+				#ifndef OPENSSL_NO_ECDH
+				# define OPENSSL_NO_ECDH
+				#endif
+				#ifndef OPENSSL_NO_ECDSA
+				# define OPENSSL_NO_ECDSA
+				#endif
+			Delete (later on the file)
+				# if defined(OPENSSL_NO_EC) && !defined(NO_EC)
+				# define NO_EC
+				# endif
+				# if defined(OPENSSL_NO_ECDH) && !defined(NO_ECDH)
+				# define NO_ECDH
+				# endif
+				# if defined(OPENSSL_NO_ECDSA) && !defined(NO_ECDSA)
+				# define NO_ECDSA
+				# endif
+		4. Save the file and close it
+	2. Add the ECC files
+		1. Navigate to http://www.openssl.org/source/ and download the latest version of openssl source
+		2. Untar it
+		3. Navigate to /path/to/openssl-[version]/include/openssl (ie inside the untarred file)
+			cd /path/to/openssl-[version]/include/openssl
+		4. Add the new files to the current OpenSSL installation
+			su -c "yes n | cp * /usr/include/openssl"
+	3. Build the new shared libraries
+		1. Navigate to your downloaded version of OpenSSL
+			cd /path/to/openssl-[version]/
+		2. Configure OpenSSL to make the shared libraries
+			./config shared
+		3. Make the new OpenSSL library
+			make
+	4. Move the new shared libraries with their links
+		su -c "cp --no-dereference libcrypto.so /usr/local/lib/libcrypto.so.10"
+		su -c "cp libcrypto.so.1.0.0 /usr/local/lib"
+		su -c "cp --no-dereference libssl.so /usr/local/lib/libssl.so.10"
+		su -c "cp libssl.so.1.0.0 /usr/local/lib"
+		su -c "cp libcrypto.a /usr/local/lib"
+		su -c "cp libssl.a /usr/local/lib"
+	5. And now we need to set the library search path to look for the libraries we just added first.
+		cd /etc/ld.so.conf.d/
+		su -c "vi charm.conf"
+		put "/usr/local/lib" (without quotes) into the file, save, and close
+		su -c ldconfig
+	6. Set the library search path to look for the new libraries first (either type this into your terminal or put it in your .bashrc file and source it)
+		export LD_LIBRARY_PATH=/usr/local/lib/:$LD_LIBRARY_PATH
+
+3. Now we need to obtain a copy of Charm:
+	git clone -b master https://github.com/JHUISI/charm.git
+
+4. Next, we will install Charm. Navigate to the Charm directory.
+	1. We must first run the configuration script:
+		su -c ./configure.sh
+
+		If the output of the configure script says that libgmp is already installed (and this is your first time installing Charm), chances are you have an outdated version of GMP.  We need to check which version of libgmp you have installed.
+			su -c updatedb
+			locate libgmp
+		If you don't see libgmp.so.10 OR libgmp.so.10.0.2 in the resulting list, then you will need to build the GMP libraries from source.
+			1. Download the latest version of the GMP source from ftp://ftp.gnu.org/gnu/gmp/gmp-5.0.2.tar.gz
+			2. Untar it
+			3. Navigate to /path/to/gmpsource (ie inside the untarred file)
+				cd /path/to/gmpsource
+			4. Build and install the libraries
+				./configure
+				make
+				su -c "cp gmp.h /usr/local/include"
+				su -c "make install"
+            5. You now have two options (remove or keep the old libraries):
+				1. Remove the old libraries
+					cd /usr/lib
+					su -c "rm libgmp.*"
+				2. Keep the old libraries, rename the new one
+					1. Determine the version of the old library
+						su -c updatedb
+						locate libgmp
+					2. Look for /usr/lib/libgmp.so.X in the resulting list where X is a number (NOT /usr/lib/libgmp.X.Y.Z)
+					3. Rename the new link
+						cd /usr/local/lib
+						su -c "mv libgmp.so.10 libgmp.so.X"
+			6. Rebuild the searchpath for libraries
+				su -c ldconfig
+	2. Now we will build and install Charm:
+		su -c "make"
+		su -c "make install"
+	3. And finally we must rebuild the searchpath for libraries
+		su -c ldconfig
+
+[Fedora x86_64]
+
+[Mint x86_64]
+1. Before installing Charm, there are a few prerequisites that need to be installed on your system. These are:
+        1. Git
+                sudo apt-get install git
+        2. m4
+                sudo apt-get install m4
+        3. Python 3
+                sudo apt-get install python3
+        4. Header files/static library
+                sudo apt-get install python3-dev
+        5. libssl-dev (only necessary if you did not install Python 3)
+                sudo apt-get install libssl-dev
+        6. This distro doesn't seem to come with binutils or gcc, install those.
+
+2. Now we need to obtain a copy of Charm:
+	git clone git://github.com/JHUISI/charm.git
+
+3. Next, we will install Charm. Navigate to the Charm directory.
+        1. We must first run the configuration script:
+                sudo bash ./configure.sh                * Bash to avoid unexpected operator error.
+        2. Now we will build and install Charm:
+                sudo make
+                sudo make install
+        3. And finally we must rebuild the searchpath for libraries
+                sudo ldconfig
+
+[Creating a .deb]
+If you want to create a .deb binary from the charm source, there are a
+couple more steps. The following was tested in Ubuntu 16.04 (x86_64).
+1. Before installing Charm, there are a few prerequisites that need to be installed on your system. These are:
+        1. Git
+                sudo apt-get install git
+        2. m4
+                sudo apt-get install m4
+        3. Python 3
+                sudo apt-get install python3
+        4. Header files/static library
+                sudo apt-get install python3-dev
+        5. libssl-dev (only necessary if you did not install Python 3)
+                sudo apt-get install libssl-dev
+        6. Additional packages related to packaging for .deb
+                sudo apt-get install python3-all-dev debhelper python3-pip
+        7. The stdeb python package, installed via pip
+                pip3 install stdeb
+        8. Verify that *all* of the dependencies at the top of the
+            document are satisfied. Not doing this may result in strange
+            bugs while compiling the .deb from source.
+
+2. Now we need to obtain a copy of Charm:
+	git clone git://github.com/JHUISI/charm.git
+
+3. Next, we will install Charm. Navigate to the Charm directory.
+        1. We must first run the configuration script:
+                sudo bash ./configure.sh                * Bash to avoid unexpected operator error.
+        2. Now we will build and install Charm:
+                sudo make
+                sudo make install
+        3. And finally we must rebuild the searchpath for libraries
+                sudo ldconfig
+
+4. Finally, we will build the installer. Navigate to the installers/deb.installer directory, and at a shell prompt run
+    sudo python3 create_deb.py      * use python instead of python3 to make a 2.7 binary
+
+5. Install the created .deb file.
+
+
+    
+BUILDING IN WINDOWS
+------------------------
+
+Note that the entire compilation process is now supported by the Charm configure/make scripts.
+The steps for building in mingw32 this way are:
+    1. Download the latest source version of openssl.
+	2. Run MinGW Shell.
+    3. Extract openssl, configure and install as shown below.	
+	4. Extract Charm, and navigate to the top directory.
+	5. Run configure.sh as shown below.
+	6. The process will fail out at wget, and open Internet Explorer to the wget download 
+	   page.
+	7. Install wget, and set it's bin directory on your PATH.  To do this, right-click My 
+	   Computer, Select Properties, Select Advanced System Settings, Select Advanced, Select
+       Environment Variables, and than PATH.  Scroll to the end, and enter a ; followed by 
+       the absolute path to the bin directory (e.g., C:\Program Files\etc).
+    8. With wget installed, run the configure.sh script again, and it should set up your
+       Make dependencies for you.  
+    9. Make build.
+   10. Make install.
+    *. Another way to install dependencies is to follow the Windows blocks below.	
+
+[MinGW32 and Cygwin]
+
+Let's first build our dependencies with the following scripts:
+	
+	#GMP
+	./configure --prefix=/mingw --disable-static --enable-shared
+	make
+	make install
+	
+	#OPENSSL
+	./config --openssldir=/mingw --shared # This gets us around installing perl.
+	make
+	make install
+
+        # ** NOTE ** openssl-1.0.0e ./test compilation problems.
+        # You will run into a compilation error that looks similar to:
+        #    mdtest.c:1:10 error: expected ...
+        #
+        # To mitigate, do the following:
+        #    grep "./test/dummytest.c" *
+        #    edit each file from "dummytest.c" to "#include "dummytest.c"
+
+	#PBC
+	./configure --prefix=/mingw --disable-static --enable-shared
+	make
+	make install
+	
+	#Building Charm
+	./configure --prefix=/mingw --python=/c/Python32/python.exe 
+
+        # ** NOTE ** The latest mingw installer comes coupled with gcc-4.6.x
+        # which no longer supports the flag -mno-cygwin.  This, unfortunately,
+        # is called during python setup.py build as it is a part of a class
+        # in distutils for python.  A fix is coming for python to evaluate
+        # the gcc compiler version, and remove the flag -mno-cygwin if it
+        # 4.6+, but that has yet to be implemented.  
+
+[Building Executable]
+
+	If you are building to make an executable with NSIS, than be sure to
+	compile the dependencies first and pass the appropriate header and
+    library files to --python-build-ext (calls build_ext option for setup).	
+	
+	    ./configure.sh --python=/c/Python32/python.exe --python-build-ext="-L/path/to/lib -I/path/to/header"
+	
+
+     Need help building the dependencies? Follow the below:
+		#GMP
+		./configure --prefix=/c/charm-crypto --disable-static --enable-shared
+		make
+		make install
+
+		#PBC
+		./configure --prefix=/c/charm-crypto --disable-static --enable-shared LDFLAGS="-L/c/charm-crypto/lib" CPPFLAGS="-I/c/charm-crypto/include"
+		make
+		make install
+
+		#OPENSSL
+		./config --openssldir=/c/charm-crypto --shared # This gets us around installing perl.
+		make
+		make install
+
+
+BUILDING IN OS X
+------------------------
+
+Note that the entire compilation process is supported by the Charm configure/make scripts.
+
+[macOS (Monterey, Ventura, Sonoma)]
+
+1. Install Homebrew if not already installed:
+	/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
+
+2. Install dependencies via Homebrew:
+	brew install gmp openssl@3 flex bison wget
+
+3. Build and install PBC library:
+	wget https://crypto.stanford.edu/pbc/files/pbc-1.0.0.tar.gz
+	tar -xzf pbc-1.0.0.tar.gz
+	cd pbc-1.0.0
+	./configure LDFLAGS="-L$(brew --prefix gmp)/lib" CPPFLAGS="-I$(brew --prefix gmp)/include"
+	make
+	sudo make install
+
+4. Configure and build Charm:
+	./configure.sh --enable-darwin
+	make
+	sudo make install
+

charm_crypto_framework-0.60/LICENSE.txt

@@ -0,0 +1,165 @@
+                   GNU LESSER GENERAL PUBLIC LICENSE
+                       Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+
+  This version of the GNU Lesser General Public License incorporates
+the terms and conditions of version 3 of the GNU General Public
+License, supplemented by the additional permissions listed below.
+
+  0. Additional Definitions.
+
+  As used herein, "this License" refers to version 3 of the GNU Lesser
+General Public License, and the "GNU GPL" refers to version 3 of the GNU
+General Public License.
+
+  "The Library" refers to a covered work governed by this License,
+other than an Application or a Combined Work as defined below.
+
+  An "Application" is any work that makes use of an interface provided
+by the Library, but which is not otherwise based on the Library.
+Defining a subclass of a class defined by the Library is deemed a mode
+of using an interface provided by the Library.
+
+  A "Combined Work" is a work produced by combining or linking an
+Application with the Library.  The particular version of the Library
+with which the Combined Work was made is also called the "Linked
+Version".
+
+  The "Minimal Corresponding Source" for a Combined Work means the
+Corresponding Source for the Combined Work, excluding any source code
+for portions of the Combined Work that, considered in isolation, are
+based on the Application, and not on the Linked Version.
+
+  The "Corresponding Application Code" for a Combined Work means the
+object code and/or source code for the Application, including any data
+and utility programs needed for reproducing the Combined Work from the
+Application, but excluding the System Libraries of the Combined Work.
+
+  1. Exception to Section 3 of the GNU GPL.
+
+  You may convey a covered work under sections 3 and 4 of this License
+without being bound by section 3 of the GNU GPL.
+
+  2. Conveying Modified Versions.
+
+  If you modify a copy of the Library, and, in your modifications, a
+facility refers to a function or data to be supplied by an Application
+that uses the facility (other than as an argument passed when the
+facility is invoked), then you may convey a copy of the modified
+version:
+
+   a) under this License, provided that you make a good faith effort to
+   ensure that, in the event an Application does not supply the
+   function or data, the facility still operates, and performs
+   whatever part of its purpose remains meaningful, or
+
+   b) under the GNU GPL, with none of the additional permissions of
+   this License applicable to that copy.
+
+  3. Object Code Incorporating Material from Library Header Files.
+
+  The object code form of an Application may incorporate material from
+a header file that is part of the Library.  You may convey such object
+code under terms of your choice, provided that, if the incorporated
+material is not limited to numerical parameters, data structure
+layouts and accessors, or small macros, inline functions and templates
+(ten or fewer lines in length), you do both of the following:
+
+   a) Give prominent notice with each copy of the object code that the
+   Library is used in it and that the Library and its use are
+   covered by this License.
+
+   b) Accompany the object code with a copy of the GNU GPL and this license
+   document.
+
+  4. Combined Works.
+
+  You may convey a Combined Work under terms of your choice that,
+taken together, effectively do not restrict modification of the
+portions of the Library contained in the Combined Work and reverse
+engineering for debugging such modifications, if you also do each of
+the following:
+
+   a) Give prominent notice with each copy of the Combined Work that
+   the Library is used in it and that the Library and its use are
+   covered by this License.
+
+   b) Accompany the Combined Work with a copy of the GNU GPL and this license
+   document.
+
+   c) For a Combined Work that displays copyright notices during
+   execution, include the copyright notice for the Library among
+   these notices, as well as a reference directing the user to the
+   copies of the GNU GPL and this license document.
+
+   d) Do one of the following:
+
+       0) Convey the Minimal Corresponding Source under the terms of this
+       License, and the Corresponding Application Code in a form
+       suitable for, and under terms that permit, the user to
+       recombine or relink the Application with a modified version of
+       the Linked Version to produce a modified Combined Work, in the
+       manner specified by section 6 of the GNU GPL for conveying
+       Corresponding Source.
+
+       1) Use a suitable shared library mechanism for linking with the
+       Library.  A suitable mechanism is one that (a) uses at run time
+       a copy of the Library already present on the user's computer
+       system, and (b) will operate properly with a modified version
+       of the Library that is interface-compatible with the Linked
+       Version.
+
+   e) Provide Installation Information, but only if you would otherwise
+   be required to provide such information under section 6 of the
+   GNU GPL, and only to the extent that such information is
+   necessary to install and execute a modified version of the
+   Combined Work produced by recombining or relinking the
+   Application with a modified version of the Linked Version. (If
+   you use option 4d0, the Installation Information must accompany
+   the Minimal Corresponding Source and Corresponding Application
+   Code. If you use option 4d1, you must provide the Installation
+   Information in the manner specified by section 6 of the GNU GPL
+   for conveying Corresponding Source.)
+
+  5. Combined Libraries.
+
+  You may place library facilities that are a work based on the
+Library side by side in a single library together with other library
+facilities that are not Applications and are not covered by this
+License, and convey such a combined library under terms of your
+choice, if you do both of the following:
+
+   a) Accompany the combined library with a copy of the same work based
+   on the Library, uncombined with any other library facilities,
+   conveyed under the terms of this License.
+
+   b) Give prominent notice with the combined library that part of it
+   is a work based on the Library, and explaining where to find the
+   accompanying uncombined form of the same work.
+
+  6. Revised Versions of the GNU Lesser General Public License.
+
+  The Free Software Foundation may publish revised and/or new versions
+of the GNU Lesser General Public License from time to time. Such new
+versions will be similar in spirit to the present version, but may
+differ in detail to address new problems or concerns.
+
+  Each version is given a distinguishing version number. If the
+Library as you received it specifies that a certain numbered version
+of the GNU Lesser General Public License "or any later version"
+applies to it, you have the option of following the terms and
+conditions either of that published version or of any later version
+published by the Free Software Foundation. If the Library as you
+received it does not specify a version number of the GNU Lesser
+General Public License, you may choose any version of the GNU Lesser
+General Public License ever published by the Free Software Foundation.
+
+  If the Library as you received it specifies that a proxy can decide
+whether future versions of the GNU Lesser General Public License shall
+apply, that proxy's public statement of acceptance of any version is
+permanent authorization for you to choose that version for the
+Library.

charm_crypto_framework-0.60/MANIFEST.in

@@ -0,0 +1,12 @@
+include VERSION README.md INSTALL configure.sh Makefile CHANGELOG setup.cfg
+include LICENSE.txt pyproject.toml config.dist.py pytest.ini
+graft doc
+graft doc/source
+recursive-include charm *.h *.c *.py
+prune build
+prune deps/pbc
+prune deps/relic
+prune *.egg-info
+global-exclude __pycache__
+global-exclude *.py[cod]
+global-exclude *.so