full-disclosure - RE: [ISN] How To Save The Internet

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <75C025AE395F374B81F6416B1D4BDEFB01C3C781@mtv-corpmail.microfocus.com>
From: Michael.Wojcik at microfocus.com (Michael Wojcik)
Subject: RE: [ISN] How To Save The Internet

> From: Arndt.WA@...ces.gc.ca [mailto:Arndt.WA@...ces.gc.ca] 
> Sent: Wednesday, 23 March, 2005 11:24
> 
> Jason Coombs wrote:
> > 
> > David Gillett wrote:
> > > are the various rights of the owner
> > > of the CPU, the *operator* of the
> > > CPU, and the owner of the *data*,
> > > each of whom may have a more or
> > > less legitimate say in what code
> > > actually gets executed.
> > 
> > Nonsense. Absurd, ridiculous nonsense.
> > 
> > There is only one party who has any say over what code gets 
> > executed by a CPU: the owner of that physical property.
> 
> Hold on. If you're dealing with a large company or government
> department, who "physically owns" the computer in question,
> you can't tell me that they're going to micromanage exactly
> what goes on with that system. They'll delegate the authority
> off to someone who'll actually run the equipment.

And CPU owners frequently transfer, by contract, some or all of their
(purported) right over the code executed by that CPU to others.  Service
bureaus often work that way.

Many CPUs are leased.  Does IBM have the sole right to determine what runs
on all of the mainframes it leases to customer?

There's some nonsense in this thread, all right, but it wasn't David's.

-- 
Michael Wojcik
Principal Software Systems Developer, Micro Focus