News for hackers. Stuff that matters.
Re:Announcing Caddy Commercial Licenses by diggan on Wednesday September 13, 2017 @10:45AM (#15238755)
Hm, I don't think so (but I'm no expert)

> The freedom to study how the program works, and change it so it does your computing as you wish (freedom 1). Access to the source code is a precondition for this.

Even with or without the above statement, this freedom is not broken by Caddy. You are still allowed to download the source and remove the headers, just as before.

Re:Announcing Caddy Commercial Licenses by Sir_Cmpwn on Wednesday September 13, 2017 @10:47AM (#15238773)
>its presence is required by the non-commercial EULA

This statement reads to me that you _cannot_ remove it.

It also combines with freedom 3, if you can't distribute your modified version.

Re:Announcing Caddy Commercial Licenses by mholt on Wednesday September 13, 2017 @10:50AM (#15238803)
The EULA does not apply to the source code. The source code is Apache licensed.
Re:Announcing Caddy Commercial Licenses by bpicolo on Wednesday September 13, 2017 @10:50AM (#15238800)
The EULA only applies to precompiled binaries
Re:Announcing Caddy Commercial Licenses by joepie91_ on Thursday September 14, 2017 @06:05AM (#15246415)
The binary build from the Caddy website and the GitHub repository are effectively two separate products, as they are covered by different licenses.

The code in the GitHub repository is open-source; but the binary builds from the Caddy website are not.