>You just arrange for the script to detect whether a private key is
>present. If none exists, it asks the user whether they want to generate
>a private key, and then calls gpg with the relevant options to do so.
>
>The private key isn't part of the script, nor is it a requirement to
>be able to (successfully) run the script.
>
>Note that the GPL does not say whether the output from the installation
>script has to be usable with the target hardware.
>
>
>
>On Thu, Apr 24, 2003 at 10:57:21AM +0200, Arjan van de Ven wrote:
>
>
>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.
>
>
Wouldn't "control ... installation" include the keys too?
IANAL, but I am on the board of an NPO that advocates Free and Open
Source Software, and that NPO has a lawyer (who is VERY familiar with
the GPL). Would it make sense to ask him? After all, that merely means
what one lawyer would say.
-- Shachar Shemesh Open Source integration consultant Home page & resume - http://www.shemesh.biz/
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/