bug-bash archive search

Results:

References: [ ssh: 493 ]

Total 493 documents matching your query.

1. Failed to login. (score: 2): Author: HIDDEN; Date: Sun, 22 Oct 2000 23:08:04 +0200; Configuration Information [Automatically generated, do not change]: Machine: i486 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DHOSTTYPE='i486' -DOSTYPE='linux-gnu' -DMACHTYPE='i; /archive/html/bug-bash/2000-10/msg00050.html (4,830 bytes)
2. [PATCH]: ipv4 and ipv6 support when getaddrinfo() available (score: 2): Author: HIDDEN; Date: Thu, 30 Nov 2000 22:09:48 +0100; Simple patch to add v6 support for bash ie: [misiek@arm misiek]$ cat < /dev/tcp/::1/22 SSH-1.99-OpenSSH_2.3.0p1 bye, -- Arkadiusz Miśkiewicz, AM2-6BONE [ PLD GNU/Linux IPv6 ] http://www.t17.ds.pwr.w; /archive/html/bug-bash/2000-11/msg00096.html (4,345 bytes)
3. bash2 running as bash1 (score: 2): Author: HIDDEN; Date: Wed, 6 Dec 2000 15:47:52 -0500; Configuration Information [Automatically generated, do not change]: Machine: i386 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i386' -DCONF_OSTYPE='linux-gnu' -DC; /archive/html/bug-bash/2000-12/msg00006.html (5,173 bytes)
4. Invocation and startup file compatibility with OpenSSH (score: 2): Author: HIDDEN; Date: Fri, 08 Dec 2000 21:03:19 -0700; Can someone help me out here? I was having trouble running the OpenSSH version of scp and discovered that the problem occurs because the remote shell generates text output (in my case) when calling t; /archive/html/bug-bash/2000-12/msg00018.html (5,895 bytes)
5. Re: openssh-SNAP-20001207 scp "Bad file descriptor" sort-of work-around (score: 2): Author: HIDDEN; Date: Sat, 09 Dec 2000 11:17:28 -0700; As I understand, bash already can tell the difference - that's why BASH(1) says: Bash attempts to determine when it is being run by the remote shell daemon, usually rshd. That's part of the reason I; /archive/html/bug-bash/2000-12/msg00020.html (7,706 bytes)
6. [50 character or so descriptive subject here (for reference)] (score: 3): Author: HIDDEN; Date: Sat, 17 Mar 2001 08:57:35 +0100; Configuration Information [Automatically generated, do not change]: Machine: i686 OS: linux-gnulibc1 Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686' -DCONF_OSTYPE='linux-gnu; /archive/html/bug-bash/2001-03/msg00071.html (6,154 bytes)
7. Re: "set -o vi" not working (score: 2): Author: HIDDEN; Date: Mon, 9 Apr 2001 11:24:39 -0400; Does question F6 of the FAQ address the problem? -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ( ``Discere est Dolere'' -- chet) Chet Ramey, CWRU chet@po.CWRU.Edu http://cnswww.cns.; /archive/html/bug-bash/2001-04/msg00043.html (4,479 bytes)
8. bash and read -u (score: 2): Author: HIDDEN; Date: Mon, 14 May 2001 19:57:12 -0400; The ksh read builtin has a really nifty -u N option to get input from filedescriptor N instead of from stdin. It would be useful if bash read got that option, too. Example: while read -u3 host; do ec; /archive/html/bug-bash/2001-05/msg00065.html (4,523 bytes)
9. Re: bash and read -u (score: 2): Author: HIDDEN; Date: 15 May 2001 15:23:43 +0200; Morty> The ksh read builtin has a really nifty -u N option to get input from Morty> filedescriptor N instead of from stdin. It would be useful if bash Morty> read got that option, too. Why not use t; /archive/html/bug-bash/2001-05/msg00069.html (4,666 bytes)
10. Re: redirect to STDERR problem (score: 3): Author: HIDDEN; Date: 15 Jul 2001 11:52:28 +0200; I guess one scp (aka ssh) writes the password prompt to /dev/tty but the other to STDERR, depending on ssh flavour (and version?). Sven; /archive/html/bug-bash/2001-07/msg00098.html (5,176 bytes)

Current List: 1 - 10
Page: [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20]