similar to: openssh 3.1 and rsync dont work

We have AIX 4.3.3 ML09 and AIX 5.1 ML01 I have narrowed the problem down, it is nothing to do with uni/multiprocessor machines. Both rsync 2.3.1 compiled by Bull in an installp and a gcc compiled version of 2.4.5 ( by me ) both have exactly the same problem with SSH 3.1.p1 and both DONT have the problem with SSH 2.9.9p1 - so I assume this is something highly specific to SSH 3.1.1.p1 Hope this

Can I get people from other platforms to test the waitpid.patch to see if it solves hang-on-exit on their platform? I can confirm Solaris at this moment (but I've not done heavy testing at this moment) that is works like a charm (Solaris 7). It handles 'sleep 90&' vs 'nohup sleep 90&' correctly (killed, vs left). thanks. - Ben ---------- Forwarded message

Hi, I wanted to have access to the openssh-3.x source in which the bugs were reported. For instance, one of the problems reported in openssh-3.1 was *Bug 182* <https://bugzilla.mindrot.org/show_bug.cgi?id=182> - ssh should still force SIGCHLD to be SIG_DFL when calling ssh-rand-helper When I download openssh-3.1p1, I see the bug fixed. I would like to

Peter Dimitrov and myself were debugging a very peculiar bug when libguestfs is run as a plugin from collectd: https://www.redhat.com/archives/libguestfs/2018-November/thread.html#00023 The long story short is that collectd leaks SIGCHLD == SIG_IGN setting into plugins: https://www.redhat.com/archives/libguestfs/2018-November/msg00095.html This means that any plugin that does the usual

http://bugzilla.mindrot.org/show_bug.cgi?id=182 Summary: ssh should still force SIGCHLD to be SIG_DFL when calling ssh-rand-helper Product: Portable OpenSSH Version: 3.1p1 Platform: ix86 OS/Version: All Status: NEW Severity: normal Priority: P3 Component: ssh AssignedTo:

On Tue, Nov 13, 2018 at 10:04:33AM +0000, Daniel P. Berrangé wrote: > On Fri, Nov 09, 2018 at 12:19:30PM +0000, Richard W.M. Jones wrote: > > Peter Dimitrov and myself were debugging a very peculiar bug when > > libguestfs is run as a plugin from collectd: > > > > https://www.redhat.com/archives/libguestfs/2018-November/thread.html#00023 > > > > The long

Hi list, I have 3 Citrix Xenserver 5.6  and currently building a a VM backup server. I took the xe client on one of the server and installed it on the backup server (gentoo based) installed the stunnel package to make XE work. now when running, I get this error message : [server ­~ #] ./xe help -debug -s 192.168.111.17 -u user -pw pass Connecting via stunnel to [192.168.111.17] port [443]

Using --existing, I would like to transfer files created by root to home dirs, where the files would be updated, but leave the user,group and perms as they were. ie root creates a new file on the sending system, rsyncs it to the home dir of the user, leaving the perms untouched. Seems there is no option for this - the users are not defined on the sending system. I cant do it backwards due to

Here are strace outputs per process. strace_output.22076 is the plugin's pid. (A little before forking) strace_output.22077 runs qemu-img strace_output.22078 is a mystery to me strace_output.22079 is rm -rf to the overlay image and its temporary dir. Best Regards, Peter On Wed, Nov 7, 2018 at 4:38 PM Richard W.M. Jones <rjones@redhat.com> wrote: > On Wed, Nov 07, 2018 at

This patch is against Cray patch against openssh-SNAP-20010710. Here a few notes about them: 1) rijndael does not work on cray due to the fact it is rooted in 32 bits. I looking for a fix, it may come form Wendy Palam. For now the cray default to the following cihpers for ssh version 2 ssh are: 3des-cbc,blowfish-cbc,cast128-cbc,arcfour 2) Crays don't have setitimer so I

Rsync maintainers please review rsync bug https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=98740 The code in question is in socket.c in start_accept_loop. The user is getting these warning messages:

I have been having problems with syslinux not working on one system. The error message was "failed to create ldlinux.sys". I checked and mcopy was installed. But upon further investigation I finally found the problem. I were starting syslinux for python (2.4) and in the python code I made it ignore SIGNCHLD. It turns out that this signal state was inherited by syslinux and it made

Commit 8418552 ("[klibc] ia64: Fix shared build") missed this use of the GP register, although the code appears to have been dubious anyway, assuming the address of errno was the first thing pointed to by GP. --- usr/klibc/arch/ia64/vfork.S | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/usr/klibc/arch/ia64/vfork.S b/usr/klibc/arch/ia64/vfork.S index

Please find enclosed two patches for OpenSSH 3.1p1. The first patch solves a problem where sessions will be left "hanging" when you normally exit from a ssh shell (for example by logging out from the remote host via "exit" or "logout"). The problem seems to be that sshd (and some other parts of OpenSSH) doesn't check the return code and errno from waitpid() for

Hi, thank you very much for reporting this! Sounds like a bug in the exec plugin – it never ceases to amaze me how many issues a single plugin can have ;) > > > This means that any plugin that does the usual pattern of: > > > > > > pid = fork (); Note that the exec plugin is the *only* plugin that does this. All other plugins are forbidden to fork(), popen() or

This took longer than it should have. Icecast 1.3.9 fixes all the known security problems, and also adresses many that weren't reported, thanks to a code audit by John Viega. If you for some reason have problems with 1.3.9 that prevent you from using it, please, please, please make sure you don't run icecast as root, or make sure you have patched the problem areas yourself. Along with

This took longer than it should have. Icecast 1.3.9 fixes all the known security problems, and also adresses many that weren't reported, thanks to a code audit by John Viega. If you for some reason have problems with 1.3.9 that prevent you from using it, please, please, please make sure you don't run icecast as root, or make sure you have patched the problem areas yourself. Along with

While nbdkit itself must run with SIGPIPE ignored, many applications expect to inherit SIGPIPE in the default state. What's worse, POSIX states that a non-interactive shell script cannot use 'trap' to undo an inherited SIG_IGN on SIGPIPE. I have seen several bug reports over the years of something that works for a developer but fails under a CI environment, where the root cause was

Hi! I'm unable to write with remote rsync in daemon mode. ********* My configuration: rsync 2.6.2 Linux 2.4.20-alt16-up (ALTLinux www.altlinux.org) (There is owl-patch in ALTLinux-kernel) ========== /etc/rsyncd.conf ============= log file = /var/log/rsync [routers] comment = Our Backups path = /mnt/backup/routers uid = archiver gid = archiver use chroot = true read only = false list = true

Hello, I have several systems which I recently updated with yum -y update to all the latest packages. These systems use yum-priorities and use the CentOS (priority 1) EPEL (priority 5) and rpmforge (priority 10) repositories. After the updates, dhcpd stopped working with a SIGPIPE error which occurs shortly after it attempts to fork into the background. I worked around that problem by building