This is a collection of reports about email delivery
process concerning a message you originated:

<smtp ipebio15.ise.pw.edu.pl [EMAIL PROTECTED] 1284>: ...\
        expired after 3 days, problem was:
        smtp; 500 (connect to ipebio15.ise.pw.edu.pl 
[194.29.161.106|25|194.29.160.2|57475]: Connection timed out)

Following is a copy of MESSAGE/DELIVERY-STATUS format section below.
It is copied here in case your email client is unable to show it to you.
The information here below is in  Internet Standard  format designed to
assist automatic, and accurate presentation and usage of said information.
In case you need human assistance from the Postmaster(s) of the system which
sent you this report, please include this information in your question!

        Virtually Yours,
                Automatic Email delivery Software

Reporting-MTA: dns; elektron.elka.pw.edu.pl
Arrival-Date: Wed, 18 Jul 2001 04:28:48 +0200

Original-Recipient: rfc822;[EMAIL PROTECTED]
Final-Recipient: RFC822;[EMAIL PROTECTED]
Action: failed
Status: 5.4.1 (TCP/IP-connection failure)
Diagnostic-Code: smtp; 500 (connect to ipebio15.ise.pw.edu.pl 
[194.29.161.106|25|194.29.160.2|57475]: Connection timed out)
Remote-MTA: dns; ipebio15.ise.pw.edu.pl (194.29.161.106|25|194.29.160.2|57475)
Last-Attempt-Date: Sat, 21 Jul 2001 23:26:33 +0200

Reporting-MTA: dns; elektron.elka.pw.edu.pl
Arrival-Date: Wed, 18 Jul 2001 04:28:48 +0200

Original-Recipient: rfc822;[EMAIL PROTECTED]
Final-Recipient: RFC822;[EMAIL PROTECTED]
Action: failed
Status: 5.4.1 (TCP/IP-connection failure)
Diagnostic-Code: smtp; 500 (connect to ipebio15.ise.pw.edu.pl [194.29.161.106|25|194.29.160.2|57475]: Connection timed out)
Remote-MTA: dns; ipebio15.ise.pw.edu.pl (194.29.161.106|25|194.29.160.2|57475)
Last-Attempt-Date: Sat, 21 Jul 2001 23:26:33 +0200


> certificate with the signing authority I created, does this create a 128
> bit or 40 bit certificate?

You are confusing the RSA keysize (typically 1024) and the certificate,
with the session key (3des, rc4).  Public-key encryption is expensive
for "bulk data."  So it's only used to securely exchange session keys
for short-lived (hence "session") stream-oriented ciphers.
        /r$

-- 
Zolera Systems, Securing web services (XML, SOAP, Signatures,
Encryption)
http://www.zolera.com
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [EMAIL PROTECTED]
Automated List Manager                           [EMAIL PROTECTED]


Reply via email to