Must be SPARC-specific, all tests pass on my x86/x64 Solaris 11.4 using latest
GCC (11.2)
>-- Original Message --
>
>What Ben suggests is a great start.
>
>Note that none of the core developers have Solaris access, so that
>debugging could be problematic.
>
>
>Pauli
>
>
>On 12/9/21 1:39 pm,
>-- Original Message --
>
>
>>-- Original Message --
>>
>>On Tue, Apr 30, 2019 at 03:23:23PM -0700, Erik Forsberg wrote:
>>
>>> >Is the handshake explicit, or does the application just call
>>> >SSL_read(), with OpenSSL performing the hand
>-- Original Message --
>
>On Tue, Apr 30, 2019 at 03:23:23PM -0700, Erik Forsberg wrote:
>
>> >Is the handshake explicit, or does the application just call
>> >SSL_read(), with OpenSSL performing the handshake as needed?
>>
>> I occasionally (somewhat
I can add some of my own observations to this below ...
>> I haven't looked at the code, but my impression is that WANT_READ and
>> WANT_WRITE are returned in two cases: when OpenSSL has received or sent a
>> partial record and needs to complete it; or when the TLS state is such that
>>
I see this is Solaris 10, dont use that anywhere anymore.
But in Solaris 11, its fine. From ld(1)
-M mapfile
Reads mapfile as a text file of directives to the link-editor. This
option can be specified multiple times. If mapfile is a directory,
then all regular
hmm, been reading this whole thread.
I dont have any current issues building with Sun Studio 12.6 in 2011 mode (but
I only do Intel x86 and x86_64)
However, I do have a preference for using gcc for openssl builds though.
Do note however, that in my opinion, for Solaris, one MUST do the -R linker
There are missing comma's in ssl/t1_trce.c that causes compilation to fail.
You have to configure with enable-ssl-trace to see it though.
gcc -I. -Iinclude -I../src -I../src/include -fPIC -std=gnu90 -march=core2
-Wall -O3 -fomit-frame-pointer -pthread -DFILIO_H -DDSO_DLFCN -DHAVE_DLFCN_H
>-- Original Message --
>
> As for -lm, which symbol was undefined?
>
Undefined first referenced
symbol in file
fabs test/ct_test.o
>>>
>>> ??? One can only wonder where does it come
>-- Original Message --
>
>>> As for -lm, which symbol was undefined?
>>>
>>
>> Undefined first referenced
>> symbol in file
>> fabs test/ct_test.o
>
>??? One can only wonder where does it come from. I see no fabs
as that is the ONLY -lm reference and the fact its in test code, why not
simply avoid using fabs(), that is so trivial here ?
if (value < 0)
value = -value;
>-- Original Message --
>
>On 24/02/18 04:47 AM, Andy Polyakov wrote:
>>> So testsuite is running but this is a non-optimal debug
>-- Original Message --
>
>On 20/02/18 12:47 PM, Norm Green wrote:
>> On 2/20/2018 5:43 AM, Michael Wojcik wrote:
>>> Not by default. The comments in /usr/include/sys/feature_tests.h (on a
>>> Solaris system) explain this in excruciating detail, but in short you
>>> need either
Havent seen any.
>-- Original Message --
>
>Over the last many months, I have received a constant flow of
>"newsletters" from databreachtoday.com to my OpenSSL posting
>address.
>
>I am wondering if this is specific to me, or if they are
>sending to most other subscribers too.
>
>Enjoy
>
>Jakob
Not sure what platform the other person is using, but, for the record
the soname 1.0.0 causes big problems on Solaris 11 and up. Solaris 11
ships an OpenSSL 1.0.0 version in standard library locations, if anyone just
builds
anything higher than that, and do NOT modify build to add -R runtime
load
Starting a few days ago, www.openssl.org when clicking on the
Source tab, then selecting the GitWeb tab, redirects you to
git.openssl.org (probably ok ? ) but that page returns the
OpenSSL home page (same as www.openssl.org) so no web git access.
DNS issues perhaps ?
That triggers my memory. I saw this too a long time ago, if I recall correctly,
if you get a TLSv1.2 connection, its still logged as SSLv3 (there is lack of
printable enums in the OpenSSL code. I looked at my negotiation with wireshark
and saw that I got TLSv1.2 despite what the debug trace said.
I have a weird case that I cannot properly explain.
Using OpenSSL 1.0.1c for both client and server, I was testing various
combinations of ciphers and protocol version requests.
Basically, the server uses SSLv23_server_method().
The client code uses SSLv23_client_method() and SSL_OP_NO_SSLv2
that TLSv1 in the cipher string disables
TLSv1.2 ciphers ? I didnt expect that.
-- Original Message --
Date: Fri, 15 Jun 2012 14:34:27 -0700
From: Erik Forsberg e...@efca.com
Subject: How does cipher selection and TLS protocol negotiation interact
To: openssl-users@openssl.org
Reply-To: openssl
17 matches
Mail list logo
