Skip to content

Securebox ad hoc backups for web applications v3.0

Latest
Latest
Compare
Choose a tag to compare
@fititnt fititnt released this 19 Nov 04:33
· 14 commits to main since this release
v3.0
595d9a5

Technically speaking v3.0 should still be backward compatible with v2.0 and all documentation should still works. The main reason for this major version bump is.. license model.

  • New features
    • New auto detected web applications
      • Moodle LMS
      • Laravel based web applications
  • Bugfixes
    • securebox-backup-download -> mysqldump strategy now allow non-localhost MariaDB/MySQL servers on target remote servers

New dual licensing model

SPDX-License-Identifier: Unlicense OR 0BSD

Explanation

While the v2.0 and earlier versions already were dedicated to Public Domain, v3.0 is more explicitly the Unlicense https://unlicense.org. The securebox-ad-hoc-backups-for-web-applications is meant to be used without need to deploy copies of the license (the file headers already are OK), but seems that Dedicate only to public domain may not be sufficient. Then the SPDX-License-Identifier: Unlicense OR 0BSD is more explicitly about this.

Why 0BSD?

The reason to explicitly add Zero-Clause BSD License, as quoted from https://landley.net/toybox/license.html:

Zero clause BSD is a public domain equivalent license.

As with CC0, unlicense, and wtfpl, the intent is to effectively place the licensed material into the public domain, which after decades of FUD (such as the time OSI's ex-lawyer compared placing code into the public domain to abandoning trash by the side of a highway) is considered somehow unsafe. But if some random third party takes public domain code and slaps some other license on it, then it's fine.

To work around this perception, the above license is the OpenBSD suggested template license, minus the half sentence requiring the license text be copied verbatim into derived works. If 2BSD is ok, then 0BSD should be ok, despite being equivalent to placing code in the public domain.

Modifying the license in this way avoids the hole android toolbox fell into where 33 copies of BSD license text were concatenated together when copyright dates changed, or the strange solution the busybox developers used to resolve tension between GPLv2's "no additional restrictions" and BSD's "you must include this large hunk of text" by sticking the two licenses at opposite ends of the file and hoping nobody noticed.

Note: I asked Kirk McKusick for permission to call this a BSD license at a conference shortly before I started using the name, and again in 2018.

Assets 2
Loading