--0-1233789107-1110434085=:6906
Content-Type: text/plain; charset=us-ascii

Hi all

I need to check for RFC conformations for the following alogorithms

P_MD5_RSA_512
P_SHA1_RSA
P_SHA1_DSA
P_OSA_MD5
P_OSA_HMAC_SH1_96
P_OSA_HMAC_MD5_96

Details of each is provide below
Wether any of you have checked for the RFC compliances of these alogrithem
If so can u please provide me the results..

with Thanks
Nagabhushana Rao Devineni


P_MD5_RSA_512

MD5 takes an input message of arbitrary length and
produces as output a 128bit message digest of the input. This is then
encrypted with the private key under the RSA publickey cryptography
system using a 512bit modulus. The signature generation follows the
process and format defined in RFC 2313 (PKCS#1 v1.5)


P_MD5_RSA_1024 MD5
takes an input message of arbitrary length and
produces as output a 128bit message digest of the input. This is the
encrypted with the private key under the RSA public key cryptography
system using a 1024bit modulus. The signature generation follows the
process and format defined in RFC 2313 (PKCS#1 v1.5).

P_RSASSA_PKCS1_v1_5_SHA1_1024
SHA1 is used to produce a 160bit message
digest based on the input message to be signed. RSA is then used to
generate the signature value, following the process defined in section
8 of RFC 2437 and format defined in section 9.2.1 of RFC 2437. The RSA
private/public key pair is using a 1024bit modulus.

P_SHA1_DSA SHA1
is used to produce a 160bit message digest based on
the input message to be signed. DSA is then used to generate the
signature value. The signature generation follows the process and
format defined in section 7.2.2 of RFC 2459.


AuthMechanism :

P_OSA_MD5
Authentication is based on the use of MD5 (RFC 1321) hashing
algorithm to generate a response based on a shared secret and a
challenge received via challenge() method. The capability touse this
algorithm is required to be supported when using CHAP (RFC 1994)

P_OSA_HMAC_SH1_96
Authentication is based on the use of HMAC-SHA1 (RFC
2404) hashing algorithm to generate a response based on a shared
secret and a challenge received via challenge() method.

P_OSA_HMAC_MD5_96
Authentication is based on the use ofHMAC-MD5 (RFC
2403) hashing algorithm to generate a response based on a shared
secret and a challenge received via challenge() method














---------------------------------
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
--0-1233789107-1110434085=:6906
Content-Type: text/html; charset=us-ascii


Hi all

  I need to check for RFC conformations for the following alogorithms

P_MD5_RSA_512
P_SHA1_RSA
P_SHA1_DSA
P_OSA_MD5
P_OSA_HMAC_SH1_96
P_OSA_HMAC_MD5_96

Details of each is provide below
Wether any of you have checked for the RFC compliances of these alogrithem
If so can u please provide me the results..

 

with Thanks
Nagabhushana Rao Devineni

 

 

P_MD5_RSA_512

 

 MD5 takes an input message of arbitrary length and
produces as output a 128bit message digest of the input. This is then
encrypted with the private key under the RSA  publickey cryptography
system using a 512bit modulus. The signature    generation follows the
process and format defined in RFC 2313 (PKCS#1 v1.5)

 

 

P_MD5_RSA_1024  MD5

 takes an input message of arbitrary length and
produces as output a 128bit message digest of the input. This is the
encrypted with the private key under the RSA public key cryptography
system using a 1024bit modulus. The signature generation follows the
process and format defined in RFC 2313 (PKCS#1 v1.5).

P_RSASSA_PKCS1_v1_5_SHA1_1024  

SHA1 is used to produce a 160bit message
digest based on the input message to be signed. RSA is then  used to
generate the signature value, following the process defined in section
8 of RFC 2437 and format defined in section 9.2.1 of RFC 2437. The RSA
private/public key pair is using a 1024bit modulus.

P_SHA1_DSA      SHA1

 is used to produce a 160bit message digest based on
the input message to be signed. DSA is then used to generate the
signature value. The signature generation follows the process and
format  defined in section 7.2.2 of RFC 2459.


AuthMechanism   :

P_OSA_MD5     

  Authentication is based on the use of MD5 (RFC 1321) hashing
algorithm to  generate a response based on a shared secret and a
challenge received via  challenge() method. The capability touse this
algorithm is required to be supported when using CHAP (RFC 1994)

P_OSA_HMAC_SH1_96      

 Authentication is based on the use of HMAC-SHA1 (RFC
2404) hashing   algorithm to generate a response based on a shared
secret and a  challenge received via challenge() method.

P_OSA_HMAC_MD5_96   

    Authentication is based on the use ofHMAC-MD5 (RFC
2403) hashing algorithm to generate a response based on a    shared
secret and a challenge received via challenge() method

 



 

 


 




 



Do you Yahoo!?

Yahoo! Small Business - Try our new resources site!
--0-1233789107-1110434085=:6906--
__________________________________________________ ____________________
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager majordomo@openssl.org