similar to: [Test Problem] RSync 3.2.3 - Commit 15bc7ded

Displaying 20 results from an estimated 1000 matches similar to: "[Test Problem] RSync 3.2.3 - Commit 15bc7ded"

2025 Jan 15
1
new release 3.4.0 - critical security release
FYI: I think this is just missing #include ?rsync.h? in popt/findme.c From: rsbecker at nexbridge.com <rsbecker at nexbridge.com> Sent: January 14, 2025 10:35 PM To: rsbecker at nexbridge.com; 'rsync.project' <rsync.project at gmail.com> Cc: rsync at lists.samba.org Subject: RE: new release 3.4.0 - critical security release Another issue here in findme.c. strlcpy() is
2025 Jan 14
1
new release 3.4.0 - critical security release
This happens on NonStop x86 and ia64. I have been building/packaging Rsync for years ? almost a decade in fact. I think this happened once before this year, in fact. It is equivalent to the more portable malloc/free, which I would prefer to have in this series even if it has to be wrapped in a #if defined (__TANDEM) block. This call is considered not portable and allocates on the stack
2025 Jan 15
1
new release 3.4.0 - critical security release
I'd also note that the patches for 3.4.0 were made available to 81 different vendors via VINCE since 18th December (under embargo to give time for vendors to prepare). It is unfortunate that it didn't cover the platform you are building for. What platform is it btw? On Wed, 15 Jan 2025 at 17:57, rsync.project <rsync.project at gmail.com> wrote: > The popt changes came from
2025 Jan 14
1
new release 3.4.0 - critical security release
Here is my fix for the situation: diff --git a/popt/findme.c b/popt/findme.c index ac4cbae..4fe8a18 100644 --- a/popt/findme.c +++ b/popt/findme.c @@ -25,12 +25,23 @@ const char * findProgramPath(const char * argv0) if (path == NULL) return NULL; bufsize = strlen(path) + 1; +#if defined __TANDEM + start = pathbuf = malloc(bufsize); +#else start = pathbuf =
2025 Jan 15
1
new release 3.4.0 - critical security release
The popt changes came from upstream popt. We have Solaris and FreeBSD CI tests, along with linux, but don't have a method for testing other platforms. If you submit a PR to fix this, please consider a way we can test the fix in CI. Cheers, Tridge On Wed, 15 Jan 2025 at 14:35, <rsbecker at nexbridge.com> wrote: > Another issue here in findme.c. strlcpy() is a BSD-only method and >
2018 Apr 06
2
Announce: OpenSSH 7.7 released
On 6 April 2018 at 01:36, Randall S. Becker <rsbecker at nexbridge.com> wrote: [...] > Sorry to report that I'm having difficulty building on NonStop (built from a > git clone at 2c71ca1). Configure is failing, run as: > > configure --prefix=/usr/local --without-openssl-header-check > ... > checking for sys/un.h... yes > checking compiler and flags for sanity... no
2025 Jan 15
2
new release 3.4.0 - critical security release
Another issue here in findme.c. strlcpy() is a BSD-only method and definitely not portable. Please consider other platforms when creating patches. I can provide a patch to this patch also. Thanks, Randall From: rsync <rsync-bounces at lists.samba.org> On Behalf Of Randall S. Becker via rsync Sent: January 14, 2025 6:46 PM To: 'rsync.project' <rsync.project at
2016 Feb 10
2
Test Failure OpenSSH 7.1 P2 on HPE NSE for key-commands
On February 9, 2016 7:28 PM, Darren Tucker wrote: > To: Randall S. Becker <rsbecker at nexbridge.com> > Cc: OpenSSH Devel List <openssh-unix-dev at mindrot.org> > Subject: Re: Test Failure OpenSSH 7.1 P2 on HPE NSE for key-commands > > On Wed, Feb 10, 2016 at 10:35 AM, Randall S. Becker > <rsbecker at nexbridge.com> wrote: > > Thread split from my
2016 Feb 08
3
[Bug] Regression problem in transfer.sh for OpenSSH 7.1 P2 on HPE NSE above dd-size 32k
G'Day, I am requesting help in resolving an issue on the HPE NonStop platform in OpenSSH 7.1 P2 in the regression suite for all dd-size above 32k. Previous tests are all passing, but in the for-loop inside regress/transfer.sh, when s is 64k, the command: dd if=$DATA obs=${s} 2> /dev/null | \ ${SSH} -q -$p -F $OBJ/ssh_proxy somehost "cat >
2025 Jan 15
1
new release 3.4.0 - critical security release
Also, the patch I previously sent works correctly on x86, but not ia64. This problem is isolated to popt/findme From: rsync.project <rsync.project at gmail.com> Sent: January 15, 2025 2:11 PM To: rsbecker at nexbridge.com Cc: Perry Hutchison <pluto at agora.rdrop.com>; rsync at lists.samba.org Subject: Re: new release 3.4.0 - critical security release Is there a way I can get
2018 Jan 15
1
Rsync 3.1.3pre1 released
On Mon, Jan 15, 2018 at 6:20 AM, Randall S. Becker <rsbecker at nexbridge.com> wrote: > Incompatibility introduced at 3.1.3pre1. These are not present at master, > which compiles cleanly. > The master branch and 3.1.3pre1 were pretty much the same until just a moment ago (except that the tar files get some generated files that aren't present in git, such as the autoconf
2016 Feb 08
2
[Bug] Regression problem in transfer.sh for OpenSSH 7.1 P2 on HPE NSE above dd-size 32k
On February 8, 2016 3:30 PM, Darren Tucker wrote: > To: Randall S. Becker <rsbecker at nexbridge.com> > Cc: OpenSSH Devel List <openssh-unix-dev at mindrot.org> > Subject: Re: [Bug] Regression problem in transfer.sh for OpenSSH 7.1 P2 on > HPE NSE above dd-size 32k > > On Tue, Feb 9, 2016 at 6:36 AM, Randall S. Becker > <rsbecker at nexbridge.com> wrote:
2018 Apr 12
3
OpenSSH 7.7 t1 script breakage
On 13 April 2018 at 08:29, Josh Soref <jsoref at gmail.com> wrote: > Randall S. Becker <rsbecker at nexbridge.com> wrote: >> >> >> -REGRESSTMP = "$(PWD)/regress" >> +REGRESSTMP = `pwd` >> >> tests interop-tests t-exec unit: regress-prep regress-binaries $(TARGETS) > > > It looks like the problem is that pwd is in uppercase, not
2019 Jan 24
2
[Regression] OpenSSH 7.7p1 no longer tests on NonStop Port
On January 22, 2019 10:45, I wrote: > On January 21, 2019 19:00, Darren Tucker wrote: > > On Tue, 22 Jan 2019 at 12:01, Randall S. Becker > > <rsbecker at nexbridge.com> > > wrote: > > > > > Hi All, > > > > > > I finally got around to trying to test the 7.7p1 release on the HPE > > > NonStop Platform. 7.6p1 worked just fine - no
2018 Apr 13
2
OpenSSH 7.7 t1 script breakage
On Thu, Apr 12, 2018 at 6:29 PM, Josh Soref <jsoref at gmail.com> wrote: > Randall S. Becker <rsbecker at nexbridge.com> wrote: > >> >> -REGRESSTMP = "$(PWD)/regress" >> +REGRESSTMP = `pwd` >> >> tests interop-tests t-exec unit: regress-prep regress-binaries $(TARGETS) >> > > It looks like the problem is that pwd is in
2025 Jan 15
3
new release 3.4.0 - critical security release
Is there a way I can get access to a machine 3.4.0 is failing to build on? Maybe a VM under VirtualBox? Or some cloud service? I don't have an ia64 On Thu, 16 Jan 2025 at 01:20, <rsbecker at nexbridge.com> wrote: > On January 14, 2025 11:20 PM, Perry Hutchison wrote: > >"Randall S. Becker via rsync" <rsync at lists.samba.org> wrote: > > > >> FYI:
2018 Jan 15
1
[Bug 13224] New: New file handling causes compile issues for NonStop port.
https://bugzilla.samba.org/show_bug.cgi?id=13224 Bug ID: 13224 Summary: New file handling causes compile issues for NonStop port. Product: rsync Version: 3.1.3 Hardware: Other OS: Other Status: NEW Severity: normal Priority: P5 Component: core Assignee:
2025 Jan 14
2
new release 3.4.0 - critical security release
the alloca comes from the new popt release. What system are you having an issue with? On Wed, 15 Jan 2025 at 07:16, <rsbecker at nexbridge.com> wrote: > A new dependency was added since 3.3, alloca(), which is not portable. Is > there a way around this? > > Thanks, > > Randall > > > > *From:* rsync <rsync-bounces at lists.samba.org> *On Behalf Of
2020 Aug 29
10
[Bug 3205] New: Support HPE NonStop Server Port
https://bugzilla.mindrot.org/show_bug.cgi?id=3205 Bug ID: 3205 Summary: Support HPE NonStop Server Port Product: Portable OpenSSH Version: 8.3p1 Hardware: Other OS: Other Status: NEW Severity: enhancement Priority: P5 Component: Build system Assignee: unassigned-bugs at
2016 Feb 09
2
Test Status OpenSSH 7.1 P2 on HPE NSE
Hi All, Just reporting in on how testing has gone. After reducing obs to 32k max and banners to a max of 10000, plus some minor platform changes - root is not 0, for example, all normal tests have passed except for: multiplex - hangs at the end of this output. We had a similar issue that single reads of data were not working in dd but that does not seem to be the case in this test suite. test