Hello, I've compiled openssl.1.0.2h on osx (32bit) and linked staticly my
project with libcrypto.a and libssl/a, but I get 2 linking errors with
"Symbol(s) not found":
_TLSv1_2_method, referenced from ...
and
_BIO_test_flags, referenced from ...
Why would this be happening?
ps: (same code
..
it seems there is an object maybe missing from when it was linked.
Any help or suggestion would be greatly appreciated
Thank you in advance
On Wed, Jun 8, 2016 at 5:29 PM, Dan S <danc...@rebelbase.com> wrote:
> Hello, I've compiled openssl.1.0.2h on osx (32bit) and linked staticly my
ssl that came with 10.6 :(
So I may just use the renamed files if I can't figure out how to tell the
xcode to ignore the system libraries
Thank you for helping look into this for me
On Mon, Jun 13, 2016 at 1:16 PM, Dan S <danc...@rebelbase.com> wrote:
> sorry forgot to mantion t
the paths before compiling
openssl, make had issues installing across paths with spaces)
On Sun, Jun 12, 2016 at 2:24 AM, Axel Luttgens <axel.luttg...@skynet.be>
wrote:
> > Le 9 juin 2016 à 02:29, Dan S a écrit :
> >
> > Hello, I've compiled openssl.1.0.2h on osx (32bit)
sorry forgot to mantion that after linking with all the paths set it
produces the single error (one from before: Symbol(s) not found
_TLS1_2_method referenced from _main in main.o
On Mon, Jun 13, 2016 at 1:14 PM, Dan S <danc...@rebelbase.com> wrote:
> I did this step at a time to
You can look into modifying the window size for transmission (likely
devastating your throughput, considering it will have to drop from around
usual 64K to about a tenth of the size - mostly notably with the increase
of ACKs and header repetition with each packet ... falls too far and it
will
less headache static linking to SSLEAY32 and LIBEAY32 :), depending on how
many windows versions you want to support, static linking to WS2_32 and
CRYP32 may also be useful (though linking all 4 nearly tripled the binary
for what we needed to have included), but don't have to worry about what
Hello,
Instead of using SSL_CTX_load_verify_locations with a file, we load the
data from dll resource (multiple certs separated by -BEGIN
CERTIFICATE- -END CERTIFICATE-):
...
if(pdata = (BYTE *)LockResource( hglobal )) { // BYTE *pdata, hglobal
is initialized with
I thought there is anything that would stop you from compiling with
everything and make choices at run time, (TLSv1_2_method, TLSv1_1_method,
TLSv1_method, SSLv23_method etc... just set the right flags and cyphers)
On Wed, Nov 16, 2016 at 2:58 PM, craig_we...@trendmicro.com <
internal file structure of iOS app is well defined with API to access the
directories without any hacks (I assume you weren't looking to access a
directory outside of your app)
10 matches
Mail list logo
