On Wednesday 23 January 2008 7:52 am, Rex Dieter wrote:
> See also:
> https://bugzilla.redhat.com/show_bug.cgi?id=429846
>
> Due to licensing issues, kdelibs dlopens openssl instead of linking. In
> order to make this work, kdelibs needs to know the soname of both libcrypto
> and libssl. Upstream
On Thursday 10 January 2008 9:22 pm, Justin Karneges wrote:
[...snip...]
> ask here about the state of DTLS and memory BIOs.
>
> If it is not possible, does anyone have a tip on how to make it possible?
> Maybe I could create a substitute for the dgram BIO that works on memory,
>
Hi folks,
I prefer to work with a memory BIO so that I can handle my own network
transporting. With TLS, I'm able to use a memory BIO. However, I cannot
determine if memory BIOs are supported with DTLS. I even recall trying to
write a program this way a year or so ago without success, so I t
the
> first ("ok") parameter passed in? (do my own checking
> on the expired stuff - or maybe there's some way to
> get the reasons for failure if the cert fails?) ...
> one of those reasons being acceptable in my case?
>
> Thanks again!
>
> --- Justin Karneg
On Thursday 27 October 2005 07:25, M G wrote:
> Hi list,
>
> My goal is to create mutual authentication for small business (each client
> app is also a server that can share data securely), is there a way to use
> SSL the "normal" way i.e., to create an X509 store, set verify function,
> use certif
On Wednesday 19 October 2005 08:37, Alain Damiral wrote:
> If I understand what Ning Ke suggests, OpenSSL uses a BIO output to send
> all those messages regardless of what that BIO is actually encapsulating
> ? (That would normally be the TCP connexion) If it is so, I believe I
> have the answer to
Hi guys,
I think I may have discovered a bug in OpenSSL's AES though EVP, or perhaps I
don't know how it is supposed to work. I want to encrypt with padding
disabled, but it seems my output data is padded regardless. For instance, if
I am using AES128 and I give a 16 byte input, I get a 32 by
