similar to: [Bug 858] Grammar bug in sshd(8)

On Fri, Jun 04, 2004 at 01:20:54PM -0400, Joey Hess wrote: > My colocated server was refusing both ssh and ssl telnet connections. > It looked like this: > > joey:~>ssh -v kite > OpenSSH_3.8.1p1 Debian 1:3.8.1p1-4, OpenSSL 0.9.7d 17 Mar 2004 > debug1: Reading configuration data /home/joey/.ssh/config > debug1: Applying options for kite > debug1: Reading configuration

https://bugzilla.mindrot.org/show_bug.cgi?id=1692 Summary: sshd sometimes dies when sent multiple SIGHUPs in quick succession Product: Portable OpenSSH Version: 5.3p1 Platform: Other URL: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug /497781 OS/Version: Linux Status: NEW

Here's a quick patch that adds a timeout (value set from the connection timeout config parameter) for identification exchange. The situation that this fixes is the one where the sshd has a connection open (so you can make a TCP connection) but does not put up a banner (e.g. when the disk has crashed or when file descriptors are exhausted on a machine). Sounds unusual, but this happens with

Hello OpenSSH folks, This was a really minor knit, but I noted while I was developing a pexpect module for ssh that setting ConnectTimeout to 0 in the options to ssh sets the login timeout to infinite time. I was wondering whether or not this was a documentation bug and/or potential clarification that could to be made, or if this was a software bug that needs to be fixed. I don't see

Hello, I'm using Ruby's Shellwords module, which generates a string from an array, suitable for shell evaluation. Ruby's implementation prefers escaping whitespace with a backslash rather than quotes. However, this appears to cause some kind of issue in Rsync when it computes argv from -e option. Here is an example command generated by some Ruby code: rsync --archive --stats -e

Hi all, I have somewhat a strange problem that I could not figure out, maybe someone here can lelp. I have a script that uses scp to distribute files to many servers, I use '-o BatchMode=yes -o ConnectTimeout=2 options so the scp will not get stuck if something is wrong with the remote host. If the remote host is down (non-pingable) or sshd is down the timeout option works and the scp

Fix bug ConnectTimeout=N only works on the first ConnectionAttempts https://bugzilla.mindrot.org/show_bug.cgi?id=2918 --- sshconnect.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/sshconnect.c b/sshconnect.c index 4862da5e..b837a83a 100644 --- a/sshconnect.c +++ b/sshconnect.c @@ -454,11 +454,12 @@ waitrfd(int fd, int *timeoutp) { struct pollfd pfd; struct timeval

> Yeah, it only does space-splitting and that's all it will ever do. It still looks to me like there is a bug in the original escaping, since any command receiving that string is receiving a backslash that is not supposed to be there. It should only be escaping the string enough to get it to rsync, not trying to guess what rsync is going to do with it after it gets it. I'm not

Fix and/or document issues raised in this thread: https://www.redhat.com/archives/libguestfs/2017-February/msg00010.html Rich.

The attached patch adds a new 'ConnectTimeout' option (man page updated in patch) to avoid wasting time when the target host is down. I needed that because I was using rsync/rdist over ssh for massive files update and the default connect() took too long for my purpose. The patch was tested on Linux only, but I used a similar one for ssh 1.2.XX on Linux, Solaris and HP-UX without

http://bugzilla.mindrot.org/show_bug.cgi?id=354 ------- Additional Comments From cjwatson at debian.org 2003-01-03 02:42 ------- Alternatively, perhaps sshd could be configured to setrlimit() everything up to RLIM_INFINITY after forking but before giving up root privileges. It could then rely on pam_limits to set limits back down if the administrator wants that, which would work even with

https://bugzilla.mindrot.org/show_bug.cgi?id=1933 Bug #: 1933 Summary: restorecon typoed as "restorcon" in contrib/redhat/sshd.init Classification: Unclassified Product: Portable OpenSSH Version: 5.9p1 Platform: All OS/Version: All Status: NEW Severity: normal

https://bugzilla.mindrot.org/show_bug.cgi?id=3717 Bug ID: 3717 Summary: Stricter sshd absolute path requirement breaks xinetd Product: Portable OpenSSH Version: 9.8p1 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: sshd Assignee: unassigned-bugs at

http://bugzilla.mindrot.org/show_bug.cgi?id=207 ------- Additional Comments From jclonguet at free.fr 2003-04-22 05:08 ------- Created an attachment (id=273) --> (http://bugzilla.mindrot.org/attachment.cgi?id=273&action=view) Patch for OpenSSH-3.6.1p1 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

There's been a lot of discussion on this list about creating a formal grammar for markdown. I had a go at writing a [parsing expression grammar] for markdown. I used Haskell and John Meacham's Frisby PEG parsing library, but it should not be too hard to port the grammar to PEG libraries in other languages. [parsing expression grammar]:

https://bugzilla.mindrot.org/show_bug.cgi?id=1471 Summary: sshd can block if authorized_keys is a named pipe Classification: Unclassified Product: Portable OpenSSH Version: 4.7p1 Platform: All OS/Version: Linux Status: NEW Severity: minor Priority: P2 Component: sshd AssignedTo: bitbucket at

Has anyone seen any attempts to give Markdown a PEG (parsing expressions grammar) recognizable by some ruby PEG parser generator grammar like Treetop? http://treetop.rubyforge.org/

Hey Zed, any chance you mind sharing the grammar file you use with lemon to create the parser? I''ve been meaning to sit down and learn how to use one of those things. If not, any suggestions on a good resource for learning how to use a LALR parser?

Hi everyone, Today I tried to use the CD-ROM that came with my "Cambridge Grammar of English" on Ubuntu 8.10 and Wine 1.1.14 The install went ok, but when I try to run it I get the following error: Code: $ wine start 'C:\Program Files\Cambridge\Cambridge Grammar of English\cge.exe' fixme:exec:SHELL_execute flags ignored: 0x00000100 vwilson at

> The point is that the original escaping DOUBLE escapes an equals sign: > foo\\\=bar > It shouldn't, there's no reason to. If you paste into your command line: rsync -e ssh\ -l\ backup\ -i\ /etc/synco/id_rsa\ -o\ ConnectTimeout\\\=60\ -o\ BatchMode\\\=yes The list of arguments would be (i.e. the values in ARGV): ['rsync', '-e', 'ssh -l backup -i