On 22/3/09 22:20, Anders Rundgren wrote:
Nelson B Bolyard wrote:
Solution: One solution would be to define signature support as a
browser component.
Especially the component you've invented and have been trying to get
Mozilla to adopt for some time, right? Anders?
At this stage it is enough considering (acknowledging) the 10M+ that already
use signature
plugins.
Hmm, where are those? I've seen an application begging for user-based
(client-cert) signing, and am interested, even if Mozilla isn't ;-)
Let's see a standard from W3C (or browser standards group de jour) first.
I believe we will have to wait a long time for that one.
Thank our lucky stars! I seriously doubt they could do it, and if they
did do it, we'd be on yet another disastrous track like S/MIME, the
failure that defies remedy. Which would suck up innocent volunteer
coders and block a useful solution from arising from the market. Awful.
The problem with this standards thing is that it works well when
standardising an existing working killer product ... but it does not
work at all if there is any confusion as to how to make the product.
There is an intermediate
MUCH more interesting thing for Mozilla and other vendors to do and that
is defining a useful way of adding XML protocol browser extensions.
There is a ton of efforts that simply goes nowhere including IETF's KEYPROV
because it is such a problem to get this basic thing.
It's that old "I'll invent an operating system in my browser" thing again :)
iang
--
dev-tech-crypto mailing list
dev-tech-crypto@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-tech-crypto
