Skip to main content
Open Source

Return to Question

edited tags
Link
unor
unor
  • 5.7k
  • 26
  • 55
deleted 38 characters in body
Source Link
Mureinik
Mureinik
  • 5.2k
  • 3
  • 33
  • 42

I'm working on building a proprietary application that I would like to release as PGP-signed Debian packages.

I heard I might be forced to release the source to my proprietary application simply due to the fact that it would be signed by GnuPG, which is covered under GPLv3 containing the "Tivoization" clause.

Is this true? It is my understanding that the license for GnuPG would enforce disclosing any modifications to GnuPG itself, not the use of GnuPG to apply a signature to an arbitrary "object". Saying that the object I'm signing with GnuPG is now also open source makes no sense to me.

Can someone clarify?

Thank you!

I'm working on building a proprietary application that I would like to release as PGP-signed Debian packages.

I heard I might be forced to release the source to my proprietary application simply due to the fact that it would be signed by GnuPG, which is covered under GPLv3 containing the "Tivoization" clause.

Is this true? It is my understanding that the license for GnuPG would enforce disclosing any modifications to GnuPG itself, not the use of GnuPG to apply a signature to an arbitrary "object". Saying that the object I'm signing with GnuPG is now also open source makes no sense to me.

Can someone clarify?

Thank you!

I'm working on building a proprietary application that I would like to release as PGP-signed Debian packages.

I heard I might be forced to release the source to my proprietary application simply due to the fact that it would be signed by GnuPG, which is covered under GPLv3 containing the "Tivoization" clause.

Is this true? It is my understanding that the license for GnuPG would enforce disclosing any modifications to GnuPG itself, not the use of GnuPG to apply a signature to an arbitrary "object". Saying that the object I'm signing with GnuPG is now also open source makes no sense to me.

Source Link
berto
berto
  • 139
  • 2

Is GPLv3 violated by releasing proprietary code as a GnuPG-signed package?

I'm working on building a proprietary application that I would like to release as PGP-signed Debian packages.

I heard I might be forced to release the source to my proprietary application simply due to the fact that it would be signed by GnuPG, which is covered under GPLv3 containing the "Tivoization" clause.

Is this true? It is my understanding that the license for GnuPG would enforce disclosing any modifications to GnuPG itself, not the use of GnuPG to apply a signature to an arbitrary "object". Saying that the object I'm signing with GnuPG is now also open source makes no sense to me.

Can someone clarify?

Thank you!