Displaying 20 results from an estimated 200 matches similar to: "user input in clientloop.c"
2020 Oct 14
2
Connection hang, can't stop SSH
Using OpenSSH_8.3p1 I had an open (working) connection to some other
box; after a bit of inactivity, some device in the middle seems to have
forgotten about the TCP connection (NAT) and broke it.
I've got an EscapeChar defined, though; so first I tried to send a BREAK
and, when that didn't help (TCP already gone, packets get lost!), I
tried (just out of curiosity) a Rekey.
Now I can see
2009 Jul 07
1
Read buffer size in clientloop.c
Hi,
when trying to optimize socket transfer rates under Cygwin, it turned
out that the underlying WinSock implementation is surprisingly sensitive
to buffer sizes. The latest Cygwin from CVS is now setting the socket
receive/send buffers (SO_RCVBUF/SO_SNDBUF) to 64K, rather than keeping
them at their default values of 8K which thwarts data transfers a lot.
While testing I still had the problem
2007 Jan 16
11
[Bug 52] ssh hangs on exit
http://bugzilla.mindrot.org/show_bug.cgi?id=52
dtucker at zip.com.au changed:
What |Removed |Added
----------------------------------------------------------------------------
OtherBugsDependingO| |1274
nThis| |
------- You are receiving this mail because: -------
You are the assignee for
2001 Feb 22
3
intermittent stderr
The command "ssh ls -l /doesnotexist" gives various responses:
Running from a 200 MHz PentiumPro with dsa key added to ssh-agent:
Mistakes worst to fast machine:
To a faster 600 MHz dual processor i686 600 MHz machine:
ls: /doesnotexist: No such file or directory -- correct
nothing at all -- wrong
ls: select: Bad file descriptor -- wrong
2009 Jan 06
3
[Bug 1548] New: Double free in OpenSSH clientloop.c/xmalloc.c via cmdline port forwarding
https://bugzilla.mindrot.org/show_bug.cgi?id=1548
Summary: Double free in OpenSSH clientloop.c/xmalloc.c via
cmdline port forwarding
Product: Portable OpenSSH
Version: 5.1p1
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: ssh
AssignedTo:
2004 Sep 10
0
mysteries of client_process_input()
I was trying to modify the way openssh client (3.9.1p)
handles keyboard input (regular input, once the
connection is made). I modified the
client_process_input function, but it seems that it
was never called. I confirmed this with gdb - setting
a breakpoint on that function never tripped.
Obviously, there must be some other function that
openssh uses to read keyboard input, but I can't find
2012 Oct 22
1
[PATCH] Implement remote dynamic TCP forwarding
Hi all,
This is a client side only implementation of reversed dynamic (SOCKS) TCP
forwarding, which means it is compatible with any existing servers
have 'remote forward' capability.
To establish such forward, use "ssh -R [BIND_ADDRESS:]PORT ...".
The server will listen on that port and address and accept SOCKS
traffics.
Hope this will be useful for you.
There was an
2004 Jul 13
1
channel->input buffer bug and patch
In our work with enabling large windows for openssh we found
1) that if a window > 0x10000 is advertised to openssh's sshd
2) the sshd tries to send more than 0x10000 bytes of data
3) the receiver does not consume them
4) the input buffer will grow larger than the size allowed by buffer.c
and fatal().
We believe the correct behavior is to limit reading into the channel
input buffer to
2007 Jul 26
1
Channel Handling Patch
The current code for channel.c creates an array of Channel structs
(initially set to NULL) which is then iterated through, in full, every
time a channel needs to be dealt with. If only one channel is in use,
which is relatively common, the code still loops through the entire array.
This patch creates a linked list of pointers to these structs and the
code steps through the linked list. Since
2023 Aug 06
2
Packet Timing and Data Leaks
On Thu, 3 Aug 2023, Chris Rapier wrote:
> Howdy all,
>
> So, one night over beers I was telling a friend how you could use the timing
> between key presses on a type writer to extract information. Basically, you
> make some assumptions about the person typing (touch typing at so many words
> per second and then fuzzing the parameters until words come out).
>
> The I
2004 Apr 23
1
openssh code
Hi,
How do the communication between sshd and program happens when compat20
is enabled? There are two function process_buffered_input_packets and
process_input, but in both cases if compat20 is enabled its just buffering
the packets, but how do sshd will the command to program for execution?
Regards
prasad
2010 Jul 22
1
remote vs local window discrepancy
I am utilizing an openssh tunnel between two Linux boxes. On the client
box I issue the following commands to set up the tunnel;
- ssh -w0:0 root at x.x.x.x -v where x.x.x.x is the IP address of the Linux
system running sshd
- ip addr add 10.0.5.1/32 peer 10.0.5.2 dev tun0
- ip link set tun0 up
On the box running sshd I issue the following commands:
- ip addr add 10.0.5.2/32 peer 10.0.5.1 dev
2001 Aug 02
0
patch: properly zeroing fd_set in clientloop
Hello all,
This is a problem and patch reported to Red Hat Bugzilla by
Jonathan Kamens <jik at kamens.brookline.ma.us>. I'm just acting as a relay
:-)
jik has experienced some weird crashes relating to window size changes or
some similar activity. These are rather hard to trace.
Problem was fixed by patching clientloop, where fd_set structures appear
to be improperly zeroed (bytes vs
2007 Mar 23
7
4.6p1 chan_read_failed error
The 4.6p1 sshd is logging this error during remote commands or file
transfers:
error: channel 0: chan_read_failed for istate 3
Platform is Solaris 8, 4.6p1 + OpenSSL 0.9.8d.
The commands and transfers work correctly, so the error message appears
to be spurious. The error message does not appear when processing logins.
Otherwise 4.6p1 is running without any apparent problems. This error
2023 Aug 03
2
Packet Timing and Data Leaks
Howdy all,
So, one night over beers I was telling a friend how you could use the
timing between key presses on a type writer to extract information.
Basically, you make some assumptions about the person typing (touch
typing at so many words per second and then fuzzing the parameters until
words come out).
The I found a paper written back in 2001 talked about using the
interpacket timing in
2008 Aug 04
1
Hanging ssh sessions with openssh-5.1p1 and Solaris 8 & 10
Since we upgraded OpenSSH from 5.0p1 to 5.1p1 on our Solaris 8 boxes
(I know, I know, we should upgrade or retire them...), we've started
experiencing problems with slogin'ing into these boxes, running vi,
and pasting text into the vi session.
As long as we are pasting in less that 1024 characters it's fine.
With >= 1024 characters, the session hangs.
If you run
2007 Apr 08
11
Error message after upgraing the openssh 4.6P1
Hi,
We have upgraded the openssh 4.6P1 on Solaris 8 servers. After upgrade
we get the below error message whenever we execute the remote commands
using ssh. Please let me know what the fix is for this.
Apr 8 03:03:43 dvsrv10 sshd[25379]: [ID 800047 auth.info] Accepted
publickey for osteam from 10.0.93.31 port 35856 ssh2
Apr 8 03:03:50 dvsrv10 sshd[25381]: [ID 800047 auth.error] error:
2002 Sep 24
5
BUG: ssh hangs on full stdout-file-system
System: Linux 2.4.18, openssh-3.4p1
Problem:
I use "ssh" and "tar" to backup remote directory trees to a local
hard-disk/file-system:
# ssh remote.server.org "tar -cz /home" >/backup/remote.tar.gz
If the backup-file-system runs out of space before the backup
completes, ssh starts hanging (waiting for the stdout-write to
complete).
Analysis:
In
2010 Jan 14
1
ssh(1) multiplexing rewrite
Hi,
At the n2k10 OpenBSD network hackathon, I finally got some time to clean
up and rewrite the ssh(1) client multiplexing code. The attached diffs
(one for portable OpenSSH, one for OpenBSD) are the result, and they
need some testing.
The revised multiplexing code uses a better protocol between the master
and slave processes and I even bothered to write it up :) It tracks the
control sockets
2011 Oct 10
2
Channel life span
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
Basic context for my questions:
Client (ssh) and server side (sshd) where the client use -L option for a
direct-tcpip channel and forward all requests. (All Linux and openssh version
5.9p1).
$ ssh -L8080:<some-ip>:8181 ...
I noticed that when a third client send data to the local port (8080) used for
forwarding, a channel is created: