-
Notifications
You must be signed in to change notification settings - Fork 22
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Added OpenTofus Hashicorp Cease and Desist Response blogpost (#286)
Signed-off-by: James Humphries <james@james-humphries.co.uk>
- Loading branch information
Showing
3 changed files
with
36 additions
and
1 deletion.
There are no files selected for viewing
35 changes: 35 additions & 0 deletions
35
blog/2024-04-11-our-response-to-hashicorps-cease-and-desist.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,35 @@ | ||
--- | ||
title: Our Response to Hashicorp's Cease and Desist Letter | ||
slug: our-response-to-hashicorps-cease-and-desist | ||
image: /img/blog/cease-and-desist-response.png | ||
--- | ||
|
||
On April 3rd, we received a Cease and Desist letter from HashiCorp regarding our implementation of the "removed" block in OpenTofu, claiming copyright infringement on the part of one of our core developers. We were also made aware of an article posted that same day with the same accusations. We have investigated these claims and are publishing the C&D letter, our response and the source code origin document resulting from our investigation. | ||
|
||
**The OpenTofu team vehemently disagrees with any suggestion that it misappropriated, mis-sourced, or otherwise misused HashiCorp’s BSL code. All such statements have zero basis in facts.** | ||
|
||
HashiCorp has made claims of copyright infringement in a cease & desist letter. These claims are **completely unsubstantiated**. | ||
|
||
The code in question can be clearly shown to have been copied from older code under the MPL-2.0 license. HashiCorp seems to have copied the same code itself when they implemented their version of this feature. All of this is easily visible in our detailed SCO analysis, as well as their own comments which indicate this. | ||
|
||
## Documents | ||
|
||
- [HashiCorp's C&D Letter](https://opentofu.github.io/legal-documents/2024-04-03%20HashiCorp%20C%26D/OpenTofu%20C&D%20-%20Redacted.pdf) | ||
- [Our Response](https://opentofu.github.io/legal-documents/2024-04-03%20HashiCorp%20C%26D/OpenTofu%20C&D%20Response%20-%20Redacted.pdf) | ||
- Source Code Origin Document: [[HTML](https://opentofu.github.io/legal-documents/2024-04-03%20HashiCorp%20C%26D/SCO.html), [PDF](https://opentofu.github.io/legal-documents/2024-04-03%20HashiCorp%20C%26D/SCO.pdf)] **⇐ For the detailed code analysis, see here.** | ||
|
||
_To prevent further harassment of individual people, we have redacted any personal information from these documents._ | ||
|
||
## Conclusion | ||
|
||
Despite these events, we have managed to carry out significant development on OpenTofu 1.7, including state encryption, “for_each” implementation for “import” blocks, as well as the all-new **provider-defined functions** supported by the recently released provider plugin protocol. | ||
|
||
On that note, we will be releasing a new pre-release version next week, and we are eager to gather feedback from the community. | ||
|
||
— The OpenTofu Team | ||
|
||
--- | ||
|
||
<small> | ||
*The image in this blog post contains code licensed under the BUSL-1.1 by HashiCorp. However, for the purposes of this post we are making non-commercial, transformative fair use under [17 U.S. Code § 107](https://www.govinfo.gov/content/pkg/USCODE-2022-title17/html/USCODE-2022-title17-chap1-sec107.htm). <br /> You can read more about fair use on the [website of the US Copyright Office](https://www.copyright.gov/fair-use/).* | ||
</small> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.