Compatibility between Java crypto and open ssl

Hello I have some question about compatibility between java crypto and openssl library. This is my case: 1.I created DESede key and stored it to file: {code} SecretKey key = KeyGenerator.getInstance(TripleDES).generateKey(); File f = new File(c:\\key.dat); DataOutputStream dos =new

RE: Signature verification fails with block type is not 01

Hello, We have the same openssl version in both the machines. Still the problem occurs. My proposition was to check private key modulus and public/certificate modulus to be sure that they are the same. Best regards, -- Marek Marcola [EMAIL PROTECTED]

RE: Signature verification fails with block type is not 01

Hello, Does anyone have a separate test program where we can test only the signature verification? # openssl genrsa -out rsa.pem 2048 # openssl rsa -in rsa.pem -text -noout # openssl rsa -in rsa.pem -pubout -out rsa-pub.pem # openssl rsa -in rsa-pub.pem -pubin -text -noout # echo test test

SHA1 checksum mismatch on openssl-0.9.8f tarball

The file at http://www.openssl.org/./source/openssl-0.9.8f.tar.gz.sha1 contains the checksum 0a0a3fd9be3d46053df2e91b6eb8a3b4348c793c whereas the file at http://www.openssl.org/source/openssl-0.9.8f.tar.gz (even after repeated download) has SHA1 checksum

Re: Signature verification fails with block type is not 01

Belliappa, Ashith Muddiana (HP Software) wrote: Hi, We have complied the code in an Solaris 5.7 machine. We have the same set of binaries working fine in all the Solaris 5.8 machines. I am getting the error ONLY in ONE Solaris 5.8 machine. i believe your saying that the same application

Re: Signature verification fails with block type is not 01

On Fri, Oct 12, 2007, Belliappa, Ashith Muddiana (HP Software) wrote: Hi, We have the same openssl version in both the machines. Still the problem occurs. Do you have the same binaries or did you compile it on both machines? If you compiled it try make test on the failing machine if that

RE: Signature verification fails with block type is not 01

Hi, We have complied the code in an Solaris 5.7 machine. We have the same set of binaries working fine in all the Solaris 5.8 machines. I am getting the error ONLY in ONE Solaris 5.8 machine. Does anyone have a separate test program where we can test only the signature verification? Regards

Re: openssl problem?

Hello, I compiled successfuly openssl 0.9.8f maked the tests and installed it. I compiled openssh 4.7.p1 with the above But when I try to compile qpopper 4.0.9 with ssl support at the end make outputs the following: gcc pop_dele.o pop_dropcopy.o pop_get_command.o pop_get_subcommand.o

openssl problem?

Hello all I compiled successfuly openssl 0.9.8f maked the tests and installed it. I compiled openssh 4.7.p1 with the above But when I try to compile qpopper 4.0.9 with ssl support at the end make outputs the following: gcc pop_dele.o pop_dropcopy.o pop_get_command.o pop_get_subcommand.o

Re: openssl problem?

Thanks a lot guys IT WORKS! Giannis Mantzouranis - Original Message - From: Marek Marcola [EMAIL PROTECTED] To: openssl-users@openssl.org Sent: Friday, October 12, 2007 10:42 PM Subject: Re: openssl problem? Hello, I compiled successfuly openssl 0.9.8f maked the tests and installed

OpenSSL 0.9.8f Win32 Compile Error

I am trying to compile version 0.9.8f for Windows, using VC++ 6.0, ActivePerl, and MASM 6.15.8803. I am following the instructions in INSTALL.W32, which works fine for the previous 0.9.8f build, but when I get to the point of running nmake -f ms\ntdll.mak I get the following errors in 0.9.8f:

Re: OpenSSL 0.9.8f Win32 Compile Error

I am following the instructions in INSTALL.W32, which works fine for the previous 0.9.8f build, but when I get to the point of running nmake -f ms\ntdll.mak I get the following errors in 0.9.8f: oops.. I ment to say that the previous version 0.9.8E works fine, and now that I look closer I see

Re: SHA1 checksum mismatch on openssl-0.9.8f tarball

On Fri 07-10-12 16:18, Lasse Kliemann wrote: The file at http://www.openssl.org/./source/openssl-0.9.8f.tar.gz.sha1 contains the checksum 0a0a3fd9be3d46053df2e91b6eb8a3b4348c793c whereas the file at http://www.openssl.org/source/openssl-0.9.8f.tar.gz (even after repeated download)

Re: OpenSSL 0.9.8f Win32 Compile Error

Did someone forget to add the equate for XMMWORD? Can anyone tell me how XMMWORD should be defined? It appears that I need more then just the newer version of MASM, and while reading the MASM32 forums they reference this page: http://www.intel.com/cd/ids/developer/asmo-na/eng/167741.htm?page=6

Re: Compatibility between Java crypto and open ssl

Hi, Metalpalo, Have you seen this? http://juliusdavies.ca/commons-ssl/pbe.html It doesn't quite do 100% what you're looking for, but I could probably do a release this weekend to help you. yours, Julius On 10/11/07, Metalpalo [EMAIL PROTECTED] wrote: Hello I have some question about

Re: Unusual RSA Private Key Format? (JSAFE)

Hi, Have you seen this? http://juliusdavies.ca/commons-ssl/utilities.html You can probably use the KeyStoreBuilder utility on the command-line to convert your OpenSSL RSA key into a java-friendly jks file (aka: java keystore file). Try this command: - java -cp

Re: SHA1 checksum mismatch on openssl-0.9.8f tarball

On Fri 07-10-12 15:02, Keith Thompson wrote: [...] That's not the only problem. As of a few minutes ago, there were two versions of the openssl-0.9.8f.tar.gz.asc file, one on the ftp server and another on the web server. Both are signed by the same key (which is *not* the key used for

Re: OpenSSL 0.9.8f Win32 Compile Error

I downloaded NASM (nasm-0.99.04-win32.zip) from Soundforge, and gave it a try, and when I run ms\do_nasm it is all sucessful but now I get a different error when running nmake -f ms\ntdll.mak: Microsoft (R) Program Maintenance Utility Version 6.00.9782.0 Copyright (C) Microsoft Corp 1988-1998.