Users of the gnu general Public License have no need to worry about Sarbanes-Oxley.
Thats the upshot of a white paper published by the Software Freedom Law Center on March 8. The paper dismisses recent claims that the GPL violates the Sarbanes-Oxley Act.
The SFLCs white paper follows those from the legal department at embedded-systems seller Wasabi Systems. Wasabi has posted online a licensing guide with a section on how SarbOx “has changed the open-source landscape by making GPL violations a federal crime.”
Wasabi has also posted online a white paper, titled “When GPL Violations Are Sarbanes-Oxley Violations,” that says SarbOx requires public companies to provide truthful disclosures of information, including ownership of intellectual property.
While some have argued that corporate executives face increased risk of criminal liability under SarbOx if their companies develop and distribute GPL-licensed code, the latest white paper from the New York-based SFLC maintains that these issues were reviewed and that there is no special risk for developing such code under SarbOx.
“Under most circumstances, the risk posed to a company by SOX [Sarbanes-Oxley] is not affected by whether they use GPLd or any other type of software,” the paper says.
Eben Moglen, the centers chair, said the recent discussions regarding the GPL and SarbOx prompted the SFLC to issue its position on the topic.
Moglen said the white paper will help all GPL users to clearly understand “no criminal charges on the basis of violating SOX have ever been brought against a GPL user.”
The white paper also defines the realistic impact of a GPL violation as it could be applied under SarbOx, pointing out that the legislation generally applies only to public companies and that disclosure in a companys Securities and Exchange Commission reports is not necessary if its use of the license is immaterial to its business.
In addition, companies that must comply with SarbOx bear the full cost of compliance, regardless of the software licenses they choose, the white paper says. The paper also explains that if SarbOx applies to a GPL violation, it is not likely a company or developer would be criminally liable, since only intentional misconduct is liable for prosecution—an unlikely scenario for issues surrounding a well-established and broadly used license.
“The idea that a GPL violation could result in jail time is unreasonable,” Karen Sandler, an SFLC attorney, said in a prepared statement.
The Gpl and Sarbanes-Oxley
* SarbOx applies only to companies that file periodic reports with the SEC.
* If a companys reliance on a software license is not material, and it reasonably believes that harm from a license violation is not substantial, the company is not required to disclose the reliance in its periodic reports.
* Companies subject to SarbOx must bear the cost of full SarbOx compliance, whether or not they use “GPLd” software.
* The SarbOx provisions impose criminal liability on executives who “knowingly” or “willfully” falsify their companys certification for SarbOx compliance, whether the software is GPLd or not.