|
Developer
Downloads
Tutorial
Licensing
Mac
OS X
Success Stories
|
|
Efficient e-signature
XML software articles specification.
|
There is also an efficient e-signature
XML software articles implicit assumption here, and it's in your
face obvious upon due examination. XML is Web and server based. It's a
sort of thin client approach, as opposed to the "damn the bandwidth,
load the servlet" approach of Java.
XML
signatures will therefore use the Web to find out the method to
encode or decode things. Exactly how it uses the Web can be
syntactically specified, but that kind of discussion ignores the
meta-question of what URL to use. That is, if the signature needs 'Net
resources to complete its action, then who will supply those resources?
If this sort of signature becomes a widely-used "semaphore" for
authentication of messages and transactions, whichever URLs are pointed
to in the XML
code can become a de facto standard for authentication Efficient
e-signature XML software articles services.
Efficient
e-signature XML software articles,
The real use of
authentication services will most
likely be found in Web shopping.
|
Efficient e-signature XML software
articles example a merchant will want to know that he is receiving a
valid order from a customer, and so will insist on some form of
acceptable
authentication. This is the sort of problem that was first solved by
Electronic Data Interchange systems that used secured networks to
operate. Over the insecure Internet, the same previously-solved
operational problems remain open. The XML signature process is meant to
address this in a sweeping way, but that sweep is part of the problem.
This little known candidate carries in it the seeds of a method for some
company to monopolize Internet Efficient e-signature XML software
articles authentication services.
Let me posit a scenario. Imagine that some Commercial Off The Shelf
software company decides it wants to be the authorization service that
all must pass through to get things done. Also further posit that this
COTS proprietary operating system is found on the majority of the
deployed systems under consideration. The COTS vendor then brings out an
extra Proprietary version of its OS, which contains a client that uses
XML signatures
for security. All the XML code points to this vendor's servers to
provide information, sort of like a non public PKI infrastructure. This
client becomes widely used for authentication simply because it's easy
to set up as a default since the OS is widely used. Also, said
manufacturer embeds it in its popular "free" browser as the Efficient
e-signature XML software articles default security mechanism.
|
|
