search for: exec'd

...orking on a project to write a ProxyCommand that reaches out to an SSH CA to receive an SSH certificate prior to the connection. The ProxyCommand also creates a tunnel to the upstream SSH server. When using ProxyCommand alone, the issue is that the identity files are loaded as soon as SSH has fork/exec'd the process. It does not wait for a valid server negotiation. I found the ProxyUseFdPass flag which seemed promising -- here, the identity files weren't loaded until after the file descriptors are passed back to the SSH client. Perhaps I could fetch the identity file, return the fds, and...

...N LNO C EQN STATUS DNCTR LNCTR CHBAR ------+------------+-----+-+-------------+------+-------+-------+------- 05 2171035 16 0-42- 0-16 DIDLE& 0- 0 0- 0 0- 0 IDLE END JOB 7809 EXEC'D E1 STATUS AES/V15SBOL/BOLCBK1V51327079/013 05-06-06 11:28:38 7873 OMT-00/SYSTEM#1 3080/04515 STATDIU:LTG=0-42,DIU=0; EXEC'D LTG DIU LTU TYPE APPLIC OST LTG OST DIU OST PCM -------+--...

For root sessions pam_open_session is called, but not pam_close_session. sshd behavior is broken for root logins because if pam session is run from the child, close is never called due to exec: on open since use_privsep is not set, parent calls do_exec_pty(), which does not open session. then, it skips calling do_setusercontext(), so it does not open session. child calls do_setusercontext(), which opens session. on close child will not close sesion, because it exec&...

...dling and somewhere, deep down there, the process was stuck. Well, that led my to believe, that there was something wrong with the -so called- "mach bootstrap context". I usually start dovecot from with a (home-brewn) startup-script, which invokes it (practically) like so: sudo /usr/libexec/StartupItemContext dovecot (again: all this was working fine under 2.0.15) Now with 2.1.10, when I manually invoke dovecot with just sudo dovecot Everything appears to work fine - at least the sessions don't get stuck any more. But as soon as I logout (with dovecot still running in the bac...

...in the wild is not easy, as the window for the race condition is so small. However, it can be fairly easily reproduced under the following slightly artificial conditions, by using gdb to pause sshd within the window for long enough to kill the child: Run ssh -T -x localhost 'sleep 30s; echo X; exec >&- 2>&- <&- sleep 5h' Find the sshd serving this connection, and connect to it with gdb. It will be in the middle of the actual select() system call. Set a breakpoint at the start of libc select() and continue. When the first sleep completes, the shell will print X, and...

initramfs-tools wants to validate the real init program before running it, as there is no way out once it has exec'd run-init. This is complicated by the increasing use of symlinks for /sbin/init and for /sbin itself. We can't simply resolve them with 'readlink -f' because any absolute symlinks will be resolved using the wrong root. Add a dry-run mode (-n option) to run-init that goes as far...

...sfer and post-transfer command. These options handle our need to prepare a server to receive files and to do some processing after receiving files. The options for /etc/rsyncd.conf are pretransfer script = /some/command/to/run posttransfer script = /some/other/command The commands are exec'd (not run through system() or popen()) and the inputs are the list of files (and directories) that are being synched (from struct file_list *flist). If the pretransfer script fails the synch is stopped. -- david ahern -------------- next part -------------- Only in rsync-2.5.6: config.h O...

...#39;s ksh output! Let's change my shell to "bash" instead % bash bash-3.2$ ./x ./x: line 1: ${.sh.version}: bad substitution So now it's bash that's trying to interpret it! So "it depends" is still true :-) Basically, without #! there (which allows it to be exec'd) the shell determines how the file is interpreted. -- rgds Stephen

Installed v205 for Solaris8, and successfully exec'd tests 1-7 -- but failed 8-10 -- in //doc/docs/textdocs/DIAGNOSIS.txt. Errors... TEST 8 "System error 5 has occured. Access is denied." TESTS 9 & 10 "The account is not authorized to log in from this station." I recall from a previous life that the solution is to mod...

...very simple with no sym/hard links. and total number of files in there is about 30. running the command on local file system has no problem (replicating local dir with -C option). I did truss the remote sshd and see the client connected successfully. forked child sshd which forked again and rsync exec'd: 137: execve("/usr/bin/rsync", 0x0004509C, 0x000450F8) argc = 6 137: argv: rsync --server --sender -vlogDtprC . /home/john/data 137: envp: _=/usr/bin/rsync Both end of rsync is version 2.6.9. and both system are running solaris 9. binary compiled with Sun's cc (not...

...tly in my testing. When I >do use Solaris login (UseLogin yes), a ton of the important environment >variables (like TERM, etc) don't get passed. Is that normal behavior? Looking at the source os session.c it is obvious that when you use login the environment is not passed: execl(LOGIN_PROGRAM, "login", "-h", get_remote_ipaddr(), "-p", "-f", "--", pw->pw_name, NULL); But when the shell is exec'd directly it is: execve(shell, argv, env); Login can accept a list of environment variables...

This is continuing/summarising a rather long discussion that happened on IRC ... We talked to some SELinux experts about what was required to make SELinux work with libguestfs, and it seems reasonably simple to load the policy from the guest filesystem. All that needs to be done is to mount the guest disks up and then run: sh "/usr/sbin/load_policy -i" That command also mounts up

https://bugzilla.mindrot.org/show_bug.cgi?id=2646 Bug ID: 2646 Summary: zombie processes when using privilege separation Product: Portable OpenSSH Version: 7.2p2 Hardware: ix86 OS: Linux Status: NEW Severity: minor Priority: P5 Component: sshd Assignee: unassigned-bugs at

...console. However, I am unable to login as root. I've used "chroot" and "passwd" from the host system to explicitly set the root password. Still no luck. So I began debugging.... I ran "strace" on the container's "login" process (after agetty exec'd login). I noticed that it was unable to open "/dev/log". Sure enough the unix domain socket did not exist inside the container (as seen from outside the container). So I tweaked my host's syslog-ng.conf file to create this socket. My hope was to monitor the log events genera...

...g.uk> AuthorDate: Sun, 17 Jan 2016 19:50:28 +0000 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Wed, 2 Jan 2019 03:08:04 +0000 [klibc] run-init: Add dry-run mode initramfs-tools wants to validate the real init program before running it, as there is no way out once it has exec'd run-init. This is complicated by the increasing use of symlinks for /sbin/init and for /sbin itself. We can't simply resolve them with 'readlink -f' because any absolute symlinks will be resolved using the wrong root. Add a dry-run mode (-n option) to run-init that goes as far...

On 04/24/2015 03:57 AM, Pete Geenhuizen wrote: > if you leave it out the script will run in whatever environment it > currently is in. I'm reasonably certain that a script with no shebang will run with /bin/sh. I interpret your statement to mean that if a user is using ksh and enters the path to such a script, it would also run in ksh. That would only be true if you

The following patches come from Debian and/or Ubuntu packages of klibc. Ben. Ben Hutchings (1): [klibc] run-init: Add dry-run mode Jay Vosburgh (1): [klibc] ipconfig: Use separate sockets for DHCP from multiple interfaces Mathieu Trudel-Lapierre (1): [klibc] ipconfig: Set broadcast when sending DHCPREQUEST and DHCPDISCOVER YunQiang Su (1): [klibc] mips: setjmp.S: don't

As the start of work to add remote support, I'm taking a close look at the protocol layer in the library. These are some small cleanups. Rich.

https://bugs.freedesktop.org/show_bug.cgi?id=73358 Priority: medium Bug ID: 73358 Assignee: nouveau at lists.freedesktop.org Summary: [nv34] adobe flash + firefox -> DATA_ERROR QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: All Reporter: ronald645 at gmail.com

This changes the proposed API slightly. Previously 'mount-local' generating a 'mounted' event when the filesystem was ready, and from the 'mounted' event you had to effectively do a fork. Now, 'mount-local' just initializes the mountpoint and you have to call 'mount-local-run' to enter the FUSE main loop. Between these calls you can do a fork or whatever