Hello!
I was playing around with DTLSv1 (openssl 1.0.1e) and tried to get DTLS
working with a nonblocking socket and multiple destinations.
The outline of my application is as follows:
On every socket event I peek the socket address and lookup the correct SSL
struct. If none is found I try to DT
> From: owner-openssl-us...@openssl.org On Behalf Of Tom Pfeifer
> Sent: Monday, February 10, 2014 16:53
> I've tried doing that with no success so far, most likely due my lack of
> understanding of how to set up policy sections in the config file (among
> other things).
>
The policy section(s) i
HFS has several meanings, and so does keyring, but they seem to be used in
combination only for some
SSL/TLS piece of IBM z/OS. My top google hit is pic.dhe.ibm.com which
sounds authoritative but responds down.
The next page of hits are mostly looking at small patches of the elephant,
but sever
I'm trying to remediate a couple of memory leaks on shutdown. I'm
having trouble: (1) locating a definitive guide that lists what should
be called during cleanup; and (2) what order they should be called in.
The closest I've find to answering the questions are (1) OpenSSL
source code; and (2)
http
On 02/07/2014 04:11 PM, Walter H. wrote:
> On 07.02.2014 21:04, Tom Pfeifer wrote:
>> ...which are required for Extended Validation (EV) certificates.
>> I'm currently using openSSL 1.0.1e-fips on Fedora 20, and I have
>> these OIDs specified in the [new_oids] section in openssl.cnf like
>> this
Just an update..
Looks like -nodetach option is doing the trick..phew..
S
--
View this message in context:
http://openssl.6102.n7.nabble.com/openssl-smime-sign-issue-tp48444p48472.html
Sent from the OpenSSL - User mailing list archive at Nabble.com.
___
Hello,
If I run openssl -verify command it is successful but if I send the output
to /usr/sbin/sendmail to mail me, the outlook says invalid signature..
I am verifying like this:
openssl smime -sign -signer
/home/howler/processEmail/signedCert/email_sign_cert_prod.pem -inkey
/home/howler/process
On 2/9/2014 9:18 PM, Gisle Vanem wrote:
"Thomas J. Hruska" wrote:
If this ends up being a bug that won't be fixed, then my
recommendation is to build it against VC++. Borland has two
command-line tools called 'impdef' and 'implib' bundled with their
compiler suite(s) that can take almost any
