Sept is not GPL 2 compliant, thus it is not open source:
The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable.
There is no means to actually compile *and* install sept because you do not include the signing key (or even offer to sign people's builds), thus it is not GPL 2 compliant. Nor can modifications be made to sept.
https://www.gnu.org/licenses/old-licenses/gpl-2.0.en.html
Actually, all scripts required to compile sept are concluded. A user may compile and generate the same plaintext binary that I do (with same compiler config), and modify it to their heart's content. Scripts are even included to generate .enc files, and users can build and modify to their heart's content.
This requirement of the GPL is actually why keys_template.py is included -- it satisfies the relevant requirement as build instructions are allowed to require copying/configuring for the user's build system.
The only thing they cannot do is run those builds on hardware, since they would be built with the wrong keys...however this is not a requirement of GPLv2.
Look into TiVo cases, sept is 100% in the clear.
Last edited by SciresM,