Displaying 20 results from an estimated 3000 matches similar to: "[Bug 1307] client disconnects if ServerAlive enabled but not implemented"
2007 Dec 28
3
[Bug 1307] client disconnects if ServerAlive enabled but not implemented
https://bugzilla.mindrot.org/show_bug.cgi?id=1307
--- Comment #10 from Darren Tucker <dtucker at zip.com.au> 2007-12-29 00:38:09 ---
Created an attachment (id=1424)
--> (http://bugzilla.mindrot.org/attachment.cgi?id=1424)
Hack sshd to provide testcase for this change.
This patch is a nasty hack to make sshd behave the same as described
here to test this change. Against the hacked
2001 Jul 22
1
[patch] ignore SSH2_MSG_IGNORE packets
Hi,
protocolkeepalives sends ssh_msg_ignore, which the ssh2 server handles
incorrectly (i.e. it produces some output to syslog, instead of
ignoring the packet):
Jul 9 11:58:07 ren sshd[16580]: error: Hm, dispatch protocol error:
type 32 plen 4
This patch implements a highly advanced function to ignore these
packets ;)
Matthew
-------------- next part --------------
An embedded and
2000 Mar 03
7
[PATCH] Add a Maximum Idle Time (1.2.2)
The attached patch adds an option (off by default to preserve current
behavior) to set a timeout on the select() statement that waits for input
in clientloop.c. This fixes a timeout issue for me (explained below) and
probably also fixes the timeouts mentioned in last month's thread "Idle
time out". The patch is also available by http from:
2014 Aug 25
13
[Bug 2265] New: ServerAlive{Interval,CountMax} ignored if using an active -R or -L tunnel
https://bugzilla.mindrot.org/show_bug.cgi?id=2265
Bug ID: 2265
Summary: ServerAlive{Interval,CountMax} ignored if using an
active -R or -L tunnel
Product: Portable OpenSSH
Version: -current
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P5
Component:
2003 Apr 04
5
Anti-idle in OpenSSH client?
Heya,
Most of the windows ssh clients (putty, securecrt) have anti-idle
features. They offer either a null packet or protocol no-op or user
defined string to be sent over every x seconds.
Is this possible or planned with the OpenSSH client? Our draconian
firewall admins have started timing out ssh sessions. Yes I'm aware I
could hack up a port forwarding dumb traffic process, but was
2001 Mar 14
1
[PATCH] Added Null packet keepalive option
I have attached a patch which adds null packet keepalive
functionality to the client. This patch is made against the
current CVS tree as of 3/14/01.
Please consider this patch for inclusion in the OpenSSH main tree.
This patch is based upon and includes code from the Chris Lightfoot
(chris at ex-parrot.com) patch posted 2/23.
The original patch from Chris is at:
2010 Aug 02
7
Persistent SSH sessions
Hi all
I have an ADSL modem which reboots when there is a power cut and the
inverter (UPS) kicks in. Internet access is down for a duration of 1
to 2 minutes while the modem boots.
I have many SSH tunnels and shells active. Due to the default
"TCPKeepAlive On" setting, these sessions are terminated almost
immediately.
I tried the following configuration:
sshd_config on server:
2015 Nov 11
8
[Bug 2494] New: kex_protocol_error should send SSH2_MSG_UNIMPLEMENTED
https://bugzilla.mindrot.org/show_bug.cgi?id=2494
Bug ID: 2494
Summary: kex_protocol_error should send SSH2_MSG_UNIMPLEMENTED
Product: Portable OpenSSH
Version: 6.9p1
Hardware: Other
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: sshd
Assignee: unassigned-bugs
2001 Apr 09
3
[PATCH]: Heartbeat/Watchdog Patch
Dear Developers,
I've released a patch against openssh-2.5.2p2.
The patch adds heartbeat (keepalive) function to ssh(1),
and watchdog timeout function to sshd(8). The watchdog
timeout is intended to terminate user's processes
as soon as possible after the link has been lost.
http://www.ecip.tohoku.ac.jp/~hgot/sources/openssh-watchdog.html
The combination of the heartbeat and the
2016 Aug 24
3
kex protocol error: type 7 seq xxx error message
Hi,
mancha and me debugged a problem with OpenSSH 7.3p1 that was reported on
the #openssh freenode channel. Symptoms were that this message was
popping on the console during a busy X11 session:
kex protocol error: type 7 seq 1234
I managed to reproduce the problem, it is related to the SSH_EXT_INFO
packet that is send by the server every time it is sending an
SSH_NEWKEYS packet, hence after
2010 Jan 28
1
Possible issue with stdio forwarding
Greetings,
I've been doing a little testing with the stdio forwarding support added
in recent snapshots and have encountered one possible issue. First, I
should say that this feature generally seems to work. However, I haven't
been able to get it to work when connecting to a server running
SSH.COM's product.
The config file I am using is fairly simple:
Host sfe1
LogLevel debug3
2006 Apr 01
2
List posting etiquette
Just a tag-on for the thread about list posting etiquette, etc., etc.
The following is a link to an excellent (if wordy) how-to-do-it-right
instruction manaual replete with links to other treatises on the
topic. The entire text of this document is emailed to the mailing list
on the 1st of each month. This is the Cadillac of etiquette manuals.
http://www.linux-sxs.org/index2.html
Enjoy,
--
2011 Jun 24
2
[LLVMdev] multiple return value assembler regression?
On 06/24/2011 03:45 PM, Chris Lattner wrote:
>
> On Jun 24, 2011, at 9:29 AM, Bagel wrote:
>
>> It appears the syntax for returning multiple values has changed since 2.9.
>> Previous to that:
>> ret i32 %a, i32 %b
>> worked. The new syntax is something like:
>> ret { i32, i32 }{i32 %a, i32 %b}
>> but this yields an error:
>> mrv-bug.ll:5:24:
2013 Sep 12
5
Setting up postfix under CentOS-6
I recently, perhaps foolishly, changed over a remote server
from sendmail/procmail to postfix/amavis/spamassassin/clamd ,
and I'm finding it difficult to configure this setup.
The CentOS document <http://wiki.centos.org/HowTos/postfix>
explicitly says that its instructions may not work in CentOS-6.
Does anyone know of reasonably simple postfix documentation
for CentOS-6?
I've been
2001 Dec 13
3
behaviour of ssh/scp over flakey links - timeout/retry?
I'm using OpenSSH's ssh and scp to back up some remote
machines, roughly as follows :
ssh remote-host "tar up a few dirs"
scp remote-host:tarfile local-repository
On the whole, as I'd expect, this works just fine.
But .. sometimes the link is a bit dodgey (for lack of
a more explicit term, this being a polite list :) )
Can anyone tell me how ssh and scp timeout and retry,
2001 Sep 26
1
[PATCH] random SSH_MSG_IGNORE packets
Hi!
The following patch adds ability to configure the ssh client to
send SSH[2]_MSG_IGNORE packets of random length at random times
whithin a user-specified interval. The function is configured by
setting the config-file options BogusTrafficIntervalMax and
BogusTrafficIntervalMin, which defines the interval in seconds in
which the packets are randomly sent. It is disabled by default. It
suffices
2010 Feb 28
3
Slightly OT: Does anyone use latex2rtf with sweave output ?
Hello,
I'm trying to use R (and Sweave) to pull some data out of a database and
produce some standard reports. unfortunaltey, the people who want the
reports want them in an editable format so they can add wordy bits to
the automatically generate tables and graphs.
My current plan is to use R to call a standard sweave document and pass
variables to tell what data to pull out of the db,
2004 Mar 26
2
Patch for login exchange timeout
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
2010 Feb 11
2
[LLVMdev] Metadata
On Thu, Feb 11, 2010 at 8:50 PM, David Greene <dag at cray.com> wrote:
>
> So I tried a bunch of things:
>
> %r8 = load <2 x double>* %r6, align 16, metadata !"nontemporal"
> %r8 = load <2 x double>* %r6, align 16, metadata !nontemporal
> %r8 = load <2 x double>* %r6, align 16, !{ metadata !"nontemporal" }
> %r8 = load <2 x
2008 Sep 03
1
Problem connecting with openssh-5.1-client to Juniper Eseries
After upgrading to 5.1, connections to our Juniper E-Series routers
fail with:
$ ssh -v eseries
OpenSSH_5.1p1, OpenSSL 0.9.8g 19 Oct 2007
debug1: Reading configuration data /etc/ssh_config
debug1: Applying options for *-lns*
debug1: Applying options for *
debug1: Connecting to eseries [1.2.3.4] port 22.
debug1: fd 3 clearing O_NONBLOCK
debug1: Connection established.
debug1: identity file