> The point is that in Netscape, it is very hard to tell if a given link > is 40 bit or 128 bit. Sure, with enough poking around looking at page > info you could probably figure it out. Or maybe someone knows if the > little padlock means something like the little key used to. But I'm a > crypto-sophisticated person, and I don't know. What about people who > don't understand the technology at all? Good point 1. when evaluating, never underestimate the lure of convenience 2. Paul Kocher has found, as I recall, that the percentage of browsers that are 40bit is *growing* because of the inconvenience and invasiveness of what extra effort it takes to get your hands on the 128bit stuff. 3. having inertia & ignorance on your side is strongly advantageous --dan
- write code outside US (Re: so why is IETF ... Adam Back
- Re: write code outside US (Re: so why ... Tom Weinstein
- Re: write code outside US (Re: so why ... Sameer Parekh
- Re: so why is IETF stilling adding DES to ... Eivind Eklund
- Re: so why is IETF stilling adding DES to ... Bodo Moeller
- Re: so why is IETF stilling adding DES to ... Ulf Möller
- Re: so why is IETF stilling adding DES... John Gilmore
- Re: so why is IETF stilling addin... Nelson Minar
- Padlock Size was Re: so why i... Steve Mynott
- Re: Padlock Size was Re: so w... Tom Weinstein
- Re: so why is IETF stilling a... Dan Geer
- Re: so why is IETF stilling adding DES... Adam Shostack
- Re: so why is IETF stilling adding DES to protocols? (R... Adam Back
- RE: so why is IETF stilling adding DES to protocol... Phill Hallam-Baker
- Re: so why is IETF stilling adding DES to prot... Bodo Moeller