I'm trying to figure out whether it's supported to call X509_free(NULL)
in 1.0.2 and beyond. It's not documented what action occurs when the
pointer is null. Also generally speaking is it supported to call openssl
free functions with null pointers?
--
openssl-dev mailing list
To unsubscribe: htt
I recently built OpenSSL 1.1.0 x64 debug using Visual Studio 2010, like
this:
perl Configure debug-VC-WIN64A no-asm
nmake
Then I ran the tests
nmake test
At test\recipes\80-test_ssl_old.t a message box popped up with an
assertion failure, I debugged it and saved the information. However when
It looks like the hostname is missing the trailing slash.
GET http://rt.openssl.org/Ticket/Display.html?id=3621 HTTP/1.1
Host: rt.openssl.org
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:38.0) Gecko/20100101
Firefox/38.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Acce
On 10/24/2015 11:41 AM, Richard Levitte wrote:
This is quite odd. Just for comparison, I tried the same on my laptop
(running Debian):
: ; pkg-config --static --libs-only-l openssl
-lssl -ldl -lcrypto -ldl
Thanks for checking Richard. I installed pkg-config .29 and that solved
the
On 5/27/2015 4:21 AM, Matt Caswell via RT wrote:
> On Wed May 27 06:41:51 2015, raysat...@yahoo.com wrote:
>> On 3/16/2015 5:45 AM, Kai Engert via RT wrote:
>>> Thank you very much for your work on this issue!
>>> In my testing so far, it works as requested.
>>>
>>> I noticed the code changes in x5
On 5/27/2015 4:21 AM, Matt Caswell via RT wrote:
On Wed May 27 06:41:51 2015, raysat...@yahoo.com wrote:
On 3/16/2015 5:45 AM, Kai Engert via RT wrote:
Thank you very much for your work on this issue!
In my testing so far, it works as requested.
I noticed the code changes in x509_vfy.c apply f
On 3/16/2015 5:45 AM, Kai Engert via RT wrote:
> Thank you very much for your work on this issue!
> In my testing so far, it works as requested.
>
> I noticed the code changes in x509_vfy.c apply fine on top of the 1.0.2
> stable branch, and the test suite succeeeds.
>
> Will you consider to add th
On 3/16/2015 5:45 AM, Kai Engert via RT wrote:
Thank you very much for your work on this issue!
In my testing so far, it works as requested.
I noticed the code changes in x509_vfy.c apply fine on top of the 1.0.2
stable branch, and the test suite succeeeds.
Will you consider to add this enhance
Hello, I built OpenSSL 1.0.1j this way, which in the case of x86 I have
done with some previous versions as well:
x86:
perl Configure debug-VC-WIN32 enable-static-engine
ms\do_ms
nmake -f ms\ntdll.mak
x64:
perl Configure debug-VC-WIN64A enable-static-engine
ms\do_win64a
nmake -f ms\ntdll.mak
I
When I built OpenSSL 1.0.1j for Win64 I had several hundred loss of data
warnings, most like this:
warning C4267: '=' : conversion from 'size_t' to 'int', possible loss of
data
Loss of data warnings can be serious or benign as you know. Is there a
list of known warnings that are expected and
On 6/5/2014 3:06 PM, Matt Caswell via RT wrote:
On Thu Jun 05 20:40:49 2014, rainer.j...@kippdata.de wrote:
File ssl/s3_pkt.c uses INT_MAX since May 19th. This macro is defined in
limits.h which is not included in s3_pkt.c.
+#include
#include
#include
Hmmmlook two lines down from where y
> Well I also did "set MAKE=mingw32-make" and the "perl Configure mingw ..."
>does do the correct thing; find and run the mingw32 version of make. However
>the Makefile supplied to it by the OpenSSL build system must be in the wrong
>format or something.
>
> The MSVC2010 build works (from
Hello,
I recently did a test compile of OpenSSL 1.0.0a in rxvt / msys (not command
prompt).
./config no-capieng enable-camellia > config.out 2>&1
make depend > make.depend.out 2>&1
make > make.out 2>&1
make test > make.test.out 2>&1
perl util/mkdef.pl 32 libeay enable-static-engine > libeay32.d
Both BIO_write() and BIO_puts() increment num_write on success. But BIO_gets()
by all appearances does not increment num_read, only BIO_read() does. I don't
see why that omission in BIO_gets() would be intentional. Any thoughts?
Thanks,
Jay
--- On Mon, 4/12/10, Phillip Hellewell wrote:
Thanks. That's good advice. BTW, I've finished implementing everything except
gets(). Other implementations I've seen seem to be able to get away with not
having it, but my unit tests are failing because of it.
what's failing? this is what mi
--- On Mon, 4/12/10, Phillip Hellewell wrote:
Do you think it's ok to set my type to just BIO_TYPE_SOURCE_SINK, or do I need
to set it to
(BIO_TYPE_SOURCE_SINK | some_magic_number_that_hopefully_noone_else_is_using)?
Phillip
Really it depends what's being called whether you are going to kee
--- On Mon, 4/12/10, Phillip Hellewell wrote:
So the goal is to implement a BIO interface that can "wrap" a file_read_random
or file_read_write object. I don't think it will be too tough, but after
reading your email I'm sure there will be a couple tricky parts. Thanks for
the hint about usi
Yes you can implement your own BIO. I've done it but I don't recommend it.
I had started writing something similar to osslsigncode but that could verify
Microsoft Authenticode. When hashing the file certain fields must be excluded.
PKCS7_verify() will not take a hash for comparison, only the con
oops, forgot the patch...
--- On Thu, 4/1/10, Ray Satiro wrote:
> From: Ray Satiro
> Subject: [PATCH] for compiling OpenSSL 1.0.0 (3/29/10) using MinGW
> To: openssl-dev@openssl.org
> Date: Thursday, April 1, 2010, 1:25 PM
> Third time's the charm, hopefully...
> --
&
Third time's the charm, hopefully...
--
Without this patch the make will error with "Pick one target type from" and a
list of assembler types.
"mingw32-make: *** [tmp\x86cpuid.asm] Error 1"
--
I had to make some changes to compile OpenSSL 1.0.0 (3/29/10) using MinGW. The
asmtype is not specified
20 matches
Mail list logo
