On Wednesday 14 March 2012 11:09:22 OpenSSL wrote:
>OpenSSL version 1.0.1 released
>===
>
>http://www.openssl.org/source/exp/CHANGES.
>
>The most significant changes are:
>
> o TLS/DTLS heartbeat support.
> o SCTP support.
> o RFC
On Wed, Sep 29, 2010 at 16:04, wrote:
> Why has no nobody attended to me, i need solution urgently.
then higher a consultant
-mike
__
OpenSSL Project http://www.openssl.org
User Support Mailing Li
On Tue, May 25, 2010 at 19:09, Carruth, Rusty wrote:
> Should I send this request to the developers list rather than here?
>
> If so, I'll be happy to do so...
>
> In any case, the short version is: I cross-compiled openssl for target
> xscale, and could not load the kernel module because some of
On Wed, Nov 4, 2009 at 08:24, jj Zhu wrote:
> gcc -static /usr/lib/libssl.a /usr/lib/libcrypto.a error.o wrapsock.o
> wrapunix.o driverUtility.o driver.o -o driver
> I get these compile errors:
> driver.o: In function `logout':
> driver.c:(.text+0x16e): undefined reference to `SSL_libra
On Tue, Nov 3, 2009 at 13:45, john blair wrote:
>> dont link static libraries into shared libraries and it isnt a problem
>
> Ya that is true. But, I do want to link the static library to the shared
> library.
linking static libraries into a shared library is wrong. maybe
someone else will help
On Mon, Nov 2, 2009 at 21:37, john blair wrote:
> I have built openssl-0.9.8k and am trying to link libcrypto.a statically with
> my project. I think libcrypto.a contains contains non-relocatable functions
> For example, consider the following:
> #include
> void foo(void) {
> DES_encry
On Tue, Jul 21, 2009 at 10:46, Dr. Stephen Henson wrote:
> On Tue, Jul 21, 2009, Fred Keet wrote:
>> At this point I've got code that generates the ec keys from the sect163k1
>> curve, and then signs a block of data. When I compare this with the ecsign
>> utility they provide (apparently built on M
On Mon, Jul 20, 2009 at 09:51, Fred Keet wrote:
> I'm in the process of writing an application that signs binary data for
> loading
> onto a Analog Devices BlackFin microprocessor. These chips have "built in"
> support for verification of code. The chip gets loaded with the EC public
> key,
> and t
i was given a small "ecsign.exe" program that takes some ECC parameters, the
private key, a random number, and outputs a signature of the specified binary.
i'm trying to ditch this program in favor of the openssl suite (for obvious
practical reasons).
for example, the parameters file looks lik
i was given a small "ecsign.exe" program that takes some ECC
parameters, the private key, a random number, and outputs a signature
of the specified binary. i'm trying to ditch this program in favor of
the openssl suite (for obvious practical reasons).
for example, the parameters file looks like (
10 matches
Mail list logo
