Thanks for the replies. Let me clarify my question.
I get the following error when building OpenSSL 0.9.7c on 64-bit Redhat
Linux -
cryptlib.c:1: error: CPU you selected does not support x86-64
instruction set
make[3]: *** [cryptlib.o] Error 1
Do we build OpenSSL libraries on 64-bit Linux ? If y
Hi Marek,
Thanks for your reply.
I think the libssl.a and libcrypto.a should be ok. Maybe myAPI.a had failed to link libssl.a and libcrypto.a into itself?
Later I try another way: when I make myUI, I link to not only myAPI.a, but also libssl.a and libcrypto.a all. It seems that the openssl
On 2006.11.13 at 21:07:45 +0100, Magos?nyi ?rp?d wrote:
> Hi!
>
> It seems the answer is yes, see
> http://buildd.debian.org/build.php?pkg=openssl
> Another question is what you call 64 bit linux. In debian there are
> the following processor families supported which I think work in 64
> bit: al
Hello,
> > This file is not PEM format, after exporting certificate (under Windows)
> > from this file to PEM encoded certificate this looks redable under
> > Linux.
> >
> I'm afraid I don't understand what you mean. The file I sent was a *.crt
> file. What am I to do to get the file to work? He
I am getting error messages about system variables not being defined windows CE. Does this matter if I am configuring OpenSSL for Win32? %OSVERSION% %TARGETCPU% C:\openssl>perl Configure VC-WIN32Configuring for VC-WIN32 no-camellia [default] OPENSSL_NO_CAMELLIA (skip d
Marek Marcola wrote:
> This file is not PEM format, after exporting certificate (under Windows)
> from this file to PEM encoded certificate this looks redable under
> Linux.
>
I'm afraid I don't understand what you mean. The file I sent was a *.crt
file. What am I to do to get the file to work?
Hello,
>
> I am working on a small network application on Linux(kernel version
> is 2.4.20-8), comprise of two parts: myUI and myAPI(which is .a lib).
> Now i need add SSL to the application. I have installed OpenSSL
> in /usr/local, and i can find head files in /usr/local/include/openssl
> an
Hello,
> >> server167# openssl rsa -in private.key -modulus -noout
> >> Modulus=E186578C9DC070364BCFABAF834D4FF85385E0F03B1398136361704E4359E5ABC97A2C8AB00580E9E2E6EA8EF8828009F46E5FD1331B90F8828373B3AC77B47FA4AAEAA50BF56AE721A92ED3A62E51F3ABB593099FA077845D38DDF1FB4FA52ADA06618CDD8AF7F739AEE331352
Hello,
> >>> - check if you have compatible cert and key:
> >>> $ openssl x509 -in mrtablecloth-vi.com.pem -modulus -noout
> >>>
> This gives same as above.
> > Of course you should change example file key.pem to your real
> > file private.key.
> >
> I wasn't sure, because what you use
Marek Marcola wrote:
>> server167# openssl x509 -in mrtablecloth-vi.com.pem -text -noout
>> unable to load certificate
>> 67298:error:0906D06C:PEM routines:PEM_read_bio:no start
>> line:/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/pem/pem_lib.c:637:Expecting:
>> TRUSTED CERTIFICATE
Hi!
It seems the answer is yes, see http://buildd.debian.org/build.php?pkg=openssl
Another question is what you call 64 bit linux. In debian there are
the following processor families supported which I think work in 64
bit: alpha, hppa, sparc64 and ia64. At least two of them uses 32 bit
userspace
Hallo, I guess someone of you is really confortable with the ASN1 API
openssl offers. I have to admit, I have no idea how it exactly works,
and information is really more than hard to find.
I need to read the following structures. Below the definitions you
find my try.
Maybe you can give me
Hello,
> server167# ls
> mrtablecloth-vi.com.crt mrtablecloth-vi.com.csr mrtablecloth-vi.com.pem
> private.key
>
> > I suggest:
> > - check that certificate is readable with:
> > $ openssl x509 -in cert.pem -text -noout
> >
> server167# openssl x509 -in mrtablecloth-vi.com.pem -text -noout
Marek Marcola wrote:
First up...
server167# ls
mrtablecloth-vi.com.crt mrtablecloth-vi.com.csr mrtablecloth-vi.com.pem
private.key
> I suggest:
> - check that certificate is readable with:
> $ openssl x509 -in cert.pem -text -noout
>
server167# openssl x509 -in mrtablecloth-vi.com.pem
Hi,
I could not find any
information about openSSL being supported on 64-bit Linux
platform.
Any pointers would
be most helpful.
thanks
Saumya
Hello,
> 2006-11-10 16:45:17: (network.c.377) SSL: Private key does not match
> the certificate public key, reason: error:0906D06C:PEM
> routines:PEM_read_bio:no start line /etc/ssl/certs/mrtablecloth.com.pem
>
> So, I deleted everything and tried again. Got the _same_ error. I know
> darn well I
Hi;
I sent this over the weekend and it probably got overlooked. I really
need help here, so I'm hoping someone can do that. I'm
trying to install a cert and I get this error:
2006-11-10 16:45:17: (network.c.377) SSL: Private key does not match
the certificate public key, reason: error:0906D06C:P
Ofcourse :)
Thanks alot for your help and time !!
Grtz
> Hello,
>> SHA1((const unsigned char*)word,strlen(word), hashcode);
>> result = strcpy(result,hashcode);
>>
>> printf("%i byte code generated\n> Result is now %i bytes
>> long\n",strlen(hashcode),strlen(result));
>>
>> while
Hi all,
I am working on a small network application on Linux(kernel version is 2.4.20-8), comprise of two parts: myUI and myAPI(which is .a lib).
Now i need add SSL to the application. I have installed OpenSSL in /usr/local, and i can find head files in /usr/local/include/openssl and libssl.a
On Mon, Nov 13, 2006, Simon McMahon wrote:
>
> > Ah that's a bug in the ASN1 module associated with the OCSP request.
> I'll look into fixing that.
>
> Thanks. My other post shows the openssl request (with -no_certs) includes
> an empty sequence for 'certs' which the responder must be looking
I found it using google code search:
http://www.google.com/codesearch
For example one is:
http://www.google.com/codesearch?q=+PKCS12_parse+show:eeHJRh5kAqQ:7aZjvmBSuiI:xYw6oBzZOkk&sa=N&cd=8&ct=rc&cs_p=http://www.openssl.org/source/openssl-0.9.7f.tar.gz&cs_f=openssl-0.9.7f/apps/apps.c#a0
Regards.
Dear all,I'm implementing HSM support to our OCSP Responder which uses openssl libraries to perform crypto operations. When searching for a PKCS11 engine's implementation for OpenSSL 0.9.8c (OCSP patched already with Engine support) I found OpenSC project and their engine_pkcs11 libraries, so I've
Thanks.2006/11/13, Victor B. Wagner <[EMAIL PROTECTED]>:
On 2006.11.10 at 13:23:48 +, Net Warrior wrote:>Hi there guys.>My question is simple, one I've created the certficates and I want to>deploy the public key to the clients,.>which will be he best methood to do the deploymen
Alexis Lefort wrote:
I found a source code in the openssl examples.
Could you please point me to a such :)
Thanks.
But I still don't know how to test the type of the file (X.509 or
PKCS#12). Is there a mean to do so?
regards
Alexis
Alexis Lefort a écrit :
I have now several other questions:
Hello,
> SHA1((const unsigned char*)word,strlen(word), hashcode);
> result = strcpy(result,hashcode);
>
> printf("%i byte code generated\n> Result is now %i bytes
> long\n",strlen(hashcode),strlen(result));
>
> while(sha1_count>1)
> {
>SHA1((const unsigned char*)hashco
On 2006.11.10 at 13:23:48 +, Net Warrior wrote:
>Hi there guys.
>My question is simple, one I've created the certficates and I want to
>deploy the public key to the clients,.
>which will be he best methood to do the deployment of the cacert.pem file?
Typically one does publis
26 matches
Mail list logo
