linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
To: Brian McGroarty <brian@mcgroarty.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: BK Licence: Protocols and Research
Date: Tue, 22 Jul 2003 21:23:16 +0100	[thread overview]
Message-ID: <20030722202316.GH3267@mail.jlokier.co.uk> (raw)
In-Reply-To: <20030722201517.GA25774@mcgroarty.net>

Brian McGroarty wrote:
> On Tue, Jul 22, 2003 at 05:56:15PM +0100, Jamie Lokier wrote:
> > Larry McVoy wrote:
> > > If you managed to stay close then we'd put digital signatures
> > > into the protocol to prevent your clone from interoperating with BK.
> > 
> > If this hypothetical scenario were to occur, I believe that reverse
> > engineering specific parts of the software, for the specific purpose
> > of getting the signature key, in order to use it specifically for
> > interoperating with the software, would be allowed regardless of
> > license here in Europe, and perhaps in the USA too.
> 
> Well off topic here, but in the US at least, the DMCA makes this
> hands-off if these features are added under the auspices of security
> or server license protection.

Yes, that's exactly what I had in mind when I said prison was one of
the dangers of making interoperable software.

-- Jamie

  reply	other threads:[~2003-07-22 20:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-17 12:05 Rory Browne
2003-07-17 12:15 ` Sean Neakums
2003-07-17 12:28 ` Alan Cox
2003-07-17 12:35 ` Jens Axboe
2003-07-17 13:39   ` Rory Browne
2003-07-17 14:09     ` Alan Cox
2003-07-17 14:58 ` Larry McVoy
2003-07-17 21:01   ` Rory Browne
2003-07-17 21:41     ` Mike Fedyk
2003-07-17 22:01     ` Larry McVoy
2003-07-18  3:01     ` jw schultz
2003-07-22 16:56   ` Jamie Lokier
2003-07-22 20:15     ` Brian McGroarty
2003-07-22 20:23       ` Jamie Lokier [this message]
2003-07-17 14:17 John Bradford

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030722202316.GH3267@mail.jlokier.co.uk \
    --to=jamie@shareable.org \
    --cc=brian@mcgroarty.net \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: BK Licence: Protocols and Research' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).