Re: Apple crypto engineer position available
On 4/14/98, Robert Hettinga blathered on like this:
...Hint 1: Whatsisname Sidhu,
who negotiated the world's first RSA license, and who probably could have invented digital commerce on the internet all by himself if he only knew what he had, already bought and paid for, wasted in a mail and LAN protocol, buried in the bowels of the MacOS...
...Anyway, a more clueful Sidhu, (who, to be fair, couldn't have understood what was coming) could have, with just a little of the right prompting :-), taken some of the money you guys gave to, say, Steve, for instance :-), and bought the blind signature patent at firesale prices from DigiCash ($10 million is chump change, even to Apple, even then, :-)) at last year's greater-fools exchange of ownership at "the world's greatest financial cryptography company" (my name, not theirs)....
Quite amazing to look at all of the innovation that went on at Apple and wonder what could have been. From my perspective, the big mistake with Apple's first implementation of crypto was that it was part of an architecture (yep, PowerTalk). After close encounters with this and other wonderfully "flexible architectures", I've learned (the hard way) that this is one of the best oxymorons in computerdom. Architectures seem like wonderful, grandiose ways to solve a bunch of problems at once, but they usually lead a Titanic-like existence, eventually sinking into the abyss and taking almost everything with it, including products, businesses, reputations - you name it. Well, an amazing thing happened. Just before PowerTalk started taking on serious water, someone managed to throw DigiSign (Apple's digital signature technology based on RSA public keys) into its own life boat; Apple actually built a separate library for DigiSign that didn't require PowerTalk. But, unfortunately, there was leak in this boat, too. You see, the model for DigiSign's certificates was based on a heirarchy and required a certificate authority and all of the requisite infrastructure. No one had really done this yet so Apple had to do more than create DigiSign and put it into the Mac OS - they had to get this infrastructure in place, too. Now, even though Apple had the help of RSA and BBN, there was this even bigger problem of just helping people get it. The best way to help people understand technology is to make it accessible so almost anyone can play with it and use it. This is what Apple is known for - making technology so accessible that people just go nuts, doing things with it and taking it places no one ever dreamed. That's how Apple catalyzed the transformation of the publishing industry. Requiring a CA to make DigiSign work simply made this impossible. A peer to peer model, allowing people to create and sign their own certificates would have been far more appropriate for Apple's creative users. Then came PGP... C 'est la vie! Mark ---- mark@altenberg.com
Now, even though Apple had the help of RSA and BBN, there was this even bigger problem of just helping people get it. The best way to help people understand technology is to make it accessible so almost anyone can play with it and use it. This is what Apple is known for - making technology so accessible that people just go nuts, doing things with it and taking it places no one ever dreamed. That's how Apple catalyzed the transformation of the publishing industry. Requiring a CA to make DigiSign work simply made this impossible. A peer to peer model, allowing people to create and sign their own certificates would have been far more appropriate for Apple's creative users. Then came PGP...
I think Mark makes a mistake in confusing pre-conditions for market acceptance with requirements for market growth.
From the perspective of someone who helped the Web grow from a userbase of less than 100 users I have my own ideas as to why Apple did not succeed with its powertalk architecture. I see the lack of commitment to open standards as the key factor.
Consider the attractiveness of a communications system that only communicates from one Mac to another. Today that might be just about adequate for many people's needs, after all the PowerMacs are quite powerful. Back in 1990 however the Mac platform was a rather weedy 68000 with an operating system that was very expensive to develop for and a relatively small market share. If you had a power hungry application in 1990 you had to get a RISC processor which in turn meant like it or not you had to use UNIX (or VMS). Standardising on a Mac only platform just was not going to happen regardless of how great the software was. To the extent that requiring a CA meant higher startup costs the powertalk architecture was flawed. The problem had always been a chicken and egg situation in which PKI applications could not take off without a CA and CAs could not take off without successful PKI applications. PGP cut the gordian knot and demonstrated that it was _possible_ to have a successful PKI application without a CA. But that is not to say that a trusted third party cannot add value to an application. PGP validated PKI generally but it did not invalidate the CA concept - in the PGP system everyone is a trust provider, everyone is in that sense a CA. But just because CAs may be dispensed with in a system of 10,000 odd users whose principal concern is confidentiality does not mean they have no role in a system of over 1 million users where the legal enforceability of a signed contrat is an issue. Consider as an example the case in which there are 1,000,000 users and people generally prefer certificate chains to be no longer than three people. That can only be achieved if either people on average sign 100 keys or some people sign a great number of keys (thousands). In my book anyone who is signing over 1000 keys had better have a pretty decent idea of what they are doing and should probably think of themselves as a CA. The other shortcomming of Apple's approach was not realising that there is a middle ground. To take an example most people think of VeriSign as a CA because of our public CA business (Server certificates, S/MIME certificates). A lot of people who spend a lot of energy blasting our business model don't realise that our enterprise offering, OnSite is a product which allows other people to set up their own CA outsourcing the expensive to implement Issuing Authority functions rather than handing over control of their enterprise to us. It is true that if folk want to issue certificates which are incorporated into the VeriSign public hierarchy we insist on certain contractual undertakings from them (i.e. if they issue a certificate to Fred Bloggs they take the same steps we would to check it really is Fred Bloggs). We have already got to the point where we have proved the viability of PKI generally. The question to ask is not what are the preconditions for establishing PKI but how can we grow the PKI market best? In short Apple's plans were not too crazy from the perspective of where they wanted to get. The fault lay in not understanding how the market could get from where it is to where they thought it should go. They failed to understand that communications products can only be successful as genuinely open standards with ubiquitous support. They saw the Powertalk architecture as a means to sell more Macs, not as a business in itself. Phill
At 1:06 PM -0700 4/15/98, Phillip Hallam-Baker wrote:
Now, even though Apple had the help of RSA and BBN, there was this even bigger problem of just helping people get it. The best way to help people understand technology is to make it accessible so almost anyone can play with it and use it. This is what Apple is known for - making technology so accessible that people just go nuts, doing things with it and taking it places no one ever dreamed. That's how Apple catalyzed the transformation of the publishing industry. Requiring a CA to make DigiSign work simply made this impossible. A peer to peer model, allowing people to create and sign their own certificates would have been far more appropriate for Apple's creative users. Then came PGP...
I think Mark makes a mistake in confusing pre-conditions for market acceptance with requirements for market growth.
From the perspective of someone who helped the Web grow from a userbase of less than 100 users I have my own ideas as to why Apple did not succeed with its powertalk architecture. I see the lack of commitment to open standards as the key factor. ... But just because CAs may be dispensed with in a system of 10,000 odd users whose principal concern is confidentiality does not mean they have no role in a system of over 1 million users where the legal enforceability of a signed contrat is an issue. ... The other shortcomming of Apple's approach was not realising that there is a middle ground. To take an example most people...
Lack of commitment to open standards was made obvious by the fact that Apple considered the POP/SMTP plug-in for PowerTalk to be a 3rd party opportunity! However, I was only really talking about the DigiSign stuff, trying not to get sucked into the whole enchalada of discussing why PowerTalk failed. I have no bone to pick with the CA model. Apple was stuck at the high end of this model when, as Phill points out, many levels of authentication are needed. I simply think that starting with a personal model, more like PGP, would have allowed DigiSign to build some momentum, at least in the Mac market (not a bad place to start). So, it was in fact a pre-condition for market acceptance. Market growth could have been accelerated by just paying attention. As with many Apple technologies, there was never a version 2.0 and 3.0 and so on, to correct for the misconceptions about the market. A lot of people knew what needed to be done, but management usually remained clueless. Mark
participants (2)
-
Mark Altenberg
-
Phillip Hallam-Baker