On 03/16/11 12:24, Theo de Raadt wrote: >>> One word can change the meaning of a sentence. You failed at what you >>> intended, and you also confused people. >> >> You're the only person who has ever told me that the Tarsnap license is >> confusing. Maybe everybody else was confused but didn't want to admit it. > > It's not me. I am only joining a thread that other people started.
I must have misunderstood what other people were saying. I thought the earlier complaints were just that Tarsnap's license is not open source and that (according to some people at least) openbsd's ports tree shouldn't contain non-open-source code. >> In any case, I'm happy to change the license text to make it clearer; how >> do you think "here's some code for you to use to access the Tarsnap service; >> that's the only thing you're allowed to use it for" should be phrased? > > Hey, that text there sounds fine to me. That's your own risk (if there is > any risk; let's be realistic, much of the time that is overblown). > > But please just make sure it doesn't look like a BSD licence, and fool > anyone. I understand that was never your intent. Do you think that applying Unless specified otherwise in individual files, the contents of this -package is covered by the following copyright, license, and disclaimer: +package is covered by the following copyright, license, and disclaimer +(please note that this is not an "open source" license): Copyright 2006, 2007, 2008, 2009, 2010, 2011 Colin Percival All rights reserved. to the COPYING file would make this clear? -- Colin Percival Security Officer, FreeBSD | freebsd.org | The power to serve Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid
