From: p.v.mcmahon.rea0803@oasis.icl.co.uk
To: cypherpunks@toad.com
Message Hash: eb6253c8074741600c8c83c7b8e93be31c21a8be05271f17ef07b7df453cd8fc
Message ID: <9408091522.AA25889@getafix.oasis.icl.co.uk>
Reply To: N/A
UTC Datetime: 1994-08-09 15:22:09 UTC
Raw Date: Tue, 9 Aug 94 08:22:09 PDT
From: p.v.mcmahon.rea0803@oasis.icl.co.uk
Date: Tue, 9 Aug 94 08:22:09 PDT
To: cypherpunks@toad.com
Subject: Re: Problem in draft FIPS `CRYPTOGRAPHIC SERVICE CALLS'
Message-ID: <9408091522.AA25889@getafix.oasis.icl.co.uk>
MIME-Version: 1.0
Content-Type: text/plain
DATE FROM SUBJECT
Two related points:
1. Sorry to waste list bandwidth with such a question, but could
someone please post to me the original "Problem in draft FIPS
`CRYPTOGRAPHIC SERVICE CALLS'" item? (my server was down at the
weekend).
2. NIST have proposed the draft FIPS to a number of standards
development organisations - including X/Open and POSIX - and I
know that Microsoft have reviewed it, so it will likely influence
interfaces to commercially available cryptographic software and
devices.
If there is anybody with interest in crypto APIs on this list,
then your informed comments on this NIST proposal, or other
candidates (which I could make available if the level of interest
warranted it), or alternatives, would be useful and timely.
Thanks
Piers
--------------------------------------------------------------------
P V McMahon 09AUG94
ICL Enterprises
post: Kings House, 33 Kings Road, Reading, RG1 3PX, UK
email: p.v.mcmahon@rea0803.wins.icl.co.uk OR p.mcmahon@xopen.co.uk
phone: +44 734 634882
fax: +44 734 855106
---------------------------------------------------------------------
Return to August 1994
Return to “p.v.mcmahon.rea0803@oasis.icl.co.uk”
1994-08-09 (Tue, 9 Aug 94 08:22:09 PDT) - Re: Problem in draft FIPS `CRYPTOGRAPHIC SERVICE CALLS’ - p.v.mcmahon.rea0803@oasis.icl.co.uk