"Sanford Staab(Gmail)" wrote:
I think it is high time for a v2 of openssl, a rewrite almost from scratch, removing
support for older protocols and ciphers and simplifying it down with full TDD from
start to finish to really correct this problem.
So why don't you simply switch to PolarSSL?
"Dave Thompson" wrote:
I don't see a simple fix. What you could do is write
a simple program that connects to the desired host, if
successful gets the peer cert and writes it out, and
(always immediately) closes and exits -- or just exits
and lets the OS-level TCP disconnect force a close.
"Dave Thompson" wrote:
He could just do a:
echo foo | openssl s_client -connect "uri.com:443" > cert.txt
This executes in 1 sec here.
What openssl build on what Windows?
The one from the Msys package [1]. Running on Win-XP SP3.
It has a special dependency as shown here:
cygcheck g:\Mi
Hello lists.
I've a question/doubt about this passage in
NOTES-Windows.txt:
Linking your application
This section applies to all "native" builds.
If you link with *static OpenSSL libraries* then you're expected to
additionally link your application with WS2_32.LIB
I've noted that when build OpenSSL using MSVC,
some empty directories are created:
./crypto/include
./crypto/providers
I configured with:
perl.exe -I. -I./util/perl Configure VC-WIN32-ONECORE no-makedepend
enable-zlib enable-trace enable-md2 no-ec_nistp_64_gcc_128
enable-asan enable-ari
It tested it on master, it seems like the empty directories are created by the
Configure script.
Where exactly?
Would you mind opening a GitHub issue for it?
Done:
https://github.com/openssl/openssl/issues/12815
--
--gv
Beilharz, Michael wrote:
I know that there are additional ways to verify "my binaries" like verifying hash-values etc., but i was wondering, if
it is possible to verify a signed binary.
On Windows? Sure with this tool for example:
https://docs.microsoft.com/en-gb/sysinternals/downloads/sigch
"Igor Mironchik" wrote:
But now I have the following problems:
.\crypto\ec\ec_asn1.c(260) : error C2370: 'ECPKPARAMETERS_it' :
redefinition; di
fferent storage class
.\crypto\ec\ec_asn1.c(258) : see declaration of 'ECPKPARAMETERS_it'
.\crypto\ec\ec_asn1.c(261) : error C2370: 'ECPKPAR
"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 DLL and generate .def and .lib files th
"Thomas J. Hruska" wrote:
Is, IMO, easier and more informative than using Google. Results in:
apps\apps.c:if (check_winnt())
crypto\bio\bss_log.c: if (check_winnt())
crypto\cryptlib.c:if (check_winnt() && OPENSSL_isservice() > 0)
crypto\rand\rand_win.c: if (check_winnt() &&
Perrow, Graeme wrote:
I just downloaded 1.0.1k and when trying to build it on Windows (using Visual
Studio 10.0), I get a compile error:
.\crypto\cversion.c(80) : error C2065: 'cflags' : undeclared identifier
.\crypto\cversion.c(80) : warning C4047: 'return' : 'const char *' differs in
level
I'm trying to understand how the generation of ASM-files
are done on x64. (I have no problems on x86).
With the generated Nmake makefile from a
perl Configure VC-WIN64A-ONECORE
when doing a:
nmake crypto\aes\libcrypto-lib-aesni-x86_64.obj
seems to do this:
set ASM=nasm
"f:/util/Strawber
Richard Levitte wrote:
I experimented some more. I figured the "auto" does not work.
But this works:
perl crypto\aes\asm\aesni-x86_64.pl nasm > tmp-file.s
diff tmp-file.s crypto\aes\aesni-x86_64.asm
No diffs.
Why does the the generation of .asm-files be so damn hard to
figure out? Some c
"Dan Clusin" <[EMAIL PROTECTED]> wrote:
I am getting the undefined references to the OpenSSL functions in the
link stage similar to the above posting.
(don't use HTML while posting to mailing-lists).
What does the command-line (link command) looks like?
Remember the order of libs are importan
"Ken Goldman" <[EMAIL PROTECTED]> said:
> Note that both the makefile and nmake.exe are MS proprietary. You
> can't use standard makefiles with nmake, and you can't use the MS
> makefiles with a standard make.exe like gnu make.
But you can use a GNU makefile with MS tools like cl.exe. There is
On Wed, 2 Feb 2000, Robert Fernando wrote:
> when I try and compile code with the following function
>
> void sk_pop_free(STACK *st, void (*func)())
> {
..
> I get the following response form visual c ++ version 6 compiller.
>
> error C2197: 'void (__cdecl *)(void)' : too many actual paramete
The recent OpenSSL 0.9.6 snapshot (from 1-July onwards I think)
crashes ./bin/ssltest.exe. This is caused by calling a NULL-pointer
in ssl/t1_enc.c:
EVP_Cipher(ds,rec->data,rec->input,l);
This is a macro using 'ds->cipher' and 'ds->cipher->do_cipher'.
Which one is NULL I don't know. I have no
17 matches
Mail list logo