Documentation for “Zerocat Mini Machine”
Generated on: Tue, 03 Dec 2024 15:05:40 +0100
Repository: git://zerocat.org/zerocat/projects/zerocat-mini-machine
Version: v0.0.0-249-9bbfd9f
Branch: master
Foldable chassis with transparent keyboard, both designed to ease user’s audit and inspection.
Copyright (C) 2021 Kai Mertens kmx@posteo.net
Copyright (C) 2022, 2023 Kai Mertens kmx@posteo.net
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License".
Zerocat Mini Machine is a laptop-like, word processing machine of supreme integrity. It uses encrypted Morse code for inter-device data transmission, and focuses on audio rather than wire.
This file is to be as short as possible. It provides information on how to generate the project’s verbose documentation, and how to compile the source code, if any.
It is assumed that you are running a GNU/Linux-libre operating system. We recommend to run GNU Guix System – alternatively, install the GNU Guix package manager.
Use Git to clone the project’s sources:
$ git clone git://zerocat.org/zerocat/projects/zerocat-mini-machine
Change into the project’s documentation folder:
$ cd zerocat-mini-machine/doc/
Study this README.md to get started:
$ cat ../doc/README.md
All paths within the documentation are relative to the location of the
documentation source files, which are located in this project’s doc/
folder.
Versions are tagged according to the following pattern:
v<major>.<minor>.<revision>
<major> – The resulting product is a major change or upgrade.<minor> – Additional functionality or new features are introduced.<revision> – Bug fixes, minor changes, graphical stuff.A tag should be annotated with related change log entries.
The first tag should be: v0.0.0
To checkout a version tag, run:
git checkout vx.x.x
However, this should be optional.
Using the tip of branch master should be just fine.
Use GNU Make to create a dedicated profile, and an up-to-date profile generation. This allows you to match your environment to the one used by Zerocat, thus yielding for bit-identical results:
$ make -C ../guix pull
Checkout the profile generation, instantiate channels, create a pure shell that provides nothing but prerequisites:
$ make -C ../guix environment
To confirm that your project environment is properly set up, run:
[env]$ make -C ../guix usage
Invocations of make to generate the documentation, compile the
sources, etc., should be done from this project environment, only.
To restore the initial environment, later on, when you are done with this project, type:
[env]$ exit
To remove this project’s handy guix profile, type:
$ make -C ../guix clean
This will remove symlinks only. If you want to remove the profile from your system, run the GNU Guix Garbage Collector.
To list all available targets, type:
$ make -C ../guix help
To build the documentation, type:
[env]$ make -C ../doc
The terminal output should provide a shortcut to the index.html file
of the generated HTML documentation. Open this file with your favorite
browser.
To get a full list of available targets, type:
[env]$ make -C ../doc help
To clean-up, type:
[env]$ make -C ../doc clean
To build the documentation in one go, type:
$ echo "make -C ../doc" | make -C ../guix environment
Documentation source files are written in markdown syntax. They should carry their individual copyright and license notices right below the title giving headline, e.g.:
<Title-of-Document>
===================
Copyright (C) <Year> <Name-of-Author> <Email-Address>
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.3
or any later version published by the Free Software Foundation;
with no Invariant Sections, no Front-Cover Texts, and no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License".
<Other-Headline>
----------------
...content...
The generated documentation carries a license notice right at top on
its title page, with copyright statements generated from git log
output.
Sections of the generated documentation are build from selected markdown source files, with their individual copyright and license notice stripped.
In order to enrich the generated documentation ...
*.md markdown source files to ../doc/.... and adapt ../doc/Makefile to produce nice output.
In case more tools are needed, don't forget to update ../guix/manifest0.scm.
To make your image look nice within the documentation, select a landscape layout of 16:9 aspect ratio.
Use ImageMagick to prepare your image, e.g.:
If your image is big, reduce it to a maximal width of 2000 pixel:
mogrify -resize 2000x <image>
Please clean image files from metadata, before committing, i.e.:
mogrify -strip <image>
If you embed your image into a markdown documentation file, use this syntax:
![<path/to/image>][]
[<path/to/image>]: <path/to/image> "title message"
or alternatly:
![<path/to/image>][my-image-shortcut]
[my-image-shortcut]: <path/to/image> "title message"
These patterns will guarantee that <img> tags have their src,
alt and title attributes properly set within the html output.
Change into folder ../hardware, which ships the project’s gEDA/gaf
resource file. Then, using the project environment, invoke gschem.
Within your circuit schematic, you can use specific texts as placeholder objects. They will be replaced with generated values by the documentation build process. When used within the informational fields of a titleblock, use the specified sizes and alignments:
$TITLE (Size 14, Alignment “Lower Right”)$SUBTITLE (Size 9, Alignment “Lower Right”)$GITREPO (Size 8, Alignment “Lower Right”)$FILENAME (Size 8, Alignment “Lower Right”)$PAGE (Size 8, Alignment “Lower Left”) – reserved for future use$PAGES (Size 8, Alignment “Lower Left”) – reserved for future use$GITREF (Size 8, Alignment “Lower Right”)$AUTHORS (Size 8, Alignment “Lower Right”)In case you are going to embed images, make sure to use a relative
path. Per default, gschem uses absolute paths that might reveal a
private username or folder. You can use nano to edit your schematics
outside of gschem.
Please use this license header for code source files:
Zerocat Mini Machine --- A word processing machine of supreme integrity.
Copyright (C) <Year> <Name-of-Author> <Email-Address>
This file is part of Zerocat Mini Machine.
Zerocat Mini Machine 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.
Zerocat Mini Machine 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 Zerocat Mini Machine.
If not, see <http://www.gnu.org/licenses/>.
If you intend to write shell scripts, use this skeleton to make them work for GNU Guix:
#!/bin/sh
# Re-exec if we are not using Bash or are using Bash in POSIX mode.
if [ -z "$BASH" ] || [ "$BASH" = "/bin/sh" ]; then
bash=`command -v bash`
if [ -z "$bash" ]; then
echo "Couldn't find Bash, sorry!"
exit 1
else
exec "$bash" "$0" "$@"
fi
fi
# We're using Bash now.
set -o errexit
set -o nounset
set -o pipefail
# Your code goes here ...
Update ../doc/CHANGES.md and list your contributions.
You can use git shortlog to get a starting point for your edit.
Go ahead. Fund the project now. Join the future community!
This project depends on funding:
Private pocket
The project’s first chassis prototype has been elaborated during March, April and May 2023, to give you a clear idea of the targeted vision. The prototype work and its documentation, presented as of May 2023, has been funded by workshop donations and modest, private means.
Your donations
Help is needed, ad-hoc, now! A budget of 5,000.00 Euro is to be collected during June, July and August 2023 in order to get prepared for public funding and/or a large scale crowdfunding campaign. Please go ahead and donate. You can find bank account details on Zerocat’s website: http://www.zerocat.org/donate.html
Provide your name or nickname in case you would like to see it on the list of donators and supporters.
Public funding
This project heads for the improvement of digital communication equipment, and as such should be able to apply for a grant, as provided by NGI Zero Entrust. An estimated budget of 50,000.00 Euro would leave 10,000.00 Euro per module development, or 25,000.00 Euro per year. As announced by the NLnet Foundation, the next regular deadline for applications is: 1st of August 2023
Crowdfunding campaign
Hardware projects of similar type and quality are usually using a crowdfunding platform like Startnext (Germany) or CrowdSupply (USA). If these platforms are considered, a budget of 100,000.00 Euro should be the goal, as extra time and expertise is required to get the campaign set up and to keep it maintained. The greater budget would also allow to extend the project duration and the targeted achievements.
You can help to spread the message using Zerocat’s Handout PDF, which will be updated from time to time – Thank You!
Zerocat Mini Machine ships copyrighted work.
Zerocat Mini Machine is free software. It makes use of free software licenses as recognized by Free Software Foundation (FSF), and should be freely distributable:
Files located in folder hardware/, if available, describe hardware
of a free design, licensed under:
Authorship, copyright and license information may be provided in more detail on a per-folder and/or per-file basis. Check the sources.
Please send your report if you find the distribution hindered.
See Zerocat Website for contact information.
This file tracks changes that are introduced to the project.
However, changes introduced to hardware design files are tracked with:
../hardware/CHANGES.md
NOTICE: Anyone modifying the project should provide brief information about the modifications, including the date they were made. Information should be added but never removed from this file. Licensees should provide a brief entry with a date and the nature of the modification for each change. Please use markdown syntax!
2023/07/28: Roadmap refined, budget estimated
The overall project budget has been trimmed to stay just below EUR 50,000.- by focusing on prototyping, strictly. However, the manufacturing of devices for the webshop, made of glazed pottery, is suggested as a next step, upon success of the prototyping project.
2023/07/15: Refine documentation’s layout for wide viewports
2023/07/09: Improve documentation
Fix keyboard’s missing keycap #42, add animation video, enrich points of interest, review goal description, visualize communication paths, promote usage of Morse code via sound and light beam, merge transmission modules into just one, list issues in separate file, update manifest file, add eligibility checklist, set up preliminary roadmap.
2023/06/25: Receive feedback
Refine order of sections, add images, reword goal description
2023/05/31: Launch of project, tagged as: v0.0.0
This first version ships a wooden prototype chassis, well documented with plein-air photos, CAD files and how-tos.
2023/04/01: Provide change log file with a first entry.
Let me express my special thanks to:
Greta – for helping me in times of financial despair
Susanne Bellinghausen and Stephen Kovats – for giving me shelter, coffee and a perfect work environment
Timm Wille – for his tremenduously motivating points of view
Jorgo Triantafilidis – for his review and valuable feedback
Prof. Volker Roth – for emphasizing the qualities (low complexity, 100% free design) of the Parallax P8X32A microcontroller in comparison to RISC-V and Low Risc as of 2023.
Ricardo Morte – for his input and inspiration to start this project in 2021.
For now, the project has no mechanism to place and track issues, reported by non-project audience. Please send a mail to the author(s), this file will get updated accordingly. Thanks!
These issues are to be clarified, next:
The keyboard misses crucial key #42: <Enter>
How to combine wood and batteries, while reducing risk of fire?
How to deal with electrostatic charges?
Production of keycaps per lathe is not meant for everyone
Project has no issue tracker
Approach alternative module material: Pottery and glaze
Add 7-LED circuit schematic and footprint
Get prepared for NLnet Foundation, check FAQ
In what differs this project from bunnie’s precursor?
Edit #../doc/FUNDING.md:
Edit #../doc/circuits.md:
Edit #../doc/integrity.md:
The goal of Zerocat Mini Machine is to provide you with a trustworthy, lean, laptop-alike mini machine of a free-design, even down to chip level, easily inspectable, intuitively verifyable on a daily basis.
It helps you to enter words and texts in an intgre way, to store them on simple, trustworthy media, and to produce sound or light output for transmission.
Zerocat Mini Machine focuses on text editing, text encryption, secure file storage, and secure file transfer between Zerocat Mini Machine devices over short and medium distances, avoiding the Internet.
Input of secret words and texts is done by means of the integrated, transparent keyboard. Using microphones instead would not be a good option, as it became hard to find clean, smartphone-free rooms and environments, especially in cities.
The device’s transmission module with loudspeaker and microphone is used in conjunction with high speed, multi channel Morse code – that is Morse code of tenfold frequency, simultaneously send over different frequencies, for example.
For short distances, Internet is not required, and the Mini Machines interact as stand-alone devices. In case of failure or during debugging sessions, the transmission of encrypted base16 data can be recorded with any device, played back with reduced speed, thus making it human readable again.
The transmission module offers wireless transmission via light beam as an alternative. Distances of probably 100m might be manageable with proper weather conditions.
Long distance transmissions without Internet might still be achievable by means of amateur radio stations, using Morse code on short wave. Radio operators manage to run two-way communications well beyond earth’s horizon (40 miles), reaching distances of more than 1000km with proper atmospheric conditions.
Interfaces such as RS232 and SPI should ease interaction with standard laptops or desktop machines, allowing to transmit via e-mail or snail-mail, shipping files on SD cards or SPI flash chips, or simply to transmit via wire.
However, audible Morse code perfectly matches for active voice chat or phone call conversations, set up per smartphones, laptops or desktops, thus supporting standard communication paths as well. Zerocat Mini Machine is meant to be a stand-alone device, but would match and combine with existing technology and transmission paths via Internet or Terrestrial Trunked Radio.
The power consumption of Zerocat Mini Machine is expected to be low enough to make it a portable device. Special requirements might be introduced by the display and transmission modules.
Materials and manufacturing toolchains should be simple enough to support small scale, community driven fab-labs as well as hobbyists. Usage of plastics, resins, paints and glue is greatly reduced in favor of wood, screws, clay and glaze. PCBs might be wired by hand (prototype boards), milled, or ordered from dedicated manufacturers. Optionally, it should be possible to pack kits, giving some extra fun to the end-user and increasing individual value.
The project shall be split into two major blocks of development, which should be achievable within 12 months, each:
Development of two pairs of functioning prototype devices that are able to communicate with each other per Morse code as sound and light beam.
This involves:
a) Fast prototyping with wooden chassis modules, which can easily be adapted, cut, glued, screwed during the process of cahssis and PCB development.
b) Transformation of the chassis towards glazed pottery. These chassis are expected to be colorful, shiny, sexy, individual, authentic and secure, and best suited to represent a fashion accessoire, making it appealing and attractive for non-tech users. These devices are meant to enter the RYF-compatible web shop, later on.
Implementation of strong cryptography. File storage and data transmission would move forward towards being processed securely and privately. In order to implement strong cryptography, a dedicated level of expertise is required and has to be accumulated, first. Small but essential improvements on the PCBs might be necessary, e.g.: Addition of a random number generator, replacement of inter-modular copper buses by light transmissions, additional input devices – but change of the chassis or module frames is not expected.
Zerocat Mini Machine focuses on audible, encrypted Morse code to achieve data transmission, as this old technique has essential advantages over modern ones:
In case of device failure or during debugging, Morse code remains human readable, at least for skilled, trained people.
Morse code has inherent signal-to-noise ratio advantages. The human ear-brain signal processing system can pull weak Morse code signals out of the noise where voice signals would be totally inaudible. It might be regarded as human voice, using just one frequency.
Morse code transmitters and receivers should be simple to construct.
Audible Morse code is not covered by royalties, patents, or license fees. Using audible data transmission channels does not require to ask authorities for permission.
Audible Morse code can easily be coupled into an exsisting phone call conversation, no extra interface required.
Audible Morse code can easily be coupled to an exsisting voice chat conversation, set up with standard (or better: corebooted) laptops and desktops. Again, no extra interface required.
Morse code integrates perfectly into User Controlled Technology, as it focuses on text rather than digital data. Knowing Morse code is not required to operate the device, but if required, people can train themselves with simple means. Learning Morse code is best done intuitively, when it is heard, rather than being tought in an abstract level.
Even nowadays Morse code is used by amateur radio operators, that manage to establish two-way transmissions going well beyond earth’s horizon (40 miles distance). With proper atmosperic conditions, distances of more than 1000 kilometers are achievable by using short wave radio. Again, no extra interface should be required, radio operators love to use microphones.
data sent as:
Alice’s ---> encrypted Morse code¹ ---> Bob’s
Devices Devices
·····|chat|·····
____: ____:
speaker <)))))))) /…… / /…… / ))))) ] microphone
· """""' """""' ·
· laptops ·
· ·
· ·
· ·
· ·
· /····|call|·····/ ·
· __/ __/ ·
· /… / /… / ·
<)))))))) /… / /… / ))))) ]
· /__/ /__/ ·
· phones ·
· ·
with internet · ·
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
without internet · ·
· ·
· ·
· ·
· /···|TETRA°|····/ ·
· _ / __/ ·
· /»»/ /»»/ ·
<)))))))) /»»/ /»»/ ))))) ]
· /__/ /__/ ·
· ·
· °Terrestrial Trunked Radio ·
· ·
· ·
· ·
· ·
· /\ |short| /\ ·
· / ·\···|wave |······\·· ·
· \ / |radio| \ / ·
· _\/_ _\/_ ·
>))))))) ]……o< ]……o< )))) ]
· |___| |___| ·
· radios ·
· ·
· ·
· ·
· ·
__ · · __
Mini Machine, _\ \<)))))))))))))))|sound 50m|))))))))) ]/ /_ Mini Machine,
100% integrity, / /\ \ / /\ \ 100% integrity,
input + encryption / / \ \~~~~~~~~~~~~~~|light² 100m|~~~~~~~~~~/ / \ \ decryption + display
_...._ _______/ /____\/_ _\/____\ \_______ _...._
/______\\_____/\/\______/ \______/\/\_____//______\
· | | ^
· | | ·
· | | ·
· \…………………………………………………………………|wire 1000m|…………………………………………………………/ ·
· ·
· ·
· ·
· ·
· cyclist 100km ·
SPI ____ _____ SPI
· |SD \ |\ /| _o ·
····> |Card³| ---> | \_/ | ---> _/\/~ ········
· |_____| |_____| O " O ·
· ·
· ·
· ·
· ·
· car 1000km ·
SPI ____ _____ ____ SPI
· |SD \ |\ /| | | _ ·
····> |Card | ---> | \_/ | ---> | ___|| \ ········
|_____| |_____| |________|
O O
° Terrestrial Trunked Radio, see: https://nlnet.nl/news/2023/20230724-tetra-burst.html
¹ Morse code:
Although computer-based (digital) modes and methods have largely replaced CW [continuous wave, radiotelegraphy using Morse code] for commercial and military applications, many Amateur Radio operators still enjoy using the CW mode—particularly on the shortwave bands and for experimental work, such as Earth–Moon–Earth communication, because of its inherent signal-to-noise ratio advantages. Morse, using internationally agreed message encodings such as the Q code, enables communication between amateurs who speak different languages. It is also popular with homebrewers and in particular with "QRP" or very-low-power enthusiasts, as CW-only transmitters are simpler to construct, and the human ear-brain signal processing system can pull weak CW signals out of the noise where voice signals would be totally inaudible. --- https://en.wikipedia.org/wiki/Amateur_Radio
² Light:
Free-space optical communication (FSO) is an optical communication technology that uses light propagating in free space to wirelessly transmit data for telecommunications or computer networking. "Free space" means air, outer space, vacuum, or something similar. This contrasts with using solids such as optical fiber cable. --- https://en.wikipedia.org/wiki/Free-space_optical_communication
³ SD-Card:
SD cards operate with a default bus protocol of SD mode. However, if a simpler or slower bus is needed, the card can be configured for SPI mode. While in SPI mode, SD cards operate in one-bit bus widths. [...] --- https://www.delkin.com/blog/understanding-the-sd-card-interface/
Features to achieve integrity:
Reproducable development environment
Let’s use corebooted Zerocat laptops in conjunction with hardware write protected firmware and GNU Guix System, which does not require any binaries to get started.
Due to GNU Guix System’s ability to travel in time, the development environment will be reproducable now and in future. Design results are expected to be bit-identical across different hosts of the same machine type.
Reduced complexity
Reduced complexity is crucial, as otherwise audits and maintenance will eventually fail, and the community would be disencouraged.
Simplicity avoids requirements of proprietary bridges
Complex interfaces and protocols like USB or VoIP go beyond the capabilities of a simple free-design controller. These protocols would require the use of powerful yet proprietary bridges, and are not an option if integrity comes first.
Free software, free firmware
Usage of free/open/libre licenses as recognized by the FSF will turn the device’s software into reusable building blocks, helping a world-wide community.
Free licensed hardware design files
Hardware design files will be freely available. They provide in depth details of the resulting hardware, and yield for reproducability and improvement across different, skilled manufacturers, independent from each other.
A dedicated CERN license makes the source repository travel with the physical hardware, e.g. the URL to the source repository must ship with the device.
Free documentation
The generated HTML documentation will be released under GNU FDL v1.2 or later.
Alternate PCB layout files, intended for CNC milling
In order to foster integrity, the hardware manufacturing process should be suitable for home-brewed manufacturing. Today, hobbyist’s CNC machines are powerful enough to create PCBs in a milling process. However, a PCB layout should take the limited capabilities of the process into account.
Processors of a free-design
Clocked chips, i.e. microcontrollers, are to be of a free design as well. These are required to process the data, and must be of elevated integrity. Best choice: Parallax’ P8X32A
LED display
As of today, VGA displays of a free design do not yet exist. As an alternative, let’s think about a LED-driven display, that can be managed by the P8X32A controller. Multipe seven-segment LEDs with dots are to be arranged line-wise to ease line editing of a text file, providing some context before and after the line under modification. Depending on complexity of the decoding wire network, up to five rows of 15 characters each might be driven.
Simple, inspectable, transparent keyboard module
The keyboard or keypad is supposed to be as simple as possible, it covers basic charsets only. This input device should be regarded suspectible for incognito hardware attacs, and should be an easily changeable or verifiable device or module.
Chipless input hardware
Furthermore, buttons, potentiometers might be used as input devices to ease navigation, scrolling, same as adjustment of loudness and sensitivity of the transmitter/receiver module.
Safe data storage on SPI flash or battery powered, static RAM
As of today, SPI flash chips and SD cards of a free design do not yet exist. These chips and cards are of great capacity (several Megabytes or Gigabytes), but of great complexity as well.
As an alternative, let’s think to use static RAM, battery powered. These are as well of a proprietary chip design, but of reduced complexity. Modules of sufficient capacity and endurance might eventually be accomplished by using again a P8X32A microcontroller in low-frequency mode.
Short/medium/long distance data transfer
Short distance file transfer
Medium distance file transfer
The device not only serves as a word processor, it might probably be used as a transmission repeater as well. Multiple devices might be used to set up a medium distance path of communication, repeating incoming data to a next, nearby located neighbour device, thus passing from balcony to balcony, along streets, for example.
Long distance file transfer
Inspectable, unfoldable chassis with transparent keyboard
The case or chassis must be easily inspectable. Unwanted add-ons like trackers or spying modules should be recognizable at first glance, intuitively, on a daily basis.
It would probably be too difficult to seal the keyboard module. Instead, it should be inspectable and transparent as much as possible. Furthermore, it should be easy to dismantel and reassemble the keyboard in oder to ease in depth examination.
Cryptography
Data and text files are to be encrypted before leaving the device, and decrypted after read from storage module or receiver. Strong cryptography, open to cryptoanalysis and FOSS implementation of ciphers is a must have, as otherwise the device will not be recognized, publically. Expertise has to be accumulated. Test attacks should be taken into account to prove reliability.
Enhanced password entry
Obfuscation is not targeted, but hardened password entries might be accomplished as part of a guess game.
https://en.wikipedia.org/wiki/Ultrasound
Occupational exposure to ultrasound in excess of 120 dB may lead to hearing loss. Exposure in excess of 155 dB may produce heating effects that are harmful to the human body, and it has been calculated that exposures above 180 dB may lead to death. The UK's independent Advisory Group on Non-ionising Radiation (AGNIR) produced a report in 2010, which was published by the UK Health Protection Agency (HPA). This report recommended an exposure limit for the general public to airborne ultrasound sound pressure levels (SPL) of 70 dB (at 20 kHz), and 100 dB (at 25 kHz and above).
Estimated time: 12 months
List of milestones: Quite elaborated, budgets per task are missing.
Estimated budget: EUR 49,850.-
Prototype #1: Made of plywood and color
Improve existing Chassis | 850.-
Power Module | 3,000.-
Mainboard | 3,000.-
Display | 3,500.-
Keyboard | 3,000.-
<Enter> keyArrange core system (Keyboard, Mainboard, Display, Power) | 1,000.-
Shell, Applications, Interfaces | 6,500.-
Add some applications, e.g.:
help browser, calculator, word processor, core utilities
like sort, cat, tac, basenc, ...
Support mainboard’s onboard communication bus
Prototype #2: Made of plywood and color | 4,500.-
Transmission Circuit Boards | 8,500.-
Set up transmission via Light Beam
Set up transmission via Sound
Refine circuits and drivers, as required
Refine Applications | 4,500.-
Transformation towards Final Products | 10,500.-
Finalize Documentation | 1,000.-
Estimated time: 12 months
List of milestones: To be refined.
Estimated budget: Not yet calculated.
Preparation for Cryptography
Implement strong Cryptography
Test Cryptography
Update Prototype Products
Finalize Documentation
¹ Respect Your Freedom certification program of the Free Software Foundation (FSF), USA
This project’s proposal...
should be written in English
Ok.
should be in line with the NGI vision
„An internet of human values. Resilient. Trustworthy. Sustainable.”
These keywords are targeted very well.
should have research and development as their primary objective
„Research and Development”
„A greener, more secure and resilient global Internet.”
„We want a more resilient, trustworthy and open internet. We want to empower end-users. Given the speed at which the 'twin transition' is taking place, we need a greener internet and more sustainable services sooner rather than later. Neither will happen at global scale without protocol evolution, which — as the case of three decades of IPv6 introduction demonstrates — is extremely challenging. NGI0 Core is designed to push beyond the status quo and create a virtuous cycle of innovation through free and open source software, libre hardware and open standards. If we want everyone to use and benefit from the internet to its full potential without holding back, the internet must be built on strong and transparent technologies that allow for permissionless innovation and are equally accessible to all.”
Keywords are:
Topic
„We are looking for troubleshooters that help society tackle the ossification of the internet and other hard but very very important challenges, each of which has significant social and economic consequences. We need new ideas and disruptive core technologies, while at the same time evolving and growing existing technologies that are still enough future-proof. The project results become available under an open source license, so anyone can read and validate the source code, and anyone can use the code to create technology that fits their own purposes. The right to reuse and right to repair not only allow for unrestricted scrutiny and permissionless innovation, but also help to reduce e-waste. And the use of standards enables interoperability and redundancy in implementation to reduce the risk of compromise and failure.”
„We are seeking project proposals between 5.000 and 50.000 euro's — with the possibility to scale them up if there is proven potential. Reliability, confidentiality, integrity, security, and resource efficiency should be the 'new normal' of the internet, something ordinary users should not have to worry about — users should be in control. So let's make it happen.”
Keywords:
Webpage: https://nlnet.nl/core/eligibility/index.html
„Trustworthiness and data sovereignty”
„We need a more resilient, trustworthy and open internet, empowering the end-users. Trust is only justified and sustainable if it the technology in question is up for the job, and is secure-by-design as well as trustworthy. Much of the software, services and devices does not measure up, and it is quite unlikely this will just improve by itself. NGI0 Entrust is designed to move beyond the status quo and create a virtuous cycle of innovation through free and open source software, libre hardware and open standards. If we want everyone to use and benefit from the internet to its full potential without holding back, the internet must be built on strong and transparent technologies that allow for permissionless innovation and are equally accessible to all.”
Keyword are:
Topic
„We are seeking project proposals between 5.000 and 50.000 euro's — with the possibility to scale them up if there is proven potential. Reliability, confidentiality, integrity, security and data portability should be the 'new normal' of the internet, something ordinary users should not have to worry about — users should be in control. So let's make it happen.”
„Among others we are looking to deliver "architectures, protocols and services to ensure that end-users can exert their rights (e.g. under the GDPR) and benefit from decentralised technological solutions that ensure that they are fully in control of their personal data on the Internet." We assist independent researchers and developers to create powerful new technologies, and to help them put it in the hands of future generations as building blocks for a fair and democratic society and a sustainable and open economy that benefits all.”
Keyword are:
Webpage: https://nlnet.nl/entrust/eligibility/
This project will cover some important types of activities. As a result, it should indeed be eligible for financial support by NGI0 Entrust and/or NGI0 Core:
design and development of open source software and open hardware
Zerocat Mini Machine is a new device, developed from scratch. Hardware and software will both be of a free-design.
It is important to point out that Zerocat Mini Machine is meant to be a stand-alone device, not requiring the internet for encrypted morse code data transmission. Instead, its transmission modules support alternative channels like audio, light, and radio (hopefully). However, interaction with devices such like desktops, laptops or phones is still achievable, offering standard transmission paths over internet via email, chat or phone call.
validation or constructive inquiry into existing or novel technical solutions
Technical solutions that will receive constructive inquiry:
Mobile power supply on DIY basis, probably using hand-kranked generators
Transparent DIY keyboard, driven by free-design controller
LED7 display (up to 5 lines, 15 characters each), driven by free-design controller
Data transmission, in parallel to internet:
Encryption techniques on DIY hardware, using free-design chips only.
documentation for researchers, developers and end users
The device, its modules, its recomended usage – all will be documented in detail, thus addressing professionals same as end-users.
understanding user requirements and improving usability/inclusive design
This is crucial. Zerocat Mini Machine comes with a new concept of chassis, which is meant to support intuitive, daily inspections by the end-user. However, usability has to be maintained and elaborated during experimental demonstrations and workshops. Users’ feedback will be regarded as a precious resource to refine the modular, foldable chassis.
necessary measures in support of (broad)er deployability, e.g. packaging
Zerocat Mini Machine will be a different, uncommon type of device that aims to be attractive in its apearance and package to gain acceptance. The device might be designed and shipped in the style of a fashion accessoire, probably targeting the female audience at first place.
other activities that are relevant to adhering to robust software development and deployment practices
This project involves outdoor transmission tests, held with various test groups like non-technical users, activists, journalists, amateur radio operators.
Chassis, folded
Chassis, set up for operation
Chassis, unfolded to ease user’s inspection.
Start animation:
View 00
View 01
View 02
Concatenate wooden units.
Inject nails, link units using small stripes of metal.
Cut stripes of plywood.
Add a nice angle.
Glue them onto wooden units.
Test whether the chassis folds together, smoothly.
Cut out some triangles.
Collect former snippets...
...and create small, triangular noses.
Glue noses onto wood units.
Make sure that positive and negative shape will fit together, perfectly.
Apply screws to enforce glued connection.
Prepare PCBs for assemblage.
Bent a wire to get the chassis stand.
Add PCBs and stand, refine tiny cutouts to make the units slip into well defined positions.
Mount handle support, insert raw wire and trim length, ...
...then bent both ends.
Fold chassis, pull out handle.
View 03
View 04
View 05
View 06
View 07
Drill Template and Micro Switch Landing Patterns
+-----+ +-----+ +-----+ +-----+ +-----+ +-----+ +-----+ +-----+ +-----+ +-----+
| ! | | " | | ? | | $ | | * | | & | | / | | ( | | ) | | = |
| 1 | | 2 | | 3 | | 4 | | 5 | | 6 | | 7 | | 8 | | 9 | | 0 |
+-----+ +-----+ +-----+ +-----+ +-----+ +-----+ +-----+ +-----+ +-----+ +-----+
+-----+ +-----+ +-----+ +-----+ +-----+ +-----+ +-----+ +-----+ +-----+ +-----+
| ' | | | | É | | | | | | | | Ü | | INS | | Ö | | + |
| Q | | W | | E | | R | | T | | Z | | U | | I | | O | | P |
+-----+ +-----+ +-----+ +-----+ +-----+ +-----+ +-----+ +-----+ +-----+ +-----+
+-----+ +-----+ +-----+ +-----+ +-----+ +-----+ +-----+ +-----+ +-----+
| Ä | | | | | | | | | | - | | ; | | : | | _ |
| A | | S | | D | | F | | G | | H | | J | | K | | L |
+-----+ +-----+ +-----+ +-----+ +-----+ +-----+ +-----+ +-----+ +-----+
+-----+ +-----+ +-----+ +-----+ +-----+ +-----+ +-----+ +-----+ +-----+
| | | \ | | | | @ | | | | BSP | | , | | . | | |
|Shift| | Y | | X | | C | | V | | B | | N | | M | |Enter|
+-----+ +-----+ +-----+ +-----+ +-----+ +-----+ +-----+ +-----+ +-----+
+-----+ +-----+ +-----+ +-----+
| DEL| | POS1| | UP | | END |
|Space| | <-- | | DWN | | --> |
+-----+ +-----+ +-----+ +-----+
INS = Insert
DEL = Delete
POS1 = First Position of Line
END = Last Position of Line
BSP = Backspace
UP = Upwards
DWN = Downwards
Shift = Upper Group
Enter = Finalize input. This is key #42, which is missing on prototype keyboard.
Notice: Key #42, <Enter>, is missing on prototype images. It should
be easy to add this key later on, during an update cycle.
Get some screws.
Use a lathe for the making of key caps.
Cut off cap with metal saw.
Collect 41 key caps.
Clean up caps’ backside to match exact thickness.
Arrange caps nicely, inspired by old ThinkPad keyboard.
Cutout an acrylic glass to create a cage.
Print the drill template onto paper.
Drill a first, small diameter according to drill template.
Enlarge diameters, step by step.
Bring the holes to their final diameter, preserving beveled edges.
Test the cage, check whether caps slip in easily.
Prepare for correct size of the PCB.
Cut out the PCB, using a saw.
Grind edges to make it look nice.
Match PCB and Cage and Drill Template, then drill main mounting holes.
Mount PCB and Cage together, then drill PCB mounting holes.
Clean up, refine PCB mounting holes to match sinking screw heads.
Mark landing patterns onto the PCB, using a high speed drill.
Isolate landing patterns manually from rest of PCB surface.
Remove dust, get prepared to solder micro switches into place.
Solder the switches.
PCB fully populated (using different type of switches, but same height).
Populate the cage with all key caps and screws, fix them with tape, flip the cage upside down.
Mount the PCB to the Cage.
Trim the length of mounting screws.
Drill main mounting holes into wood unit.
Mount the keyboard to the wooden chassis.
View 08
View 09
View 10
View 11
View 12
One Row of Display (15 Characters)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _
|_| |_| |_| |_| |_| |_| |_| |_| |_| |_| |_| |_| |_| |_| |_|
|_|.|_|.|_|.|_|.|_|.|_|.|_|.|_|.|_|.|_|.|_|.|_|.|_|.|_|.|_|.
1 2 3 4 5 6 7 8 9 0
_ _ _ _ _ _ _ _
| _| _| |_| |_ |_ | |_| |_| | |
| |_ _| | _| |_| | |_| _| |_|
A B C D E F G H I J
_ _ _ _ _
|_| |_ | _| |_ |_ | |_| | |
| | |_| |_ |_| |_ | |_| | | | _|
K L M N O P Q R S T
_ _ _ _
|_ | | | _ _ |_| |_| _ |_ |
|_ |_ | | | | |_| | | | _| |
U V W X Y Z Ä Ü Ö É
_ _ _ _
| | | | |_| _ |_| _ |_| | | _ |_
|_| _ _ | | _| _ | |. |_|. |_|. |_ .
' " + - * / = ( ) \
_ _ _
| | | _| _ _ _ | |_
| _ . _ . _ |_ |
? ! , . ; : _ @ & $
_ _ _
_| | _ _ _| | |_
| . . | . |. |. _ |_| _|. _|.
HELLO, WORLD.
_
|_| |_ | | _ _ |_| _ _ | _|
| | |_ |_ |_ |_| | _ |_| | |_ |_| .
"HELLO, WORLD!"
_ _ _
| | |_| |_ | | _ _ |_| _ _ | _| | | |
| | |_ |_ |_ |_| | _ |_| | |_ |_| .
MORSE CODE
_ _ _ _
| | _ _ |_ |_ | _ _| |_
| | |_| | _| |_ |_ |_| |_| |_
PARIS
_ _
|_| |_| _ | |_
| | | | | _|
CODEX
_ _ _
| _ _| |_ _
|_ |_| |_| |_ | |
TEST@TESTMAIL.COM
_ _ _ _ _ _ _ _ _ _ _
| |_ |_ | _| | |_ |_ | | | |_| | | | _ | |
| |_ _| | |_| | |_ _| | | | | | | |_ .|_ |_| | |
5*(9/3+2)-1=24
_ _ _ _ _ _
|_ |_| _ _| _| _| | _ | _ _| |_|
_| _ .|_ _| _ . _| | |_ | _ |_ |
Pi=3.141592654
_ _ _ _ _ _ _
|_| | _ _| | |_| | |_ |_| _| |_ |_ |_|
| | _ _| . | | | _| _| |_ |_| _| |
Zerocat Mini Machine
_ _ _ _ _ _ _ _ _ _
_ |_ _ _ | |_| | | | | _ | | | |_| | |_| | _ |_
_ |_ | |_| |_ | | | | | | | | | | | | | |_ | | | | | |_
This module covers two transmission paths, light beam and audio.
Transmission via light beam will require lenses, LED and photo diode driving circuits, additional power considerations, and extra mechanical constructions to protect the beam from direct sunlight. Distances greater than 1km have been managed with stationary equipment, see RONJA project – the distance that a mobile, battery driven device can handle has to be elaborated. It is estimated to 100m.
Transmission via audio will require to integrate speakers, microphones, driving circuits, and probably expertise in analog electronics. The usage of Morse code will hopefully allow to reliably grab signals out of a mix with environmental audio or speech. The managable distance is estimated to 50m.
View 13
View 14
View 15
View 16
Circuits, build from scratch.
The hardware consists of five modules, concatenated with each-other. Some modules ship their own controller, some don’t. If a controller is required, a Parallax P8X32A free-design microcontroller is the one that is used. This controller offers reduced complexity in comparison to RISC-V, which is not available as a free-design chip anyway, and Low RISC, which is still more complex and requires to be run on proprietary FPGAs.
Each module controller ships its own on-chip, free-design RAM, which holds the firmware and must be kept powered by means of a small coin battery. The firmware upload process should be managed by the core module in a secure, password protected manner. An I²C EEPROM of proprietary design might be used for powerless firmware backup, optionally. Chips of a proprietary design, such as inverters, gates, buffers and level shifters, will only be used for low level glue logic.
Module 1: Keyboard
Number of P8X32A chips: none
Module 2: Mainboard
Number of P8X32A chips: 2
Module 3: Display
Number of P8X32A chips: none
Module 4: Transmission
Number of P8X32A chips: 1
Module 5: Power
Number of P8X32A chips: none
+--------------------------------------+
| Power Module |
| |
| P8X32A chips: none |
| |
| managed array of gold-caps, | |
//====| batteries, incoming DC current, |<<=====| DC Input
|| | supplying all modules, | |
|| | buffering free-design RAM |
|| +--------------------------------------+
||
||
|| +--------------------------------------+ | firmware upload
|| | Core Module | |<····················| by corebooted
|| | | RS232 | | laptop
|| | P8X32A chips: 2 | |<········
|| | ········| ·
++==>>| keyboard driver, | ·
|| | word processor, key management, | ·
|| | password entry, encryption routines, | · | communication
|| | interface management, display driver | ·······>| machine to machine
|| | | | and machine to host
|| |············· pin usage ··············|
|| | SPI | Kbd | LED7 | DIPSW | InterCog |
|| +--------------------------------------+
|| ^ ^ ^ ^
|| | | | · | manual runtime
|| | | | ························| configuration, i.e.:
|| | |16 |10 | interactive or repeater mode
|| | / /
|| | | |
|| | | | +--------------------------------+
|| | | \------| Display Module |
|| | | | |
|| | | | P8X32A chips: none |
|| | | | |
++=======|=====|===power===>>| managed array of |
|| | | | line-oriented 7-segment LEDs |
|| | | +--------------------------------+
|| | |
|| | | +--------------------------------+
|| | \-------------| Keyboard Module |
|| | | |
|| | | P8X32A chips: none |
|| | | |
++=======|=========power===>>| managed array of keys, |
|| | | buttons, potis, switches |
|| | +--------------------------------+
|| |
|| | +--------------------------------+ | firmware upload
|| +-------- SPI------>| Transmission Module | RS232 |<········| by corebooted
|| | | sound and light beam ········| | laptop
|| | | |
|| | | P8X32A chips: 1 |
|| | | |
++=======|=========power===>>| loudspeaker, microphones, |
|| | | kill-switch, potis, buttons, |
|| | | lenses, LEDs, photo diodes |
|| | +--------------------------------+
|| |
|| |
|| | | direct access to:
|| +---------SPI------>| SPI flash chip or
|| | | SD-Card in SPI Mode
|| | | or buffered SRAM Module
|| |
:: :
:: :
|| | +--------------------------------+ | firmware upload
|| +-------- SPI------>| Experimental Module | RS232 |<········| by corebooted
|| | | ········| | laptop
|| | | P8X32A chips: ? |
|| | | |
++=======|=========power===>>| ... |
|| | | |
|| | +--------------------------------+
|| |
:: :
:: :
:: :
Module 5(5), Page 1(1)
Module 4(5), Page 1(1)
Module 3(5), Page 1(1)
Module 2(5), Page 1(2)
Module 2(5), Page 2(2)
Module 1(5), Page 1(1)
Unknown helicopter, slowly scanning Berlin on a sunday morning
Video Title: “CIA vs. Wikileaks – Andy”
Video URL: https://media.ccc.de/v/rc3-11512-cia_vs_wikileaks
Recorded by: C3VOC and FEM
License: CC BY 4.0
Video “CIA vs. Wikileaks – Andy”, cited at 00m11s
Video “CIA vs. Wikileaks – Andy”, cited at 22m54s
Video “CIA vs. Wikileaks – Andy”, cited at 23m04s
Video “CIA vs. Wikileaks – Andy”, cited at 23m34s
Video “CIA vs. Wikileaks – Andy”, cited at 24m14s
Video “CIA vs. Wikileaks – Andy”, cited at 24m24s
Video “CIA vs. Wikileaks – Andy”, cited at 24m34s
Video “CIA vs. Wikileaks – Andy”, cited at 58m24s
Video “CIA vs. Wikileaks – Andy”, cited at 58m35s
Image 1: Use wooden prototype as template
Image 2: Perform cutout.
Image 3: Glue pieces together
Image 4: Note measures to learn about shrinking later on
Image 5: First heat applied, no cracks! Shrinking factor: 1.0297
Version 1.3, 3 November 2008
Copyright (C) 2000, 2001, 2002, 2007, 2008 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.
The purpose of this License is to make a manual, textbook, or other functional and useful document "free" in the sense of freedom: to assure everyone the effective freedom to copy and redistribute it, with or without modifying it, either commercially or noncommercially. Secondarily, this License preserves for the author and publisher a way to get credit for their work, while not being considered responsible for modifications made by others.
This License is a kind of "copyleft", which means that derivative works of the document must themselves be free in the same sense. It complements the GNU General Public License, which is a copyleft license designed for free software.
We have designed this License in order to use it for manuals for free software, because free software needs free documentation: a free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless of subject matter or whether it is published as a printed book. We recommend this License principally for works whose purpose is instruction or reference.
This License applies to any manual or other work, in any medium, that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License. Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under the conditions stated herein. The "Document", below, refers to any such manual or work. Any member of the public is a licensee, and is addressed as "you". You accept the license if you copy, modify or distribute the work in a way requiring permission under copyright law.
A "Modified Version" of the Document means any work containing the Document or a portion of it, either copied verbatim, or with modifications and/or translated into another language.
A "Secondary Section" is a named appendix or a front-matter section of the Document that deals exclusively with the relationship of the publishers or authors of the Document to the Document's overall subject (or to related matters) and contains nothing that could fall directly within that overall subject. (Thus, if the Document is in part a textbook of mathematics, a Secondary Section may not explain any mathematics.) The relationship could be a matter of historical connection with the subject or with related matters, or of legal, commercial, philosophical, ethical or political position regarding them.
The "Invariant Sections" are certain Secondary Sections whose titles are designated, as being those of Invariant Sections, in the notice that says that the Document is released under this License. If a section does not fit the above definition of Secondary then it is not allowed to be designated as Invariant. The Document may contain zero Invariant Sections. If the Document does not identify any Invariant Sections then there are none.
The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says that the Document is released under this License. A Front-Cover Text may be at most 5 words, and a Back-Cover Text may be at most 25 words.
A "Transparent" copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable for revising the document straightforwardly with generic text editors or (for images composed of pixels) generic paint programs or (for drawings) some widely available drawing editor, and that is suitable for input to text formatters or for automatic translation to a variety of formats suitable for input to text formatters. A copy made in an otherwise Transparent file format whose markup, or absence of markup, has been arranged to thwart or discourage subsequent modification by readers is not Transparent. An image format is not Transparent if used for any substantial amount of text. A copy that is not "Transparent" is called "Opaque".
Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, SGML or XML using a publicly available DTD, and standard-conforming simple HTML, PostScript or PDF designed for human modification. Examples of transparent image formats include PNG, XCF and JPG. Opaque formats include proprietary formats that can be read and edited only by proprietary word processors, SGML or XML for which the DTD and/or processing tools are not generally available, and the machine-generated HTML, PostScript or PDF produced by some word processors for output purposes only.
The "Title Page" means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the material this License requires to appear in the title page. For works in formats which do not have any title page as such, "Title Page" means the text near the most prominent appearance of the work's title, preceding the beginning of the body of the text.
The "publisher" means any person or entity that distributes copies of the Document to the public.
A section "Entitled XYZ" means a named subunit of the Document whose title either is precisely XYZ or contains XYZ in parentheses following text that translates XYZ in another language. (Here XYZ stands for a specific section name mentioned below, such as "Acknowledgements", "Dedications", "Endorsements", or "History".) To "Preserve the Title" of such a section when you modify the Document means that it remains a section "Entitled XYZ" according to this definition.
The Document may include Warranty Disclaimers next to the notice which states that this License applies to the Document. These Warranty Disclaimers are considered to be included by reference in this License, but only as regards disclaiming warranties: any other implication that these Warranty Disclaimers may have is void and has no effect on the meaning of this License.
You may copy and distribute the Document in any medium, either commercially or noncommercially, provided that this License, the copyright notices, and the license notice saying this License applies to the Document are reproduced in all copies, and that you add no other conditions whatsoever to those of this License. You may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you distribute a large enough number of copies you must also follow the conditions in section 3.
You may also lend copies, under the same conditions stated above, and you may publicly display copies.
If you publish printed copies (or copies in media that commonly have printed covers) of the Document, numbering more than 100, and the Document's license notice requires Cover Texts, you must enclose the copies in covers that carry, clearly and legibly, all these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The front cover must present the full title with all words of the title equally prominent and visible. You may add other material on the covers in addition. Copying with changes limited to the covers, as long as they preserve the title of the Document and satisfy these conditions, can be treated as verbatim copying in other respects.
If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit reasonably) on the actual cover, and continue the rest onto adjacent pages.
If you publish or distribute Opaque copies of the Document numbering more than 100, you must either include a machine-readable Transparent copy along with each Opaque copy, or state in or with each Opaque copy a computer-network location from which the general network-using public has access to download using public-standard network protocols a complete Transparent copy of the Document, free of added material. If you use the latter option, you must take reasonably prudent steps, when you begin distribution of Opaque copies in quantity, to ensure that this Transparent copy will remain thus accessible at the stated location until at least one year after the last time you distribute an Opaque copy (directly or through your agents or retailers) of that edition to the public.
It is requested, but not required, that you contact the authors of the Document well before redistributing any large number of copies, to give them a chance to provide you with an updated version of the Document.
You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you release the Modified Version under precisely this License, with the Modified Version filling the role of the Document, thus licensing distribution and modification of the Modified Version to whoever possesses a copy of it. In addition, you must do these things in the Modified Version:
If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no material copied from the Document, you may at your option designate some or all of these sections as invariant. To do this, add their titles to the list of Invariant Sections in the Modified Version's license notice. These titles must be distinct from any other section titles.
You may add a section Entitled "Endorsements", provided it contains nothing but endorsements of your Modified Version by various parties—for example, statements of peer review or that the text has been approved by an organization as the authoritative definition of a standard.
You may add a passage of up to five words as a Front-Cover Text, and a passage of up to 25 words as a Back-Cover Text, to the end of the list of Cover Texts in the Modified Version. Only one passage of Front-Cover Text and one of Back-Cover Text may be added by (or through arrangements made by) any one entity. If the Document already includes a cover text for the same cover, previously added by you or by arrangement made by the same entity you are acting on behalf of, you may not add another; but you may replace the old one, on explicit permission from the previous publisher that added the old one.
The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to assert or imply endorsement of any Modified Version.
You may combine the Document with other documents released under this License, under the terms defined in section 4 above for modified versions, provided that you include in the combination all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice, and that you preserve all their Warranty Disclaimers.
The combined work need only contain one copy of this License, and multiple identical Invariant Sections may be replaced with a single copy. If there are multiple Invariant Sections with the same name but different contents, make the title of each such section unique by adding at the end of it, in parentheses, the name of the original author or publisher of that section if known, or else a unique number. Make the same adjustment to the section titles in the list of Invariant Sections in the license notice of the combined work.
In the combination, you must combine any sections Entitled "History" in the various original documents, forming one section Entitled "History"; likewise combine any sections Entitled "Acknowledgements", and any sections Entitled "Dedications". You must delete all sections Entitled "Endorsements".
You may make a collection consisting of the Document and other documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the rules of this License for verbatim copying of each of the documents in all other respects.
You may extract a single document from such a collection, and distribute it individually under this License, provided you insert a copy of this License into the extracted document, and follow this License in all other respects regarding verbatim copying of that document.
A compilation of the Document or its derivatives with other separate and independent documents or works, in or on a volume of a storage or distribution medium, is called an "aggregate" if the copyright resulting from the compilation is not used to limit the legal rights of the compilation's users beyond what the individual works permit. When the Document is included in an aggregate, this License does not apply to the other works in the aggregate which are not themselves derivative works of the Document.
If the Cover Text requirement of section 3 is applicable to these copies of the Document, then if the Document is less than one half of the entire aggregate, the Document's Cover Texts may be placed on covers that bracket the Document within the aggregate, or the electronic equivalent of covers if the Document is in electronic form. Otherwise they must appear on printed covers that bracket the whole aggregate.
Translation is considered a kind of modification, so you may distribute translations of the Document under the terms of section 4. Replacing Invariant Sections with translations requires special permission from their copyright holders, but you may include translations of some or all Invariant Sections in addition to the original versions of these Invariant Sections. You may include a translation of this License, and all the license notices in the Document, and any Warranty Disclaimers, provided that you also include the original English version of this License and the original versions of those notices and disclaimers. In case of a disagreement between the translation and the original version of this License or a notice or disclaimer, the original version will prevail.
If a section in the Document is Entitled "Acknowledgements", "Dedications", or "History", the requirement (section 4) to Preserve its Title (section 1) will typically require changing the actual title.
You may not copy, modify, sublicense, or distribute the Document except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense, or distribute it is void, and will automatically terminate your rights under this License.
However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation.
Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice.
Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, receipt of a copy of some or all of the same material does not give you any rights to use it.
The Free Software Foundation may publish new, revised versions of the GNU Free Documentation 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. See http://www.gnu.org/copyleft/.
Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License "or any later version" applies to it, you have the option of following the terms and conditions either of that specified version or of any later version that has been published (not as a draft) by the Free Software Foundation. If the Document does not specify a version number of this License, you may choose any version ever published (not as a draft) by the Free Software Foundation. If the Document specifies that a proxy can decide which future versions of this License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Document.
"Massive Multiauthor Collaboration Site" (or "MMC Site") means any World Wide Web server that publishes copyrightable works and also provides prominent facilities for anybody to edit those works. A public wiki that anybody can edit is an example of such a server. A "Massive Multiauthor Collaboration" (or "MMC") contained in the site means any set of copyrightable works thus published on the MMC site.
"CC-BY-SA" means the Creative Commons Attribution-Share Alike 3.0 license published by Creative Commons Corporation, a not-for-profit corporation with a principal place of business in San Francisco, California, as well as future copyleft versions of that license published by that same organization.
"Incorporate" means to publish or republish a Document, in whole or in part, as part of another Document.
An MMC is "eligible for relicensing" if it is licensed under this License, and if all works that were first published under this License somewhere other than this MMC, and subsequently incorporated in whole or in part into the MMC, (1) had no cover texts or invariant sections, and (2) were thus incorporated prior to November 1, 2008.
The operator of an MMC Site may republish an MMC contained in the site under CC-BY-SA on the same site at any time before August 1, 2009, provided the MMC is eligible for relicensing.
To use this License in a document you have written, include a copy of the License in the document and put the following copyright and license notices just after the title page:
Copyright (C) YEAR YOUR NAME.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.3
or any later version published by the Free Software Foundation;
with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
A copy of the license is included in the section entitled "GNU
Free Documentation License".
If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, replace the "with … Texts." line with this:
with the Invariant Sections being LIST THEIR TITLES, with the
Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.
If you have Invariant Sections without Cover Texts, or some other combination of the three, merge those two alternatives to suit the situation.
If your document contains nontrivial examples of program code, we recommend releasing these examples in parallel under your choice of free software license, such as the GNU General Public License, to permit their use in free software.
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.
The GNU General Public License is a free, copyleft license for software and other kinds of works.
The licenses for most software and other practical works are designed to take away your freedom to share and change the works. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change all versions of a program--to make sure it remains free software for all its users. We, the Free Software Foundation, use the GNU General Public License for most of our software; it applies also to any other work released this way by its authors. You can apply it to your programs, too.
When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things.
To protect your rights, we need to prevent others from denying you these rights or asking you to surrender the rights. Therefore, you have certain responsibilities if you distribute copies of the software, or if you modify it: responsibilities to respect the freedom of others.
For example, if you distribute copies of such a program, whether gratis or for a fee, you must pass on to the recipients the same freedoms that you received. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.
Developers that use the GNU GPL protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License giving you legal permission to copy, distribute and/or modify it.
For the developers' and authors' protection, the GPL clearly explains that there is no warranty for this free software. For both users' and authors' sake, the GPL requires that modified versions be marked as changed, so that their problems will not be attributed erroneously to authors of previous versions.
Some devices are designed to deny users access to install or run modified versions of the software inside them, although the manufacturer can do so. This is fundamentally incompatible with the aim of protecting users' freedom to change the software. The systematic pattern of such abuse occurs in the area of products for individuals to use, which is precisely where it is most unacceptable. Therefore, we have designed this version of the GPL to prohibit the practice for those products. If such problems arise substantially in other domains, we stand ready to extend this provision to those domains in future versions of the GPL, as needed to protect the freedom of users.
Finally, every program is threatened constantly by software patents. States should not allow patents to restrict development and use of software on general-purpose computers, but in those that do, we wish to avoid the special danger that patents applied to a free program could make it effectively proprietary. To prevent this, the GPL assures that patents cannot be used to render the program non-free.
The precise terms and conditions for copying, distribution and modification follow.
"This License" refers to version 3 of the GNU General Public License.
"Copyright" also means copyright-like laws that apply to other kinds of works, such as semiconductor masks.
"The Program" refers to any copyrightable work licensed under this License. Each licensee is addressed as "you". "Licensees" and "recipients" may be individuals or organizations.
To "modify" a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy. The resulting work is called a "modified version" of the earlier work or a work "based on" the earlier work.
A "covered work" means either the unmodified Program or a work based on the Program.
To "propagate" a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well.
To "convey" a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying.
An interactive user interface displays "Appropriate Legal Notices" to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion.
The "source code" for a work means the preferred form of the work for making modifications to it. "Object code" means any non-source form of a work.
A "Standard Interface" means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language.
The "System Libraries" of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form. A "Major Component", in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it.
The "Corresponding Source" for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. However, it does not include the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work.
The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source.
The Corresponding Source for a work in source code form is that same work.
All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program. The output from running a covered work is covered by this License only if the output, given its content, constitutes a covered work. This License acknowledges your rights of fair use or other equivalent, as provided by copyright law.
You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this License in conveying all material for which you do not control copyright. Those thus making or running the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you.
Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section 10 makes it unnecessary.
No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures.
When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures.
You may convey verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program.
You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee.
You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions:
A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an "aggregate" if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate.
You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways:
A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work.
A "User Product" is either (1) a "consumer product", which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling. In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, "normally used" refers to a typical or common use of that class of product, regardless of the status of the particular user or of the way in which the particular user actually uses, or expects or is expected to use, the product. A product is a consumer product regardless of whether the product has substantial commercial, industrial or non-consumer uses, unless such uses represent the only significant mode of use of the product.
"Installation Information" for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source. The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made.
If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information. But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM).
The requirement to provide Installation Information does not include a requirement to continue to provide support service, warranty, or updates for a work that has been modified or installed by the recipient, or for the User Product in which it has been modified or installed. Access to a network may be denied when the modification itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network.
Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying.
"Additional permissions" are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law. If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License without regard to the additional permissions.
When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it. (Additional permissions may be written to require their own removal in certain cases when you modify the work.) You may place additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission.
Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms:
All other non-permissive additional terms are considered "further restrictions" within the meaning of section 10. If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying.
If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the additional terms that apply to those files, or a notice indicating where to find the applicable terms.
Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way.
You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights under this License (including any patent licenses granted under the third paragraph of section 11).
However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation.
Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice.
Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10.
You are not required to accept this License in order to receive or run a copy of the Program. Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance. However, nothing other than this License grants you permission to propagate or modify any covered work. These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so.
Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License. You are not responsible for enforcing compliance by third parties with this License.
An "entity transaction" is a transaction transferring control of an organization, or substantially all assets of one, or subdividing an organization, or merging organizations. If propagation of a covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or could give under the previous paragraph, plus a right to possession of the Corresponding Source of the work from the predecessor in interest, if the predecessor has it or can get it with reasonable efforts.
You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it.
A "contributor" is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. The work thus licensed is called the contributor's "contributor version".
A contributor's "essential patent claims" are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be infringed by some manner, permitted by this License, of making, using, or selling its contributor version, but do not include claims that would be infringed only as a consequence of further modification of the contributor version. For purposes of this definition, "control" includes the right to grant patent sublicenses in a manner consistent with the requirements of this License.
Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its contributor version.
In the following three paragraphs, a "patent license" is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a patent or covenant not to sue for patent infringement). To "grant" such a patent license to a party means to make such an agreement or commitment not to enforce a patent against the party.
If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available for anyone to copy, free of charge and under the terms of this License, through a publicly available network server or other readily accessible means, then you must either (1) cause the Corresponding Source to be so available, or (2) arrange to deprive yourself of the benefit of the patent license for this particular work, or (3) arrange, in a manner consistent with the requirements of this License, to extend the patent license to downstream recipients. "Knowingly relying" means you have actual knowledge that, but for the patent license, your conveying the covered work in a country, or your recipient's use of the covered work in a country, would infringe one or more identifiable patents in that country that you have reason to believe are valid.
If, pursuant to or in connection with a single transaction or arrangement, you convey, or propagate by procuring conveyance of, a covered work, and grant a patent license to some of the parties receiving the covered work authorizing them to use, propagate, modify or convey a specific copy of the covered work, then the patent license you grant is automatically extended to all recipients of the covered work and works based on it.
A patent license is "discriminatory" if it does not include within the scope of its coverage, prohibits the exercise of, or is conditioned on the non-exercise of one or more of the rights that are specifically granted under this License. You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing software, under which you make payment to the third party based on the extent of your activity of conveying the work, and under which the third party grants, to any of the parties who would receive the covered work from you, a discriminatory patent license (a) in connection with copies of the covered work conveyed by you (or copies made from those copies), or (b) primarily for and in connection with specific products or compilations that contain the covered work, unless you entered into that arrangement, or that patent license was granted, prior to 28 March 2007.
Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law.
If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not convey it at all. For example, if you agree to terms that obligate you to collect a royalty for further conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program.
Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU Affero General Public License into a single combined work, and to convey the resulting work. The terms of this License will continue to apply to the part which is the covered work, but the special requirements of the GNU Affero General Public License, section 13, concerning interaction through a network will apply to the combination as such.
The Free Software Foundation may publish revised and/or new versions of the GNU 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 Program specifies that a certain numbered version of the GNU General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of the GNU General Public License, you may choose any version ever published by the Free Software Foundation.
If the Program specifies that a proxy can decide which future versions of the GNU General Public License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Program.
Later license versions may give you additional or different permissions. However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version.
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee.
END OF TERMS AND CONDITIONS
If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
This program 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.
This program 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 this program. If not, see <http://www.gnu.org/licenses/>.
Also add information on how to contact you by electronic and paper mail.
If the program does terminal interaction, make it output a short notice like this when it starts in an interactive mode:
<program> Copyright (C) <year> <name of author>
This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
The hypothetical commands \show w' and \show c' should show the
appropriate parts of the General Public License. Of course, your
program's commands might be different; for a GUI interface, you would
use an "about box".
You should also get your employer (if you work as a programmer) or school, if any, to sign a "copyright disclaimer" for the program, if necessary. For more information on this, and how to apply and follow the GNU GPL, see http://www.gnu.org/licenses/.
The GNU General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. But first, please read http://www.gnu.org/philosophy/why-not-lgpl.html.