Running a server or even a client that uses SSLv3 is an insecure protocol
(man in the middle POODLE attack is possible). You really don't want to
have that on your server! Perhaps if you explain why you believe you need
it folks can help with a secure strategy to assist. See this for reference:
It seems that user "guest" password "guest" allows one the ability to view
it.
On Mon, Jan 19, 2015 at 11:53 AM, Noel Carboni <
ncarb...@prodigitalsoftware.com> wrote:
> > See http://rt.openssl.org/Ticket/Display.html?id=3594
>
> As a new mailing list user, I don't seem to have an account capable
Just my opinion ... but ...
While nasm is the only supported assembler, I have been able to get masm to
work but I often have to tweak the perl code a bit. Every few months I
have been testing and reporting my findings to the openssl-dev group about
my results. When possible folks seem to be abl
es (ssleay32.dll and libeay32.dll) in my directory
with the new "exe" from the build and it worked just fine.
Thanks again to Tim Hudson, and of course to Rob Stradling for sharing the
utility,
Steve...
On Fri, Apr 11, 2014 at 10:58 PM, Tim Hudson wrote:
> On 11/04/2014 10:38 PM, Steven
The same issue when I tried to port over to windows, the ssl3_write_bytes
is not exposed in the library. There doesn't seem to be an easy workaround
that I can see.
Steve...
On Fri, Apr 11, 2014 at 7:40 AM, Walter H. wrote:
> On 10.04.2014 13:16, Rob Stradling wrote:
>
> On 09/04/14 20:43, Sal
I just compiled 32 bit with "ntdll.mak" with "nasm 2.11.02" and Visual
Studio Express 2013 with no issues, with and without the
"DOPENSSL_NO_HEARTBEATS" option. I was making it to drop the keys files
into Apache 2.2.26:
openssl.exe
ssleay32.dll
libeay32.dll
I am doing this to compile:
perl Conf
