similar to: [Bug 2739] New: ssh-add no longer works with xargs

Displaying 20 results from an estimated 5000 matches similar to: "[Bug 2739] New: ssh-add no longer works with xargs"

2011 May 17
3
xargs with max each line / argument
How do I pass xargs input one line at a time to subsequent command? For example I want to install rubygems by reading a text file as shown below, however the arguments are getting passed all at once to the 'gem install' command. I hace tried -L (max-lines) and -n (max args) options, but it didn't work. What's missing here?? Any help? $ cat gem.list.1 mkrf rake xmlparser $ awk
2005 Feb 08
6
help with xargs and mv
I am trying to move a group of sendmail queue files into a special area and am developing s script to assist. The manual steps are: # Identify which messages to move mailq -qR<domain> > file1 # Select only lines with message ID strings grep '^[[:alpha:]][[:alnum:]]\{13\}' file1 > file2 # extract only the messages ID cut -b -14 file2 > file3 # prepend '*' to
2006 Oct 31
0
6323628 /usr/xpg6/bin/xargs will coredump if given -n or -s flags with no argument.
Author: ceastha Repository: /hg/zfs-crypto/gate Revision: 4fa98e79aa8cacc3ee6e3642cf306228cc9edcd1 Log message: 6323628 /usr/xpg6/bin/xargs will coredump if given -n or -s flags with no argument. Files: update: usr/src/cmd/xargs/xargs.c
2002 May 22
0
Strange behaviour with OpenSSH 3.1p1 +
I've been using OpenSSH for quite along time now and I've ran into this strange bug: ssh_askpass: exec(/usr/local/libexec/ssh-askpass): No such file or directory Host key verification failed. This happens when i have X running. Without X I see the following: .... debug1: read PEM private key done: type DSA debug1: read PEM private key done: type RSA debug1: identity file
2000 Sep 09
0
2.2.0p1 PATCH: ssh/scp/slogin will invoke ssh-askpass
Enclosed is a patch against 2.2.0p1 that teaches ssh (and therefore slogin and scp) how to invoke ssh-askpass to request a password, RSA/DSA key passphrase, or an skey challenge response. I've tested this on Linux (i386), for passwords and RSA/DSA key passphrases. I cannot easily test whether the Right Thing will happen for skey challenge responses; I would appreciate it if someone who uses
2009 Oct 05
2
gnu --target-dir, how to fake with rsync?
Is this in rsync and I just can't find it, or if not, is there a way to fake this OR, third possibility, is anyone working to add it? For those who've never used this option - for the GNU cp & mv type commands they have the --target-dir="dir" option. It lets you put the destination directory as the first argument to cp and mv instead of the last argument. They added the
1999 Dec 10
2
[David Huggins-Daines <dhd@plcom.on.ca>] Bug#52414: ssh-add uses ssh-askpass, but ssh doesn't
Damien, Here's a forwarded bug for you. Cheers, Phil. --[[message/rfc822]] Subject: Bug#52414: ssh-add uses ssh-askpass, but ssh doesn't Reply-To: David Huggins-Daines <dhd at plcom.on.ca>, 52414 at bugs.debian.org Resent-From: David Huggins-Daines <dhd at plcom.on.ca> Resent-To: debian-bugs-dist at lists.debian.org Resent-CC: Philip Hands <phil at hands.com>
2001 May 10
2
2.9p1 ssh-add/ssh-askpass first try fails
OpenSSH Version 2.9p1 of "ssh-add $HOME/.ssh/id_rsa < /dev/null" fails on the first try of using ssh-askpass before the window manager starts. The second try works. The error message on the first try is "Bad passphrase, try again". This did not occur using OpenSSH-2.5.2p2.tar.gz. I've tested this on both RHL6.2 and RHL7.1, both with all RH rpm updates applied. I
2018 Apr 13
1
backup-script/backup_samba4
Hi! i am testing Louis van Belle backup script. it works quite well. Thank you for sharing this! https://github.com/thctlo/samba4/blob/master/backup-script/backup_samba4 but i think there is an error in the KEEP_DAYS code as the string '\-$KEEP_DAY1\-|\-$KEEP_DAY2-' is not interpolated so the egrep does exclude anything from rm call. So no files older than $DAYS are kept... # Remove
2001 Oct 17
3
Again: bugs in contrib/solaris/opensshd.in and buildpkg.sh
(Shame on me: wrong filename in last posting, now here are correct diffs) in contrib/solaris/ (openssh-SNAP-20011017.tar.gz) 1) buildpkg.sh makes wrong link for /etc/init.d/opensshd 2) /etc/init.d/opensshd has not-working killproc here my version tested on Solaris 2.4 and 8 (no pgrep with solaris 2.4, XARGS was undefined, simpler syntax) J?rg --- contrib/solaris/buildpkg.sh Fri Oct 12
2002 Jan 18
5
contrib/solaris/opensshd.in patch
This patch adds the seatbelts which _only_ kill parent sshd procs... -RMallory (eg: when you ssh into a machine and pkgadd the new openssh, it will not kill your current (or anyone else's sshd session) onanother_note: the buildpkg.sh could use some exec_prefix functionality... to deal with ./configure --prefix= --exec_prefix=/usr *** bak/opensshd.in Fri Oct 19 13:36:24 2001 ---
2018 Sep 11
2
Re: [PATCH nbdkit 1/4] build: Move list of plugins and filters to the configure script.
On 9/11/18 1:47 PM, Richard W.M. Jones wrote: > It's easier to get it to other places if it starts out in the > configure script. > > Also split the list into language and non-language plugins. > --- > common-rules.mk | 44 ---------------------------------------- > configure.ac | 53 +++++++++++++++++++++++++++++++++++++++++++++++++ > 2 files changed, 53
2011 May 17
5
Feed a list of filenames to vim
There are some googlable ways to feed a list of filenames to vim, but I stumble on weird results. With my filelist, I try to do cat list | xargs vim ...to edit the files listed in the file "list". Here's what happens: [root at lasso2 tempdir]# ls -l total 8 -rw-r--r-- 1 root root 0 May 17 18:28 a -rw-r--r-- 1 root root 0 May 17 18:28 b -rw-r--r-- 1 root root 3 May 17
2009 Aug 19
2
replacing permissions on uploaded windows files
Hello, I've got a CentOS box and users are putting Windows long files on it, files with " " and " - " in their filenames. I'm trying to adjust the permissions as well as user and group membership and i'd like the changes to be sticky. On the tld i've set permissions of 2755 and am trying to batch convert the files and subfolders in it. I've done this: find
2005 Jan 04
1
trying to debug ssh-askpass problem
Hi all, I have a script which calls ssh-add at a certain point, and I'm getting the following error: ssh_askpass: exec(/usr/bin/ssh-askpass): No such file or directory I don't see why it's doing this, since SSH_ASKPASS isn't set, and there should be a working terminal: SSH_ASKPASS If ssh needs a passphrase, it will read the passphrase from the
2001 Mar 04
1
streaming Vorbis: trials & errors with Icecast 2
Greetings: Okay, here's where I'm at so far. Icecast 2 builds without problems. I edit the icecast.xml config file as seen in the server output below: [root@localhost icecast]# icecast -c conf/icecast.xml <?xml version="1.0"?> <icecast> <location>DLP_House_Of_Sound</location> <admin>dlphilp@bright.net</admin> <limits>
2007 Jul 03
2
[LLVMdev] "bytecode" --> "bitcode"
I did this short experiment: ggreif at my [!297] cd /home/ggreif/llvm ggreif at my [!298] find . -name "*.cpp" | xargs grep bytecode | wc -l 143 I guess these are a quick prey for perl's in-place replace. But wait! There are more: ggreif at my [!299] find . -name "*.cpp" | xargs grep -i bytecode | wc -l 291 probably all of the rest is "Bytecode"
2002 Jul 16
1
opensshd.in
I've had the wrong sshd daemon killed by "killing using alternate method" too many times. Would this cause anyone any grief? --- opensshd.in.old Sun Oct 21 16:42:02 2001 +++ opensshd.in Mon Jul 15 19:34:16 2002 @@ -3,11 +3,8 @@ # # Stripped PRNGd out of it for the time being. -AWK=/usr/bin/awk CAT=/usr/bin/cat KILL=/usr/bin/kill -PS=/usr/bin/ps -XARGS=/usr/bin/xargs
2023 May 12
0
[Bug 3571] New: Canceling SSH_ASKPASS actually sends an empty string
https://bugzilla.mindrot.org/show_bug.cgi?id=3571 Bug ID: 3571 Summary: Canceling SSH_ASKPASS actually sends an empty string Product: Portable OpenSSH Version: 8.8p1 Hardware: Other OS: Linux Status: NEW Severity: major Priority: P5 Component: ssh Assignee: unassigned-bugs at
2004 Apr 12
1
Regarding SSH_ASKPASS
I've been giving SSH_ASKPASS a hard look, and it's not clear to me how it's supposed to work. The documentation (ssh.1) seems explicit enough: SSH_ASKPASS If ssh needs a passphrase, it will read the passphrase from the current terminal if it was run from a terminal. If ssh does not have a terminal associated with it but DISPLAY and SSH_ASKPASS are set, it will execute