Hi all, I still have the problem that when I compile OpenSSL, it creates the static libraries libcrypto.a and libssl.a, but does not create the dynamic libraries .so.0.9.8. (I thought this problem had resolved itself, but really the apps I was using were all using the .so libraries from an earlier installation of OpenSSL). I discovered in the Makefile that it does in fact try to create the .so files. When I manually try to compile it, I get: $ make libssl.so.0.9.8 ... ....<pages and pages of text output>.... ... <unknown> 0x594 ./libcrypto.a(bf_buff.o) <unknown> 0x5e0 ./libcrypto.a(bf_buff.o) <unknown> 0x5e8 ./libcrypto.a(bf_buff.o) <unknown> 0x65c ./libcrypto.a(bf_buff.o) <unknown> 0x66c ./libcrypto.a(bf_buff.o) <unknown> 0x68c ./libcrypto.a(bf_buff.o) <unknown> 0x6a8 ./libcrypto.a(bf_buff.o) <unknown> 0x6b4 ./libcrypto.a(bf_buff.o) <unknown> 0x6f4 ./libcrypto.a(bf_buff.o) <unknown> 0x710 ./libcrypto.a(bf_buff.o) gethostbyname 0x60 ./libcrypto.a(b_sock.o) gethostbyname 0x38c ./libcrypto.a(b_sock.o) dlerror 0xb8 ./libcrypto.a(dso_dlfcn.o) dlerror 0x320 ./libcrypto.a(dso_dlfcn.o) dlerror 0x468 ./libcrypto.a(dso_dlfcn.o) dlopen 0x88 ./libcrypto.a(dso_dlfcn.o) dlclose 0x148 ./libcrypto.a(dso_dlfcn.o) dlclose 0x234 ./libcrypto.a(dso_dlfcn.o) dlsym 0x2f0 ./libcrypto.a(dso_dlfcn.o) dlsym 0x42c ./libcrypto.a(dso_dlfcn.o) ld: fatal: relocations remain against allocatable but non-writable sections $
Do you know what this error means? Thanks, -Siddhartha On 8/19/07, Andreas Jellinghaus <[EMAIL PROTECTED]> wrote: > > On Wednesday 15 August 2007 04:15:59 Siddhartha Kasivajhula wrote: > > So I continued to follow the directions on the OpenSC QuickStart page, > and > > I was able to create the certificate file req.pem. And I was also able > to > > put the certificate onto the card as instructed. > > > > How do I verify that the certificate is on the card? > > pkcs15-tool can list the certificates and extract them. > > > I was trying to run "verify" in opensc-explorer, but I entered the wrong > > password too many times and now it says "authentication locked"! > > pkcs15-tool can unblock your pin if you know the puk. > if not you can try to format the card with pkcs15-init and delete > keys and certificates in the process, and then generate new keys > or store them once more. > > > What is the correct format for the "verify" command? > > pin characters as hex. "1" becomes 31. "1234" would be "31:32:33:34". > beware: some cards need padding etc. pkcs15-tool takes care of all that. > if you use opensc-explorer, you need to take care of it yourself. > > > Also, if I want to clear the card and reinitialize it, would I use > > "pkcs15-init --erase-card"? > > yes. > > Regards, Andreas >
_______________________________________________ opensc-devel mailing list [email protected] http://www.opensc-project.org/mailman/listinfo/opensc-devel
