Trying to compile OpenSSL using Bootlin tool chains for ARMv5 UCLIBC found at
https://toolchains.bootlin.com/
Does anyone have recent experience compiling OpenSSL 1.1.1 specifying alternate
tool-chains?
What commands did you use?
Thanks
Openssl already supports cross-compiles, since OpenWRT and Yocto/OpenEmbedded
use it as-is.
https://github.com/openwrt/openwrt/blob/master/package/libs/openssl/Makefile#L328..L357
> On May 6, 2022, at 6:25 AM, ~ Kunal Sharma ~ wrote:
>
> Hi friends,
>
> My objective is to compile OpenSSL 1.0
Hi friends,
My objective is to compile OpenSSL 1.0.2u on a Ubuntu development server
but not using the system's development infra. Instead, I need to use a
separate SDK, which in this case is WindRiver Linux SDK available on the
same server.
I'm having a hard time figuring out which config option
The cross-compilation will be performed on a server running:
Linux Splinter 2.6.32-5-686 #1 SMP Tue May 13 16:33:32 UTC 2014 i686
GNU/Linux
The 5 targets I need to make for are:
1. QNX 6.5.0, PPCBE-SPE
2. QNX 6.5.0, PPCBE
3. QNX 6.5.0, X86
4. QNX 6.3.2, PPCBE
5. QNX 6.3.2, X
On Thu, Sep 10, 2020 at 06:58 Bjoern Bidar wrote:
> It was version 1.1.1g.
What OS? I had to to some fiddling with packages and options for Debian 10
Buster to get a good compile.
I have documented my journey if you're interested.
Best regards,
-Tom
It was version 1.1.1g.
On 09/09/2020 20:43, Bjoern Bidar wrote:
> /usr/bin/ld: ./libcrypto.so: undefined reference to `OpenSSLDie'
>
What version of OpenSSL are you trying to compile? I can't seem to
replicate this.
Matt
Hey,
Is it possible to build openssl this way?
I'm current trying to build it this way to dest for deprecated API usage.
I configure openssl like this:
./Configure \
--prefix=%{_prefix} --openssldir=%{_sysconfdir}/pki/tls ${sslflags} \
zlib enable-camellia enable-seed enable-rfc3779 \
On Tue, Jul 14, 2020 at 09:08:10PM +0200, shivaramakrishna chakravarthula wrote:
> This is exactly similar to what I am looking for. I am using 1.0.2J version
> and there are some changes in the next version onwards that causes problems
> in SSL connections to older versions when DH key = 256 bytes
This is exactly similar to what I am looking for. I am using 1.0.2J version
and there are some changes in the next version onwards that causes problems
in SSL connections to older versions when DH key = 256 bytes are used. For
backward compatibility reasons, I need to continue supporting 256 bytes
On Tue, Jul 14, 2020 at 04:58:38PM +0200, shivaramakrishna chakravarthula wrote:
> Hi,
>
> I have compatibility issues for my application with new versions of OpenSSL
> and I want to use the older version of OpenSSL with my application. So, I
> want to link my application with an OpenSSL library b
That was something I have tried initially until I had problems with FIPS
mode. I have compiled OpenSSL with FIPS support. But, I see FIPS self-tests
failing when I link my application with OpenSSL static libraries.
On Tue, 14 Jul 2020 at 17:57, Michael Wojcik
wrote:
> > From: openssl-users On B
> From: openssl-users On Behalf Of
> shivaramakrishna chakravarthula
> Sent: Tuesday, 14 July, 2020 08:59
> I have compatibility issues for my application with new versions of OpenSSL
> and
> I want to use the older version of OpenSSL with my application. So, I want to
> link my application wit
Hi,
I have compatibility issues for my application with new versions of OpenSSL
and I want to use the older version of OpenSSL with my application. So, I
want to link my application with an OpenSSL library built with the custom
name so that it works fine on all systems and I can be assured of usin
> From: shivaramakrishna chakravarthula
>
> Is it possible to compile OpenSSL shared libraries with custom
> names on Linux/ Unix platforms to avoid conflicts with installed
> OpenSSL libraries?
> I have tried to modify the SHLIB_EXT in Configure script but it is
> not working. I am sure it is a
Hello,
Is it possible to compile OpenSSL shared libraries with custom names on
Linux/ Unix platforms to avoid conflicts with installed OpenSSL libraries?
I have tried to modify the SHLIB_EXT in Configure script but it is
not working. I am sure it is a common problem and someone in this group can
h
Hello,
I am trying to compile OpenSSL 1.0.2d with FIPS support on various Linux
and Unix platforms. I am building "openssl-fips-ecp-2.0.16" prior to
building OpenSSL.
I have successfully compiled the same version of OpenSSL with FIPS support
in linux-x86_64, aix64-cc, solaris64-x86_64-cc archite
* Sorry for being unclear, the goal would be to just not send the SCSV
value in the ClientHello.
Why?
Thanks for you reply Ben!
Sorry for being unclear, the goal would be to just not send the SCSV value
in the ClientHello.
-Mark
Am Di., 21. Apr. 2020 um 22:06 Uhr schrieb Benjamin Kaduk :
> On Tue, Apr 21, 2020 at 09:57:02PM +0200, Mark Windshield wrote:
> > Hello,
> >
> > I was wondering what I
On Tue, Apr 21, 2020 at 09:57:02PM +0200, Mark Windshield wrote:
> Hello,
>
> I was wondering what I'd have to change in the openssl code/config before
> compiling to have renegation disabled by default, so it won't send the
> Cipher Suite: TLS_EMPTY_RENEGOTIATION_INFO_SCSV (0x00ff) when using cur
Hello,
I was wondering what I'd have to change in the openssl code/config before
compiling to have renegation disabled by default, so it won't send the
Cipher Suite: TLS_EMPTY_RENEGOTIATION_INFO_SCSV (0x00ff) when using curl.
Thanks!
I have downloaded and ran the following configuration for OpenSSL 1.1.1.d
./config shared --prefix=/opt/test/openssl -openssldir=/opt/test/openssl
Does anyone have any idea why I receive the following error when executing
"Make"
c1: error: apps/app_rand.d: No such file or directory
make[1]: ***
Another great source is https://github.com/nabla-c0d3/trust_stores_observatory
One-stop shopping for all of apple, Android, Windows, NSS, OpenJDK, Oracle Java.
> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf Of
> Pete Cooper
> Sent: Saturday, August 24, 2019 13:10
> The `config` and subsequent `make` complete without any visible issues shown.
> However,
> /etc/php/shared/openssl/certs is an empty directory.
> Are there OpenS
I’m successfully compiling OpenSSL 1.1.1c from source for PHP-FPM to use in
preference to the system-native OpenSSL (1.0.*).
I’m installing OpenSSL 1.1.1c to /etc/php/shared/openssl with the following
configure flags (split for clarity):
./config \
--openssldir=/etc/php/shared/openssl
the configuration option
> '-static' that makes the binary as independent as possible, i.e. even
> links it with static libc.
>
> Cheers,
> Richard
>
> On Thu, 23 May 2019 08:26:43 +0200,
> Raveendra Padasalagi via openssl-users wrote:
> >
> >
>
gt;
>
>
> Any help/pointers on compiling openssl library to generate static version of
> openssl executable
> for ARM64 bit linux platform will help.
>
>
>
> Thanks,
>
> Raveendra
>
>
--
Richard Levitte levi...@openssl.org
OpenSSL Project http://www.openssl.org/~levitte/
./Configure linux-arm64 *no-shared*
make
make install
Thanks,
Raveendra
*From:* Dr Paul Dale [mailto:paul.d...@oracle.com]
*Sent:* Thursday, May 23, 2019 12:10 PM
*To:* Raveendra Padasalagi
*Cc:* openssl-users@openssl.org
*Subject:* Re: Compiling openssl executable as static binary
Link
; Any help/pointers on compiling openssl library to generate static version of
> openssl executable for ARM64 bit linux platform will help.
>
> Thanks,
> Raveendra
Hi,
Any help/pointers on compiling openssl library to generate static version
of openssl executable for ARM64 bit linux platform will help.
Thanks,
Raveendra
-- Forwarded message -
From: Thiagu Mohan
Date: Wed, Jan 23, 2019 at 4:39 PM
Subject: Re: [openssl-users] Compiling openssl 1.0.2q for OS390-Unix
To: Michael Wojcik
Yes I am using the option for Configure as OS390-Unix only and using
c89.sh from tools directory in the openssl
> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf Of
> Thiagu Mohan
> Sent: Tuesday, January 22, 2019 00:59
>
> When i tried compiling openssl 1.0.2q for OS390-Unix i got sevaeral warning
> like below but
> got the libraries libcrypto.a a
Hi,
>
> When i tried compiling openssl 1.0.2q for OS390-Unix i got sevaeral
> warning like below but got the libraries libcrypto.a and libssl.a compiled
>
> INFORMATIONAL CCN3764 /usr/include/signal.h:62Option rent is ignored
> for variable __sigign because pragma v
* FYI, I came up with following manual solution to correctly build 1.0.2l
static library with FIPS - 2.0.16 on Windows, using Visual Studio 2015. This
seems to work, and I no longer need to carry run time DLLs along with the
application. I feel this should be an acceptable solution. Does any
FYI, I came up with following manual solution to correctly build 1.0.2l static
library with FIPS - 2.0.16 on Windows, using Visual Studio 2015. This seems
towork, and I no longer need to carry run time DLLs along with the application.
I feel this should be an acceptable solution. Does anyone see
Hi,
I have am trying to compile OpenSSL 1.0.2l static library using FIPS - 2.0.16
on Windows 2012 R2, Visual Studio 2015, using reference from
https://www.openssl.org/docs/fips/UserGuide-2.0.pdf , page #68.
Step 1:
- cd openssl-fips-2.0.16
- ms\do_fips
Step 2:
- cd openssl-1.0.2l
- set FIPSDIR=C
Ok, found what happened.
For a reason that remains gloomy to me (I think this is undocumented from
POCO), POCO adds the following dependencies to the vcxproj file:
ws2_32.lib;iphlpapi.lib;libeay32.lib;ssleay32.lib;%(AdditionalDependencies)
I have removed those dependencies and it looks to be ok n
In message
on Sat, 8 Jul 2017 12:29:31 +0200, Raymi Coevan said:
raymi.coevan> Sorry, I meant no reference to libeaymt64.lib or ssleaymt64.lib
raymi.coevan>
raymi.coevan> On Sat, Jul 8, 2017 at 12:20 PM, Raymi Coevan
raymi.coevan> wrote:
...
raymi.coevan>
raymi.coevan> Indeed, the list
Sorry, I meant no reference to libeaymt64.lib or ssleaymt64.lib
On Sat, Jul 8, 2017 at 12:20 PM, Raymi Coevan
wrote:
> Hi,
>
> Indeed, the list you mentioned is exactly the one I have in my
> environment. In my MSVC project, I only statically link with
> libcrypto64MT.lib and libssl64MT.lib. No
Hi,
Indeed, the list you mentioned is exactly the one I have in my environment.
In my MSVC project, I only statically link with libcrypto64MT.lib and
libssl64MT.lib. No reference is made to libeaymt64.lib or libssl64MT.lib,
from what I know at least. So I don't understand why I got these link
erro
Hi,
In message
on Sat, 8 Jul 2017 11:19:57 +0200, Raymi Coevan said:
...
raymi.coevan> I have dependencies on Poco and OpenSSL (1.1.0e is currently used
on
raymi.coevan> MacOSX and Linux), and when trying to compile using MSVC2015, I
get
raymi.coevan> and link error telling that libeaymt64.l
Dear OpenSSL experts,
I'm a junior developer so please forgive me if this is a stupid question.
I'm trying to port an existing application, currently running on MacOSX and
Linux, to Windows 64 bits platform which is not my favorite environment.
I have dependencies on Poco and OpenSSL (1.1.0e is
>> Sorry, never mind. After taking a closer look at the source code I saw
>> that there are further compile time and run-time kernel version
>> checks in e_afalg.c. I adjusted the version number and got that to
>> work now.
>
> Well, why does the afalg engine depend on Linux 4.1?
> AF_ALG is part o
On 22/02/17 20:20, Richard Weinberger wrote:
> Am 22.02.2017 um 12:24 schrieb David Oberhollenzer:
>> Sorry, never mind. After taking a closer look at the source code I saw
>> that there are further compile time and run-time kernel version
>> checks in e_afalg.c. I adjusted the version number and
Am 22.02.2017 um 12:24 schrieb David Oberhollenzer:
> Sorry, never mind. After taking a closer look at the source code I saw
> that there are further compile time and run-time kernel version
> checks in e_afalg.c. I adjusted the version number and got that to
> work now.
Well, why does the afalg e
On 22/02/17 09:11, David Oberhollenzer wrote:
> Running readelf on afalg.so confirms that the symbol is indeed not
> in the binary. Am I missing some magic configure options or is there
> some other problem?
I just tried the exact same Configure line as you on 1.1.0e and it all
works fine:
$ re
Hi,
I'm trying to compile OpenSSL 1.1.0e with the afalg engine on a
recent CentOS 7. I removed the kernel version check for the
afalg engine from the Configure script since AFAIK the CentOS
kernel should have all of that back ported. I ran the following
configure command:
$ ./Configure linux-x86_
:
> On Sun, Feb 12, 2017 at 8:13 AM, Ajay Garg wrote:
> > Any ideas please?
> > Is compiling openssl even possible on Raspberry-Pi?
> >
>
> Try 'config' rather than 'Configure'. It looks like it does the job.
> I'm not sure why the same triplet pr
On Sun, Feb 12, 2017 at 8:13 AM, Ajay Garg wrote:
> Any ideas please?
> Is compiling openssl even possible on Raspberry-Pi?
>
Try 'config' rather than 'Configure'. It looks like it does the job.
I'm not sure why the same triplet produces different results.
It is definitely possible, because we run openssl on the Pi.
We did not, however, compile it ourselves. We install from a Pi repository.
On 2/12/2017 8:13 AM, Ajay Garg wrote:
Any ideas please?
Is compiling openssl even possible on Raspberry-Pi?
--
openssl-users mailing list
To
Any ideas please?
Is compiling openssl even possible on Raspberry-Pi?
On Sat, Jan 28, 2017 at 10:50 AM, Ajay Garg wrote:
> Hi Experts !!!
>
> Any help, please ?!!!
>
> On Sun, Jan 15, 2017 at 9:14 AM, Ajay Garg wrote:
>
>> Hi All.
>>
>> I am getting st
Hi Experts !!!
Any help, please ?!!!
On Sun, Jan 15, 2017 at 9:14 AM, Ajay Garg wrote:
> Hi All.
>
> I am getting stuck on the first step of configuring OpenSSL.
> Following are some of the diagnostics ::
>
>
> OpenSSL-Version : *1.0.2d*
>
>
> ###
Hi All.
I am getting stuck on the first step of configuring OpenSSL.
Following are some of the diagnostics ::
OpenSSL-Version : *1.0.2d*
#
pi@raspberrypi:~/instamsg-c/third_party/openssl $ *uname -a*
Linux raspberrypi 4.4.
Hello there,
1. I am trying to compile openssl libcrypto for selective ciphers only!
specifically excluding all key exchange rsa, echd, dh etc. and just compile
libcrypto with selected block/stream ciphers. What's the easiest/best way
to do this? I tried "no-" option to "Configure" but that doesn't
Someone correct me if I'm wrong, but I'm afraid it's not likely that
openssl will work for your use case. You might try wolfSSL, polarSSL, or
some purpose-built embedded encryption librarly. If you have a specific
cryptographic operation to achieve, it might help point you in the right
direction.
-
> Ping !!!
You didn't get a reply in 24 hours from an open source mailing list? A little
patience.
> Upon code-browsing, I am beginning to feel that OpenSSL uses program-buffer,
> which is used for malloc/free.
OpenSSL uses malloc, etc. Look at crypto/mem.c and (in 1.1.0 and master) the
man
ormal OSes), we generally don't have any
> heap-memory.
>
> So, what is the protocol for compiling OpenSSL for such systems?
> I am sorry, but this is the first time I would be compiling for a non-OS
> entity.
>
>
> Will be thankful for inputs.
>
>
> Thanks and
don't have any
heap-memory.
So, what is the protocol for compiling OpenSSL for such systems?
I am sorry, but this is the first time I would be compiling for a non-OS
entity.
Will be thankful for inputs.
Thanks and Regards,
Ajay
--
openssl-users mailing list
To unsubscribe: https:
On 11/11/2016 03:12, Gyumin wrote:
Dear openssl developers,
I modified openssl library to use my own static library which has
global variables.
When I run make then I can see some errors like|./libcrypto.so:
undefined reference to my_own_function|and making static libraries is
failed, but th
Dear openssl developers,
I modified openssl library to use my own static library which has global
variables.
When I run make then I can see some errors like|./libcrypto.so:
undefined reference to my_own_function|and making static libraries is
failed, but the shared libraries are compiled succe
On Tue, Nov 8, 2016 at 3:05 PM, Jakob Bohm wrote:
> On 08/11/2016 14:44, Kim Gräsman wrote:
>>
>> On Tue, Nov 8, 2016 at 2:24 PM, Michael Wojcik
>> wrote:
>>>
>>> My advice, frankly, is to study the OpenSSL build process until you
>>> understand it. We've had
>>> issues in the past with some Wind
On 08/11/2016 14:44, Kim Gräsman wrote:
On Tue, Nov 8, 2016 at 2:24 PM, Michael Wojcik
wrote:
My advice, frankly, is to study the OpenSSL build process until you understand
it. We've had
issues in the past with some Windows Perl implementations (currently we use
Cygwin Perl with
a wrapper pro
On Tue, Nov 8, 2016 at 2:24 PM, Michael Wojcik
wrote:
>
> My advice, frankly, is to study the OpenSSL build process until you
> understand it. We've had
> issues in the past with some Windows Perl implementations (currently we use
> Cygwin Perl with
> a wrapper program that corrects paths)
Forg
[not quoting anything because Outlook can't quote HTML email properly]
I build OpenSSL for static linking (though using a hacked configuration, since
it's going to be linked into a DLL, and we do not want the C RTS linked
statically). I've not seen any of these problems. We build on a variety of
Hi Kim.
Thanks for the reply.
On 8 Nov 2016 11:59 a.m., "Kim Gräsman" wrote:
>
> On Tue, Nov 8, 2016 at 6:26 AM, Ajay Garg wrote:
> >
> > Is compiling on windows always such a pain? :(
> > On Linux, it compiled perfectly the first time itself.
>
> It's worked well for me in a similar environmen
On Tue, Nov 8, 2016 at 6:26 AM, Ajay Garg wrote:
>
> Is compiling on windows always such a pain? :(
> On Linux, it compiled perfectly the first time itself.
It's worked well for me in a similar environment. I use DLL builds,
though, so `ntdll.mak` instead of `nt.mak`.
One thing that looks suspic
I tried configuring with no-asm, and then re-compiled.
Now, I get stuck at
*#error: MDC2 is disabled*
If I then *also* add no-mdc2, I get stuck at *cannot open input file
'out32\ssleay32.lib*'
Is compiling on windows always such a pain? :(
On Linux, it compiled perfectly the first time itself.
O
Oops.. sorry.
OpenSSL-version is 1.0.2d, and nasm-version is 2.12.02.
On Mon, Nov 7, 2016 at 9:31 PM, Jeremy Farrell
wrote:
> What version of OpenSSL? What version of nasm (nasm -v)? People are more
> likely to be able to help if you provide such basic information.
>
> Regards,
>
What version of OpenSSL? What version of nasm (nasm -v)? People are more
likely to be able to help if you provide such basic information.
Regards,
jjf
On 07/11/2016 11:42, Ajay Garg wrote:
Oops... pardon me.
The e) step was not done.
The errors came right after ste
perl Configure VC-WIN32 no-asm
Regards,Ishan
From: Ajay Garg
To: openssl-users@openssl.org
Sent: Monday, 7 November 2016 5:12 PM
Subject: Re: [openssl-users] Problem in compiling OpenSSL on Windows-7-32-bit
Oops... pardon me.
The e) step was not done.The errors came right after ste
Oops... pardon me.
The e) step was not done.
The errors came right after step d)
On 7 Nov 2016 3:36 p.m., "Ajay Garg" wrote:
> Hi All.
>
> Following are the steps I followed :
>
>
> ###
> a)
> Downloaded nasm.exe from
Hi All.
Following are the steps I followed :
###
a)
Downloaded nasm.exe from internet, and placed it in the include-path.
b)
*perl Configure VC-WIN32*
c)
*ms\do_nasm.bat*
d)
*nmake -f ms\nt.mak*
e)
*make*
*
> Am I missing something here?
OpenSSL 1.1.0 does not support FIPS. It's in the README.FIPS file :)
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
When compiling with FIPS, the compile terminated with a fatal error looking
for #include in the crypto/err/err_all.c code. The fips.h
header file lives in ../ssl/fips-2.0/include.openssl/fips.h.
Am I missing something here?
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/m
Hello,
Due to issue in openSSL 1.0.1l , I have to update openSSL in a project on 4
android platforms : armv7, 64 x86 & x64
I m following this guide, but having trouble compiling the 4 versions.
while I managed to build armv7, I failing building other versions
Can someone help me finding the righ
Hi,
I'm using openssl version 1.0.2d, and I'm trying to compile it with no-tls
options. Unfortunately,
every time I try to do this, I get the following error messages:
openssl: In file included from s2_meth.c:59:0:
openssl: ssl_locl.h:567:5: error: unknown type name ‘custom_ext_add_cb’
openssl: s
On 22/07/2015 13:14, Jeffrey Walton wrote:
On Wed, Jul 22, 2015 at 6:40 AM, Jakob Bohm wrote:
On 22/07/2015 01:21, Jeffrey Walton wrote:
For the stragglers, I don't think its a stretch to ask C99 in 2015.
Visual Studio is often used on Windows, and it is not C99.
Oh my, I was not aware it wa
On Wed, Jul 22, 2015 at 6:40 AM, Jakob Bohm wrote:
> On 22/07/2015 01:21, Jeffrey Walton wrote:
>
> For the stragglers, I don't think its a stretch to ask C99 in 2015.
>
> Visual Studio is often used on Windows, and it is not C99.
>
> Oh my, I was not aware it was still struggling for C99 :) I gue
On 22/07/2015 01:21, Jeffrey Walton wrote:
For the stragglers, I don't think its a stretch to ask C99 in 2015.
Visual Studio is often used on Windows, and it is not C99.
Oh my, I was not aware it was still struggling for C99 :) I guess
Microsoft is still putting their energies into the "one-si
On 22/07/2015 01:27, Jeffrey Walton wrote:
Like I said, its learning to play well with your tools :)
Well I think what your saying is that we should play well with other
people's tools! My tools (and presumably the rest of the dev team's as
well) don't report this warning.
Ah, OK. So its being
> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf
> Of Kaduk, Ben
> Sent: Tuesday, July 21, 2015 17:06
>
> On 7/21/15, 17:37, "Ken Goldman" wrote:
> >On 7/21/2015 6:20 PM, Jeffrey Walton wrote:
> >>
> >> For the stragglers, I don't think its a stretch to ask C99 in 2015.
>> Like I said, its learning to play well with your tools :)
>
> Well I think what your saying is that we should play well with other
> people's tools! My tools (and presumably the rest of the dev team's as
> well) don't report this warning.
Ah, OK. So its being reported in GCC 5.1 via -Wmaybe-uni
>> For the stragglers, I don't think its a stretch to ask C99 in 2015.
>
> Visual Studio is often used on Windows, and it is not C99.
>
Oh my, I was not aware it was still struggling for C99 :) I guess
Microsoft is still putting their energies into the "one-size, tablet
interface known as Windows 8
On 7/21/15, 17:37, "Ken Goldman" wrote:
>On 7/21/2015 6:20 PM, Jeffrey Walton wrote:
>>
>> For the stragglers, I don't think its a stretch to ask C99 in 2015.
>
>Visual Studio is often used on Windows, and it is not C99.
It is getting closer, though:
http://blogs.msdn.com/b/vcblog/archive/2013/0
On 7/21/2015 6:20 PM, Jeffrey Walton wrote:
For the stragglers, I don't think its a stretch to ask C99 in 2015.
Visual Studio is often used on Windows, and it is not C99.
___
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailma
It may be correct in this case, but "simple matter of" can sometimes
mask a real problem. If the function expected the value to be set
earlier, but the analysis tool finds a path where it's not set, there
could be a more real bug.
Is zero the right value? Why not, 1, -1, or 42?
=0 may be pe
On 21/07/15 21:44, Jeffrey Walton wrote:
> On Tue, Jul 21, 2015 at 4:06 PM, Matt Caswell wrote:
>>
>>
>> On 21/07/15 20:54, Jeffrey Walton wrote:
> ^
> d1_both.c: In function 'dtls1_retransmit_message':
> d1_both.c:1261:9: warning: 'save_write_sequence' may
On 21/07/15 21:40, Tom Browder wrote:
> On Tue, Jul 21, 2015 at 2:16 PM, Matt Caswell wrote:
>> On 21/07/15 15:33, Tom Browder wrote:
>>> On Sun, Jul 19, 2015 at 11:00 AM, Tom Browder wrote:
>>> I lied. After rebuilding gcc 5.2.0 and rechecking I get the following
>>> warnings from building 1.
> For the stragglers, I don't think its a stretch to ask C99 in 2015.
We agreed to support Netware; does it have C99? Anyone know?
___
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
On Tue, Jul 21, 2015 at 5:56 PM, Salz, Rich wrote:
> If it's a simple matter of adding "=0" in the declaration, we should just fix
> the darn thing.
>
You know... if OpenSSL changes its policies so that C99 is the
baseline, then you get to initialize all variables when declared.
I think its the
If it's a simple matter of adding "=0" in the declaration, we should just fix
the darn thing.
--
Senior Architect, Akamai Technologies
IM: richs...@jabber.at Twitter: RichSalz
___
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mai
On Tue, Jul 21, 2015 at 4:40 PM, Tom Browder wrote:
> On Tue, Jul 21, 2015 at 2:16 PM, Matt Caswell wrote:
>> On 21/07/15 15:33, Tom Browder wrote:
>>> On Sun, Jul 19, 2015 at 11:00 AM, Tom Browder wrote:
>>> I lied. After rebuilding gcc 5.2.0 and rechecking I get the following
>>> warnings fro
> I'm not real current with C so I'm not in a great position to
> criticize, but can't those warnings (if there is truly no problem) be
> eliminated (at least in gcc) with a pragma?
>
Sadly, no.
GCC pragmas to manage warnings are almost useless. Its been broken for
years. See:
* https://gcc.gnu
On Tue, Jul 21, 2015 at 4:06 PM, Matt Caswell wrote:
>
>
> On 21/07/15 20:54, Jeffrey Walton wrote:
^
d1_both.c: In function 'dtls1_retransmit_message':
d1_both.c:1261:9: warning: 'save_write_sequence' may be used
uninitialized in this function [-Wmayb
On Tue, Jul 21, 2015 at 2:16 PM, Matt Caswell wrote:
> On 21/07/15 15:33, Tom Browder wrote:
>> On Sun, Jul 19, 2015 at 11:00 AM, Tom Browder wrote:
>> I lied. After rebuilding gcc 5.2.0 and rechecking I get the following
>> warnings from building 1.0.2d:
>>
>> d1_both.c: In function 'dtls1_retr
On 21/07/15 20:54, Jeffrey Walton wrote:
>>> ^
>>> d1_both.c: In function 'dtls1_retransmit_message':
>>> d1_both.c:1261:9: warning: 'save_write_sequence' may be used
>>> uninitialized in this function [-Wmaybe-uninitialized]
>>> memcpy(s->s3->write_sequence, sa
>> ^
>> d1_both.c: In function 'dtls1_retransmit_message':
>> d1_both.c:1261:9: warning: 'save_write_sequence' may be used
>> uninitialized in this function [-Wmaybe-uninitialized]
>> memcpy(s->s3->write_sequence, save_write_sequence,
>> ^
>
> This one is
On 21/07/15 15:33, Tom Browder wrote:
> On Sun, Jul 19, 2015 at 11:00 AM, Tom Browder wrote:
>> On Thu, Jul 9, 2015 at 12:00 PM, Viktor Dukhovni
>>> That surely means that you're compiling some patched version or
>>> not even 1.0.2d.
>>
>> No, it's the correct version.
>>
>> But just now, after
On Sun, Jul 19, 2015 at 11:00 AM, Tom Browder wrote:
> On Thu, Jul 9, 2015 at 12:00 PM, Viktor Dukhovni
>> That surely means that you're compiling some patched version or
>> not even 1.0.2d.
>
> No, it's the correct version.
>
> But just now, after building gcc-5.2.0 and using it to rebuild
> open
On Thu, Jul 9, 2015 at 12:00 PM, Viktor Dukhovni
wrote:
> On Thu, Jul 09, 2015 at 11:50:25AM -0500, Tom Browder wrote:
>> On Thu, Jul 9, 2015 at 10:22 AM, Viktor Dukhovni
>> wrote:
>> > On Thu, Jul 09, 2015 at 09:47:00AM -0500, Tom Browder wrote:
>> Yes, and you're right about the function--weird
1 - 100 of 400 matches
Mail list logo
