On July 20, 2022 6:07 AM, Mühlstrasser wrote:
>I found the following entry in the release notes for curl 7.82.0:
>
>TPF: drop support
>https://github.com/curl/curl/pull/8378
>
>With that the code related to CURL_DOES_CONVERSIONS was removed.
>
>Do I understand it correctly that EBCDIC support is go
On July 20, 2022 10:02, Patrick Monnerat wrote:
>On 7/20/22 15:06, Randall via curl-library wrote:
>> On July 20, 2022 6:07 AM, Mühlstrasser wrote:
>>> I found the following entry in the release notes for curl 7.82.0:
>>>
>>> TPF: drop support
>&g
Was https://github.com/curl/curl/issues/9285
Originally opened by Ben Voris. The request was to have curl support OpenSSH
config specifications. I am opening a discussion on this subject from the
above case. The ask is whether it would make sense to have an option to
allow curl to honor ~/.ssh/con
Hi Curl,
I'm having some difficulties trying to build curl in 64 bits (big endian) on
NonStop. It works fine, with only 3 minor issues in 32-bit but when
compiling for 64-bit, a whole bunch of issues come up:
TESTFAIL: These test cases failed: 9 39 41 44 64 65 70 71 72 88 153 154 158
163 166 167
On September 10, 2022 5:38 PM, Daniel Stenberg wrote:
>On Fri, 9 Sep 2022, Randall via curl-library wrote:
>
>> I'm having some difficulties trying to build curl in 64 bits (big
>> endian) on NonStop. It works fine, with only 3 minor issues in 32-bit
>> but when compil
>From: Daniel Stenberg
>On Sat, 10 Sep 2022, rsbec...@nexbridge.com wrote:
>
>>> $ ./runtests.pl -g 9
>>
>> This gives me:
>>
>> test 0009...[HTTP RFC1867-type formposting] Can't exec "--directory":
>> No such file or directory at ./runtests.pl line 624.
>>
>> 9: protocol FAILED!
>>
>> To debug,
On September 11, 2022 5:07 AM, Daniel Stenberg wrote:
>On Sat, 10 Sep 2022, rsbec...@nexbridge.com wrote:
>
>> With that, the stack trace on SIGSEGV is:
>>
>> Process (2,981) received non-deferrable signal SIGSEGV (number: 11)
>> (xInspect 2,981):bt
>> #0 0xf11d9ccc in memcpyHP ()
>> #1 0
On September 11, 2022 7:04 PM, Daniel Stenberg wrote:
>On Sun, 11 Sep 2022, rsbec...@nexbridge.com wrote:
>
>> TESTFAIL: These test cases failed: 1119 1167
>>
>> 1119 failed (not a new breakage) because the script tried to run CC
>> without taking into account the supplied options from Configure,
>
On October 26, 2022 2:26 AM, Daniel Stenberg wrote:
>This time, we announce no less than four security advisories in association
with
>this release. Stay tuned for them in separate emails.
>curl and libcurl 7.86.0
We can no longer build curl on HPE NonStop because of a configure
restriction:
chec
On October 26, 2022 8:32 AM, Daniel Stenberg wrote:
>On Wed, 26 Oct 2022, rsbec...@nexbridge.com wrote:
>
>> checking size of curl_off_t... 4
>> checking for long long... yes
>> configure: error: support for systems without 64 bit curl_off_t is
>> deprecated, use --with-n64-deprecated until then
>>
On October 26, 2022 9:32 AM, Daniel Stenberg wrote:
>On Wed, 26 Oct 2022, rsbec...@nexbridge.com wrote:
>
>>> The curl_off_t type is determined in the curl/curl.h header but
>>> seeing this output above, it seems to indicate that it needs
>>> adjustment for HPE NonStop.
>>
>> The c99 interpretation
>-Original Message-
>From: Daniel Stenberg
On October 26, 2022 10:12 AM, Daniel Stenberg wrote:
>On Wed, 26 Oct 2022, rsbec...@nexbridge.com wrote:
>
>> Snippet to do that:
>>
>> #if defined __TANDEM
>> typedef long long curl_off_t;
>> #endif
>>
>> Best place to do that? In configure or
On October 26, 2022 3:07 PM, Dan Fandrich wrote:
>On Wed, Oct 26, 2022 at 10:26:40AM -0400, Randall via curl-library wrote:
>> If we build under 64-bit, which is scheduled later in the year, then
>> there is no need to override the defaults. Do you want a PR for this?
>
>K
On October 26, 2022 4:48 PM, Daniel Stenberg wrote:
>On Wed, 26 Oct 2022, Randall via curl-library wrote:
>
>> In my view , the change at 7.86.0 to force 64-bit only constitutes an
>> ABI break.
>
>That's not a change in 7.86.0.
>
>The change in 7.86.0 is that co
On October 26, 2022 6:15 PM, Daniel Stenberg wrote:
>On Wed, 26 Oct 2022, rsbec...@nexbridge.com wrote:
>
>> This will generate a 64-bit curl_off_t, which as I understand from
>> other replies it is wrong for 32-bit builds. long long is invariant,
>> being always 64-bit regardless of the memory mod
On October 27, 2022 5:30 PM, Daniel wrote:
>A regression in the noproxy filter functionality in 7.86.0 has been
suggested to be
>reason enough for a patch release:
>
> https://github.com/curl/curl/issues/9813
>
>We don't yet have any stated policy for how to judge when a bug is reason
>enough for
Hi Curl,
I have a curl built with OpenSSL. The built of OpenSSL uses hardware
randomization on the platform using _rdrand64(). When I use libcurl,
typically through git, I end up with an open to PRNGD, which is not
desirable. I'm wondering whether there is a configuration setting that I am
missing
On Sunday, March 5, 2023 4:21 PM, Daniel Stenberg wrote:
>On Sun, 5 Mar 2023, Randall via curl-library wrote:
>> I have a curl built with OpenSSL. The built of OpenSSL uses hardware
>> randomization on the platform using _rdrand64(). When I use libcurl,
>> typically through
On Monday, March 6, 2023 8:08 AM, Cristian Rodríguez wrote:
>On Sun, Mar 5, 2023 at 1:33 PM Randall via curl-library
>
>wrote:
>> I have a curl built with OpenSSL. The built of OpenSSL uses hardware
>> randomization on the platform using _rdrand64(). When I use libcurl,
>
On Monday, March 6, 2023 3:21 PM, Cristian Rodríguez wrote:
>On Mon, Mar 6, 2023 at 10:54 AM wrote:
>
>> This platform has limited porting capabilities. The Xeon x86 HRNG is highly
>> stable
>and verified on this platform - this is not one of the flakey HRNG processors.
>Its use
>has passed all
On Monday, March 6, 2023 5:20 PM, Daniel Stenberg wrote:
>On Mon, 6 Mar 2023, Randall via curl-library wrote:
>
>> Is the answer that hardware RNG is not supported by curl at all?
>
>No, curl does not support hardware RNG.
>
>curl uses the TLS library's random functi
Hi Curl Team,
I am building curl 8.2.1 for NonStop and received the following message:
*** Warning: Trying to link with static lib archive
/usr/coreutils/lib/libz.a.
*** I have the capability to make that library automatically link in when
*** you link to this library. But I can only do this if
t 03:27:34PM -0400, Randall via curl-library wrote:
>> ln: failed to create hard link '.libs/libcurl.lax/lt1-libz.a' =>
>> '/usr/coreutils/lib/libz.a': Cross-device link
>
>This looks like a bad assumption on the part of libtool that a hard link is
possible.
On Wednesday, August 30, 2023 5:56 PM, Dan Fandrich wrote:
>On Wed, Aug 30, 2023 at 05:03:34PM -0400, rsbec...@nexbridge.com wrote:
>> Actually, there is no libtool on the platform, so upgrading will be
>> difficult. No LIB, INCLUDES, or other compile-related environment variables.
>
>Then it will
On Wednesday, August 30, 2023 5:56 PM, Dan Fandrich wrote:
>On Wed, Aug 30, 2023 at 05:03:34PM -0400, rsbec...@nexbridge.com wrote:
>> Actually, there is no libtool on the platform, so upgrading will be
>> difficult. No LIB, INCLUDES, or other compile-related environment variables.
>
>Then it will
On Wednesday, August 30, 2023 7:43 PM, Fandrich wrote:
>On Wed, Aug 30, 2023 at 06:08:38PM -0400, rsbec...@nexbridge.com wrote:
>> Unfortunately, the packaging team for the platform did not help on this
one. zlib.h
>is in the /usr/coreutils/include directory, the zlib.a, zlib.so,
zlib.so.1.2.11 are
On Thursday, August 31, 2023 1:41 PM, Dan Fandrich wrote:
>On Thu, Aug 31, 2023 at 11:09:58AM -0400, Jeffrey Walton via curl-library
wrote:
>> I think you should change strategies. You should use sed to change
>> references from -lz to libz.a (and friends).
>
>While that would work, devs shouldn't
On Wednesday, August 30, 2023 7:43 PM, Dan Fandrich wrote:
>On Wed, Aug 30, 2023 at 06:08:38PM -0400, rsbec...@nexbridge.com wrote:
>> Unfortunately, the packaging team for the platform did not help on this
one. zlib.h
>is in the /usr/coreutils/include directory, the zlib.a, zlib.so,
zlib.so.1.2.11
On Friday, September 1, 2023 2:39 PM, Dan Fandrich wrote:
>On Fri, Sep 01, 2023 at 01:53:27PM -0400, rsbec...@nexbridge.com wrote:
>> Slight change, please. The i386 should be x86 (and eventually x86_64
>> when I get the 64-bit builds working).
>
>i386 is a historical tag that basically means 32-bi
On Thursday, September 28, 2023 3:03 AM, Volker Schmid wrote:
>Am 27.09.23 um 23:37 schrieb Ray Satiro via curl-library:
>> On 9/25/2023 9:59 AM, Volker Schmid via curl-library wrote:
>>> we are using libcurl in version 7.71.1 (32 bit) on Windows to send
>>> email using SMTP. The login fails to som
The dependency just added for libpsl breaks builds where the library does
not exist - for example, the latest NonStop OS from August 2023.
checking for library containing psl_builtin... no
configure: error: libpsl was not found
This seems entirely like it could be isolated to ./configure or
./con
On Wednesday, January 31, 2024 11:55 AM, Sam James wrote:
>Randall via curl-library writes:
>
>> The dependency just added for libpsl breaks builds where the library
>> does not exist - for example, the latest NonStop OS from August 2023.
>>
>> checking for librar
On Wednesday, January 31, 2024 1:08 PM, Frank Gevaerts wrote:
>On Wed, Jan 31, 2024 at 12:47:42PM -0500, Randall via curl-library wrote:
>>
>> Thanks. That seems to have made a positive difference. Would it not
>> make sense to automatically switch this off if the lib
On Wednesday, January 31, 2024 4:57 PM, Daniel Stenberg wrote:
>On Wed, 31 Jan 2024, Randall via curl-library wrote:
>
>> Having a dependency like this, that is not trivially portable leading
>> to security issues in future, is rather problematic, don't you agree?
>
&g
On Wednesday, January 31, 2024 4:57 PM, Daniel Stenberg wrote:
>On Wed, 31 Jan 2024, Randall via curl-library wrote:
>
>> Having a dependency like this, that is not trivially portable leading
>> to security issues in future, is rather problematic, don't you agree?
>
&g
On Thursday, July 4, 2024 2:51 PM, Dan Fandrich wrote:
>As it is, I don't think wcurl adds substantial enough value to carry along
upstream.
>Right now, it doesn't do much beyond setting a few standard options on curl
itself,
>which people can do themselves already in a number of different ways to
Hi Curl Team,
I have a situation where I have a proxy using libcurl taking commands from
git. The connection is failing but I cannot determine why. What would help
is being able to turn on verbose output in libcurl. The difficulty I have I
that the code is not within my control. Is there a command
On Wednesday, July 10, 2024 5:47 AM, Daniel Stenberg wrote:
>On Tue, 9 Jul 2024, Randall via curl-library wrote:
>
>> I have a situation where I have a proxy using libcurl taking commands
>> from git. The connection is failing but I cannot determine why. What
>> would help
The introduction of the use of ss_family is not necessarily portable and causes
breakages on NonStop (among others). What is the best way to suppress, get
past, this? Undefining IP_TOS is not an option as this is defined by the
operating system. I have sun_family, but not ss_family.
TIA,
Randal
On Wednesday, July 24, 2024 10:47 AM, I wrote:
>The introduction of the use of ss_family is not necessarily portable and
causes
>breakages on NonStop (among others). What is the best way to suppress, get
past,
>this? Undefining IP_TOS is not an option as this is defined by the
operating system.
>I
>-Original Message-
>From: rsbec...@nexbridge.com
>Sent: Wednesday, July 24, 2024 10:50 AM
>To: rsbec...@nexbridge.com; 'libcurl development'
>Subject: RE: [Breakage] curl 8.9.0 tool_operate.c introduces use of
ss_family
>
>On Wednesday, July 24, 2024 10:47 AM, I wrote:
>>The introduct
On Wednesday, July 24, 2024 6:17 PM, Daniel Stenberg wrote:
>On Wed, 24 Jul 2024, Randall via curl-library wrote:
>
>> I can make a formal PR if requested.
>
>Please do and we can take it from there.
>
>Note that POSIX [*] says:
>
> "The sockaddr_storage s
On February 5, 2025 3:20 AM, Daniel Stenberg wrote:
>I'm happy to announce a brand new curl release. This time in association
with three
>separate security advisories that will follow shortly.
We encountered a new issue at 8.12.0 that was not in 8.11.0. Configure is
failing
as follows on HPE NonSt
On February 5, 2025 9:23 AM, I wrote:
>On February 5, 2025 3:20 AM, Daniel Stenberg wrote:
>>I'm happy to announce a brand new curl release. This time in
>>association
>with three
>>separate security advisories that will follow shortly.
>
>We encountered a new issue at 8.12.0 that was not in 8.11.0
On January 12, 2025 5:59 PM, Daniel Stenberg wrote:
>On Sun, 12 Jan 2025, Ray Satiro via curl-library wrote:
>
>> If you're building libcurl for an embedded device that only talks to
>> an HTTP server then maybe you would skip TLS support.
>
>Sure, that's why the ability is there.
>
>Now I am askin
On March 17, 2025 2:43 PM, I wrote:
>On March 17, 2025 11:30 AM, Daniel Stenberg wrote:
>>Hello friends!
>>
>>Welcome to the second 8.13.0 release candidate: rc2.
>>
>>Please try this release candidate in your use cases and products and
>>verify that everything works as intended.
>>
>>Please try th
On March 17, 2025 11:30 AM, Daniel Stenberg wrote:
>Hello friends!
>
>Welcome to the second 8.13.0 release candidate: rc2.
>
>Please try this release candidate in your use cases and products and verify
>that everything works as intended.
>
>Please try the new features and options and verify that th
On March 8, 2025 4:28 AM, Daniel Stenberg wrote:
>Hello friends!
>
>Welcome to the first 8.13.0 release candidate: rc1.
>
>Today is the first day of the feature freeze, meaning that all changes and
new
>features that are introduced in the pending release have been merged
already and
>should work.
>
On May 21, 2025 2:02 AM, Daniel Stenberg wrote:
>In preparing for the actual release, rc3 has been uploaded and made
available
>for testing on https://curl.se/rc/.
Build/tests on NonStop x86 for OpenSSL 3.0 to 3.5 all succeeded for rc1-3.
Thanks!
--Randall
--
Unsubscribe: https://lists.haxx.se/
On June 21, 2025 5:56 AM, Daniel Stenberg wrote:
>There is a fresh rc1 build of the coming curl 8.15.0 release uploaded and
made
>available for testing on https://curl.se/rc/.
>
>Please consider taking this for a spin and verify that everything seems to
work
>as they should. All the new features fo
On August 18, 2025 2:00 AM, Daniel Stenberg wrote:
>Hello,
>
>This is the first (of three) release candidate for the coming curl 8.16.0.
>Uploaded and available for testing on https://curl.se/rc/.
>
>Please take this one for a spin and verify that everything seems to work as
they
>should. All the n
On August 20, 2025 5:31 PM, Daniel Stenberg wrote:
>On Wed, 20 Aug 2025, rsbec...@nexbridge.com wrote:
>
>> To avoid confusion, it is not OpenSSL v3.0 being dropped. It is the
TLS/SSL
>> v3 protocol that is going away.
>
>No. I'm asking if there is any point in keeping support for any OpenSSL
>*bef
On August 20, 2025 5:12 PM, Daniel Stenberg wrote:
>To: libcurl hacking
>The OpenSSL project themselves doesn't support any version before 3.0, so
>presumably there are also no security updates for older versions anymore
etc.
>That makes them insecure options to use.
>
>Is there any reason we shou
On August 18, 2025 10:43 PM, Dan Fandrich wrote:
>On Mon, Aug 18, 2025 at 09:13:10PM -0400, Randall via curl-library wrote:
>> It is a problem because I am building curl for OpenSSL 3.5, not 1.0.2,
>> which is sitting In /usr/local/lib.
>
>Can't you add the path to the
On August 18, 2025 6:38 PMm Daniel Stenberg wrote:
>On Mon, 18 Aug 2025, rsbec...@nexbridge.com wrote:
>
>> I noticed that some of the tests are reporting the use of
>> /usr/local/bin/openssl when building for alternate locations (e.g.,
>> /usr/local-ssl3.4).
>
>Sure, but why is that a problem? Run
55 matches
Mail list logo
