similar to: [Bug 1905] New: check_parent_exists() logic does not cover all cases

The check_parent_exists() function in ssh-agent.c does this: if (parent_pid != -1 && kill(parent_pid, 0) < 0) however, the kill can fail with EPERM even if the parent_pid exists. For example, consider this command: ssh-agent sh -c 'ssh-add ; exec sudo sh -i' The original ssh-agent process sets things up so that the "sh -c '...'" process is

I regularly use ssh-agent with a subcommand; my X11 session is spawned through ssh-agent, and sometimes i'll run a special agent for a certain subset of commands, like this: ssh-agent bash ... and then do work within that shell. From the man page: > If a commandline is given, this is executed as a subprocess of the agent. > When the command dies, so does the agent. But

https://bugzilla.mindrot.org/show_bug.cgi?id=3181 Bug ID: 3181 Summary: ssh-agent doesn't exit automatically after child program exits Product: Portable OpenSSH Version: 8.0p1 Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 Component: ssh-agent

This refactors existing code to close file descriptors in the recovery process, and also adds code to close file descriptors between the fork() and exec() of QEMU or User-Mode Linux. The reason is to avoid leaking main process file descriptors where the main process (or other libraries in the main process) are not setting O_CLOEXEC at all or not setting it atomically. Python is a particular

Hi Richard, I see this patch is included into libguestfs >= 1.26.6 & libguestfs >= 1.27.24. I feel that version is too high. Now RHEL 7.0 runs libguestfs-1.22.6, RHEL 6.6 alpha and 6.5 runs libguestfs-1.20.11. Is that possible to backport this patch, in order to make this problem fixed in RHEL 7.0, 6.6, and 6.5? Thanks & Best Regards Qin Zhao (赵钦) China System and Technology Lab,

From: "Richard W.M. Jones" <rjones at redhat.com> If the parent process uses a pipe (or any fd, but pipes are a particular problem), then the recovery process would hold open the file descriptor(s) of the pipe, meaning that it could not be fully closed in the parent. Because the recovery process doesn't use exec(2), this wasn't avoidable even using FD_CLOEXEC. Avoid this

http://www.core-sdi.com/advisories/ssh1_sessionkey_recovery.htm includes the line of code: kill(SIGALRM, getppid()); This is contained within what is listed as an "unsupported and untested patch" developed by SSH.com. The problem is that the arguments to "kill" are in the wrong order. In other words, to obtain the effect that was apparently intended, the line of code

The following patch allows OpenSSH 2.2.0-p1 to be started (and managed) from /etc/inittab (by "init") on systems which support that. This is useful when you *really* want SSHD to always run since it will be automatically restarted by "init" if it dies (and if "init" dies the the systems dies :-). I use a line (in /etc/inittab) like this on Solaris systems:

This adds support for systemd socket-based activation in the ssh-agent. When using socket activation, the -a flag value must match the socket path provided by systemd, as a sanity check. Support for this feature is enabled by the --with-systemd configure flag. --- Something tells me upstream would not be interested in this patch, but as it may be useful on linux, I'm submitting it here.

openssh-2.9.9p2 assumes that pid_t, uid_t, gid_t, and mode_t are no wider than int. GCC complains about this assumption on 32-bit Solaris 8 sparc, where these types are 'long', not 'int'. This isn't an actual problem at runtime on this host, as long and int are the same width, but it is a problem on other hosts where pid_t is wider than int. E.g., I've heard that 64-bit

Hi, I know this is know thing about the java windows being blank. I also kinda guess that it is not a priority to get it fixed to a lot of you ppl. So, I'm here to help! :) It's really pain to be using Xnest and all those to work with java-swing development, and I'd like to see this fixed. There was nothing of this in the archives, so whats the plan? Anybody working on

Hi Tested if i could upgrade my kyocera drivers but no go.. ( where i have currently 6.3.909.0 installed. ) Tried/Tested with win10 and win7 x64. ( 4.9.6 ) with the windows printer manager. ( as shown on the wiki ) KyoceraClassicUniversal v3.3_signed KX_741525_UPD_signed_EU All get : HRESULT: 0x0000023f (ERROR_APP_INIT_FAILURE) ( see below ) Tested them all, and atm only one works..

https://bugzilla.redhat.com/show_bug.cgi?id=1123007 This is version 2 of the patch which avoids incorrectly closing stderr, so we can still see debug and error messages. Rich.

The Find/Replace dialog got broken on Windows back when we reparented everything. Attached is a patch to conditionally included some things needed for Windows. Roy _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org http://rubyforge.org/mailman/listinfo/wxruby-users

Hi, Am 25.03.2019 um 14:12 schrieb Marco Gaiarin via samba: > [...] > Some drivers there's no way to load (for example, some samsung MFP). > Some other load, but you have to do 2-5 try before they work. I did now try many different drivers from different vendors none of them worked thus I think there is something else wrong. I then did some more tests, trying to find anything being

Hi, Oh sorry, of course: The running os is debian 9.9 and I'm running the sernet-samba-ctdb in version 4.9.11-15 This is my configuration: [global] ??? winbind refresh tickets = Yes ??? winbind use default domain = yes ??? template shell = /bin/bash ??? idmap config * : range = 1000000 - 1999999 ??? idmap config ZFD : backend = rid ??? idmap config ZFD : range = 0 - 200000 ??? hide dot

Hi, I have a ctdb cluster with 3 nodes and 3 glusterfs (version 6) nodes up and running. I observe plenty of these situations: A connected Windows-10 client doesn't react anymore. I use forder redirections.? - Smbstatus shows up some (auth in progress) processes. - In the logs of a ctdb node I get: Aug 23 10:12:29 ctdb-1 ctdbd[2167]: Ending traverse on DB locking.tdb (id 568831), records

============================================================== "All water has a perfect memory and is forever trying to get back to where it was." Toni Morrison ============================================================== Release Announcements ===================== This is is the latest stable release of Samba 3.6. Major enhancements in Samba 3.6.16 include: o Fix

Without this patch "ssh-agent -d > ~/ssh-agent.sh" will produce a zero byte file. Obviously a corner case, but for what I'm doing it's a show-stopper, and it _seems_ like an obvious improvement to correctness, rather than relying on implicit newline flushing with TTYs and flush-on-exit with the forking mode. Not subscribed, so please CC me on any replies. ---

============================================================== "All water has a perfect memory and is forever trying to get back to where it was." Toni Morrison ============================================================== Release Announcements ===================== This is is the latest stable release of Samba 3.6. Major enhancements in Samba 3.6.16 include: o Fix