yafox
/
tfc-mirror
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Delete LICENCE.md

This commit is contained in:
Markus Ottela 2016-05-06 16:20:08 +03:00
parent 8390d753ad
commit 1e405bef62
1 changed files with 0 additions and 260 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

260
LICENCE.md
View File

@ -1,260 +0,0 @@
#Licences
### C-programs
Copyrights of the design schematic for HW RNG belong to Giorgio Vazzana and
are modified and published under GNU free license and written permission of the
author.
### Data diode
Copyrights for the design schematics of the RS-232 Data Diode belong to
Douglas W. Jones and are published used under GNU free license and used in
this document accordingly.
### TFC Documents
Both the white paper and manual are released under GNU Free Documentation
License 1.3
### TFC Suite
Tx.py, Rx.py, NH.py, test_tx.py, test_nh.py, test_rx.py, hwrng.py, setup.py
and dd.py are part of the TFC application, which is free software: You can
redistribute it and/or modify it under the terms of the GNU General Public
Licence as published by the Free Software Foundation, either version 3 of the
Licence, or apart from specified sections[1], (at your option) any later
version. TFC 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 Licence for more details. For a
copy of the GNU General Public License, see http://www.gnu.org/licenses/
[1] print_banner() style 3 in Tx.py, Rx.py and NH.py are based on matrix curses
by Tom Wallroth. This code is used, modified and published under GNU GPL v2
licence.
##PyNaCl
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
###NOTICES
Since making changes to crypto libraries is generally not a good idea,
here is documentation that explains why each change was made and how
they do not weaken security.
https://github.com/maqp/pynacl/commit/
a89b862a703353fd536951eea574ef4305030a11#diff-ac3b39a5ab4db5864edbe34708be717d
Added a getter shared_key() to extract the ECDHE shared secret after key
exchange; This allows Tx.py to generate two separate symmetric keys by
generating them using PBKDF2-HMAC-SHA256, each key salted with a different
public key. While nonce-based crypto would be secure with two parties
using the same key, it would have no forward secrecy. TFC generates
forward secrecy with cyclic hashing of key through PBKDF2-HMAC-SHA256
between every message. Using only one key would mean any offset in state
of key would lead to retrospective decryption of messages between the
two states, if end points were physically compromised.
TFC has always included an option for Raspberry Pi and HWRNG generated keys.
The edit to PrivateKey.generate() allows user to mix in entropy from the
HWRNG during private key generation. External entropy is XORed with standard
entropy of the library -- it has no adverse effects and can only add entropy
to keys.
Simple proof of this is assume the external entropy is malicious. It could
try to generate a keystream based on nacl.utils.random(), aiming to produce
a final output that is a bit string of zeroes. This is not possible as
external entropy is loaded before PyNaCl's CSPRNG random() is called.
Alternatively, the external entropy can be malicious, predictable bit
sequence that provides no additional entropy. This is in no way different
from XORing the random() function's output with arbitrary number of times
with any completely predictable string, e.g. a bit-string of 0s, that has
no effect on entropy random() returns. Therefore, the external entropy can
not weaken the overall security.
This property is used when no external entropy is provided. In those cases,
the output random() is in fact XORed with bit-string of zeroes, and it will
lead to exact same output as that of random(). Since constant time XOR
operation is performed for every generation time, it introduces practically
no timing attacks. Also, in the case of TFC, adversary is unable to exploit
TxM behind data diode, and obtain information about when the key generation
started. Instead, they will first learn about the key generation when TxM
outputs the public key to contact.