as an aside  ... note X9.59 which can be implemented with public/private key
digital signature ... but doesn't dictate certificates (it is possible to
implement with or without certificates; x.509 or not). W/o certificates, do
public key management using existing business processes in place for passwords
and PINs ... i.e. in conjunction with the database/file that is also referenced
for authorization (either logging-on or financial transactions).

random refs:

http://www.garlic.com/~lynn/

.... from x9a10 mailing list

The X9.59 DSTU period starts Feb. 1, 2001 and runs through Jan. 31, 2003

The X9.59 DSTU standards document should appear in the next standards
publication catalogue:

DSTU X9.59-2001, Electronic Commerce For the Financial Services Industry:
Account-Based Secure Payment Objects

X9.59 defines a secure payment object for use in authenticated financial
transactions. It relies on existing X9F security standards for payment object
authentication. It supports secure payments involving virtual (e.g. Internet) or
face-to-face transactions. It applies to card-based (e.g. smart card) financial
transactions as well as other forms of electronic financial transactions (e.g.
e-check).







Rich Salz <[EMAIL PROTECTED]> on 01/08/2001 05:39:22 PM

To:   [EMAIL PROTECTED]
cc:    (bcc: Lynn Wheeler/CA/FDMS/FDC)
Subject:  Re: Historical PKI resources



> Here's the BibTeX entry for the paper that apparently "started it all"..

The D-H paper is the public start of public-key crypto.  The scientific
American article by Gardner explained, pre-patent-issuance, RSA to the
world. The start of PKI is an MIT Master's Thesis that created
certificates.

Sorry, no references to any of the above.  Should not be hard to find.

The adoption by X.509 for use as authentication in X.500 got us common
technology, and is probably the only reason anyone will ever have to
learn
ASN.1 and DER. :)

The old IETF PEM project gave us "---BEGIN" lines :) and showed
empirically
that global X.500 deployment is a non-starter.  RSA's version, which
became
the IETF's S/MIME showed how to do it practically.

I'll stop now before I get too cynical. :)
     /r$





Reply via email to