Hi,
I'm trying to package xca for Ubuntu, and I'm running into the same problem
discussed here:
http://fixunix.com/openssl/511998-openssl-org-1721-compilation-error-ubuntu-hardy-x86_64-a.html
I am using:
ii openssl 0.9.8g-4ubuntu3.4 Secure Socket Layer (SSL)
binary and
Hi,
Core 1
--
(gdb) bt
#0 0x4021e76e in pclose () from /lib/libc.so.6
#1 0x4021e548 in _IO_proc_close () from /lib/libc.so.6
#2 0x400b4772 in CRYPTO_free (str=0x0) at mem.c:380
(gdb)
And if I read that backtrace in the correct direction,
Sorry to interrupt, but
I've investigated lacks of documentation in the current OpenSSL
snapshot.
Method of investigation is quite simple
1. Run util/extract-names.pl on the all pod files in the doc/crypto and
doc/ssl and produce sorted list of all function names referenced in the
NAME sections.
2. Take lists of
I've investigated lacks of documentation in the current OpenSSL
snapshot.
Method of investigation is quite simple
1. Run util/extract-names.pl on the all pod files in the doc/crypto and
doc/ssl and produce sorted list of all function names referenced in the
NAME sections.
2. Take lists of
Hi,
I want to parse the x509 certficate in my application using the openssl API
not the command line tool.
Can anybody help me ?
Regards,
Vinod
--
_
Disclaimer: This e-mail message and all attachments transmitted with it
are
The routine AES_CCM_inc() keeps propagating the carry from an overflow,
which means our implementation fails for large blocks of data.
The following code fragment should address that bug.
/*! @brief
Increment the CCM CTR, which is variable length, big endian
@param counter the counter to
On Wed, Mar 18, 2009 at 11:29 AM, stefan.n...@t-online.de wrote:
Hi,
Core 1
--
(gdb) bt
#0 0x4021e76e in pclose () from /lib/libc.so.6
#1 0x4021e548 in _IO_proc_close () from /lib/libc.so.6
#2 0x400b4772 in CRYPTO_free (str=0x0) at mem.c:380
(gdb)
And if I read
2009/3/18 zlgodguy zlgod...@163.com:
hi:
very thanks for your response. but i have tested it. if i comment this
assert. the DTLS will hung in somewhere offten. i also don't know why. any
suggestion?
No idea; that was the easy try.
See these URLs for someone who's actually been using DTLS
Ger Hobbelt wrote:
Depends on what you consider 'parse': check out the sample source in
apps/x509.c and apps/asn1parse.c, among others.
Also check out the X509_get_() functions documentation (and for
actually parsing a cert, there's PEM_read_bio_X509_AUX(), for
example).
For a completely
