I
think you just have to make sure that whatever library(ies) containing accept,
socket, send (etc) is/are included in the final link stage. When
confronted with this sort of thing, I usually just grep around for whatever the
relevant library is and I'm on my way. (If
it's already in your
.so = shared object... like a DLL.
.a is a static library.
Sometimes people append the version to a .so library and
then have a link pointing to whichever version they want.
e.g. "ln -s openssl.so.0.9.6b openssl.so"
This will create the link... then anything going after
openssl.so (and able t
I found this snippet for implementing a timeout for sockets, although
the example had nothing to do with SSL... I put it in some code and it
seems to work fine, but was wondering if anybody else has tried it or
can comment on the idea. Thanks!
/// snippet:
int err;
fd_set fds;
struct timeval
I've seen the questions and have asked them myself, but I've finally
gotten it to work. This does NOT use anything fancy in SSL: it performs
the handshake that SSL_connect() gives you, but that's it: no
certificates, etc... so this is the bare minimum (that I'm aware of)
needed to do an HTTPS pos