Re: 3DES ECB
Hello Stella, Tuesday, June 04, 2002, 11:14:59 AM, you wrote: SP Hi, SP I was wondering if someone could clarify this for me. I'm trying to decrypt SP a string which has been encrypted in 3DES ECB mode. SP I'm using the command line utility and a program I have written to do this. SP According to the EVP_EncryptInit.html, I should use the cipher SP EVP_des_ede3(). This is correct! SP However in the command line utility I don't see any 3DES ECB cipher. SP According to the 'enc' man page the cipher 'des-ede3' is an alias for SP 'des-ede3-cbc'. Maybe if you supply an IV then it is aliased to des-ede3-cbc ?! SP Are both of these correct? If so, shouldn't there be a standard naming SP convention for these ciphers? and how do I encrypt/decrypt a string in 3DES SP EC mode using the command line utility? openssl des-ede3 -iv 0 -other-options-here __ OpenSSL Project http://www.openssl.org User Support Mailing List[EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: Unable to load
Hello Leandro, Thursday, May 13, 2004, 10:25:39 PM, you wrote: LSdP seeded:md_rand.c:501:You need to read the OpenSSL FAQ, LSdP http://www.openssl.org/support/faq.html Have you done as suggested ? __ OpenSSL Project http://www.openssl.org User Support Mailing List[EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
openssl-0.9.6d fails under cygwin on Win2000 was Re:
Hello A?rtCorcoran, Saturday, May 11, 2002, 7:34:49 AM, you wrote: Arnc Hi, I'm trying to compile openssl-0.9.6d on Win2000 under cygwin (latest cygwin). Arnc The configure works fine, but it fails during make with the following: Arnc make[3]: Entering directory `/d/acorcoran/apps/openssl/openssl-0.9.6d/crypto/objects' Arnc /usr/bin/perl objects.pl objects.txt obj_mac.num obj_mac.h Arnc objects.txt:92:Undefined identifier SMIME Arnc make[3]: *** [obj_mac.h] Error 255 Just tested it here - WinXP Home, cygwin 1.3.10 / all latest packages installed - and it compiles and tests jsut fine. Which is the version of cygwin that you're using ? Also which is the version of the perl package you're using - you can check this with 'cygcheck -c'. Is the directory, you're trying to compile in, mounted in binary mode ? __ OpenSSL Project http://www.openssl.org User Support Mailing List[EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
J/Crypto 3.3 DER encoded certificate cannot be read by openssl-0.9.6b
Hello, there! :) I've checked google in this but to no avail - so I'm asking here... Hope its not a duplicate thread. Trying to read the attached DER form of a X509 certificate with OpenSSL 0.9.6c and 0.9.6b yields the following error: paveltz@MORDOR ~ $ openssl x509 -in ./1.der -inform DER unable to load certificate 3212:error:0D06B078:asn1 encoding routines:ASN1_get_object:header too long:asn1_ lib.c:139: I've tried to use the asn1parse utility but to no avail: paveltz@MORDOR ~ $ openssl asn1parse -inform DER -in ./1.der -dump 0:d=0 hl=16 l=-991318795 cons: VISIBLESTRING Error in encoding 3552:error:0D06B078:asn1 encoding routines:ASN1_get_object:header too long:asn1_ lib.c:139: The certificate was produced by calling JCRYPTO_X509Certificate.toDER method. Any help ? :) Any information on how to debug further ? 1.der Description: application/x509-ca-cert
Re: J/Crypto 3.3 DER encoded certificate cannot be read by openssl-0.9.6b
Please, ignore this post. Monday, April 15, 2002, 4:34:58 PM, you wrote: PT Trying to read the attached DER form of a X509 certificate with PT OpenSSL 0.9.6c and 0.9.6b yields the following error: __ OpenSSL Project http://www.openssl.org User Support Mailing List[EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Fwd: [BUG suggested PATCH] EVP_DecodeUpdate 0.9.6b 0.9.6c
This is a forwarded message From: Pavel Tsekov [EMAIL PROTECTED] To: [EMAIL PROTECTED] Date: Thursday, April 11, 2002, 12:39:59 PM Subject: [BUG suggested PATCH] EVP_DecodeUpdate 0.9.6b 0.9.6c Seem like the original message could not made its way to the mail list so am I forwarding it. ===8==Original message text=== Hello, there! :) My colleague Nedelcho Stanev and myself have identified what we would think to be a bug (or a flaw) in the EVP_DecodeUpdate() routine. We were trying to read base64 encoded data with the base64 BIO which has the 'next' member pointed to membuf BIO in which we write the encoded data. So far so good ... Eventually it turned up that some of the data we pass to the BIO chain is properly decoded while other not - or more properly would be to say - partially decoded. We tried to debug the problem and here is what we have found: The EVP_DecodeUpdate() routine errnously returns 0 (EOF) if the buffer passed it, ends with CRLF and EVP_DecodeBlock() has just processed the data upto the ending CRLF. Attached is a patch and a testcase. I tried to follow the coding style and to make the change not intrusive :) though its a very small change :) Here is how to reproduce: 1. Base64 encode a file lets say 200kb 2. unix2dos the output 3. Use the attached testcase to decode the file ===8===End of original message text=== encode.c.patch Description: Binary data bio.cpp Description: Binary data
[BUG suggested PATCH] EVP_DecodeUpdate 0.9.6b 0.9.6c
Hello, there! :) My colleague Nedelcho Stanev and myself have identified what we would think to be a bug (or a flaw) in the EVP_DecodeUpdate() routine. We were trying to read base64 encoded data with the base64 BIO which has the 'next' member pointed to membuf BIO in which we write the encoded data. So far so good ... Eventually it turned up that some of the data we pass to the BIO chain is properly decoded while other not - or more properly would be to say - partially decoded. We tried to debug the problem and here is what we have found: The EVP_DecodeUpdate() routine errnously returns 0 (EOF) if the buffer passed it, ends with CRLF and EVP_DecodeBlock() has just processed the data upto the ending CRLF. Attached is a patch and a testcase. I tried to follow the coding style and to make the change not intrusive :) though its a very small change :) Here is how to reproduce: 1. Base64 encode a file lets say 200kb 2. unix2dos the output 3. Use the attached testcase to decode the file encode.c.patch Description: Binary data bio.cpp Description: Binary data
Re: Error when signing a certificate
Hello Charles,
Thursday, April 11, 2002, 3:38:44 PM, you wrote:
CH Hi , I am trying to do a SSL certificate to use TLS/SSL encryption with Qpopper. I
read the doc and I created a certificate request succesfully but it seems that when I
try to sign it, it crash
CH with a serious error, here's the output:
CH [bob@domain ]# openssl ca -in req.pem -out signed_req.pem
CH Using configuration from /usr/share/ssl/openssl.cnf
CH ./demoCA/private/cakey.pem: No such file or directory
CH trying to load CA private key
CH 14403:error:02001002:system library:fopen:No such file or
directory:bss_file.c:245:fopen('./demoCA/private/cakey.pem','r')
CH 14403:error:20074002:BIO routines:FILE_CTRL:system lib:bss_file.c:247:
What's so serious here ? It just cannot find a file ? Have you checked
that the file it complains about really exists ? I see it uses a
relative path to look the CA key - maybe you have a erronous
configuration file ?
__
OpenSSL Project http://www.openssl.org
User Support Mailing List[EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
