Displaying 20 results from an estimated 7000 matches similar to: "kex_reset_dispatch()"
2008 Sep 15
0
No subject
hello..
i am running openssh-3.7.1p2. on linux.It is working successfully..and daemon is running &client also connecting.But the problem is with the mips architecture when i connecting this server from remote syytem.?i got an error of buufer_get:trying to get more bytes 1 than buffer0.And client is not connecting from remote system.My out is as follows on my server
?in sshd main
before
2008 Sep 18
2
SSHD_PROBLEM
hello..
i am running openssh-3.7.1p2. on linux.It is working
successfully.and daemon is running &client also connecting.But the
problem is with the mips architecture when i connecting this server
from remote syytem. i got an error of buufer_get:trying to get more
bytes 1 than buffer0.And client is not connecting from remote system.My
out is as follows on my server
in sshd main
before
2011 Jan 06
25
Call for testing: OpenSSH-5.7
Hi,
OpenSSH 5.7 is almost ready for release, so we would appreciate testing
on as many platforms and systems as possible. This release contains a
couple of large and intrusive features and changes and quite a number of
bug fixes.
Snapshot releases for portable OpenSSH are available from
http://www.mindrot.org/openssh_snap/
The OpenBSD version is available in CVS HEAD:
2018 Nov 13
12
[Bug 2929] New: OpenSSH server should not send the SSH_MSG_EXT_INFO message after rekeying
https://bugzilla.mindrot.org/show_bug.cgi?id=2929
Bug ID: 2929
Summary: OpenSSH server should not send the SSH_MSG_EXT_INFO
message after rekeying
Product: Portable OpenSSH
Version: 7.7p1
Hardware: Other
OS: Linux
Status: NEW
Severity: enhancement
Priority: P5
2014 Jul 15
3
GSSAPI
If I am trying to build OpenSSH 6.6 with Kerberos GSSAPI support, do I still need to get Simon Wilkinson's patches?
---
Scott Neugroschl | XYPRO Technology Corporation
4100 Guardian Street | Suite 100 |Simi Valley, CA 93063 | Phone 805 583-2874|Fax 805 583-0124 |
2007 Jan 08
0
How to remove group1 and group14 from OpenSSH..
Hello everyone.. I am fairly new to the patching format.. so I just decided to post a basic info
about how to remove group1 and group14 diffie key exchange in OpenSSH.
I know that they are listed as required in RFC 4253 but I don't want a client to have the choice
to use a 1024 bit prime for the key exchange. If someone is getting into my system.. they should
upgrade to a new client. I am a
2001 May 14
2
openssh-2.9p1
Hi,
1. I think you should apply the attached patch to openssh-2.9p1,
otherwise ssh-keyscan on linux boxes with glibc-2.1 will experience enormous
timeout delays.
2. Is there a program like ssh-keyscan for the Version2 (dsa and rsa) keys??
regards
Peter Breitenlohner <peb at mppmu.mpg.de>
-------------- next part --------------
diff -ur openssh-2.9p1.orig/ssh-keyscan.c
2001 Mar 23
1
SSH Conections being dropped.
We are having problems with SSH shells disconnecting.
We are replacing a older version of SSH (Non-Comercial Version which some
one installed in error, but it was working fine.) & Had been running
OpenSSH 2.3.0p? which had similar problems, some of the errors I was
seeing went away with OpenSSH 2.5.2.p1.
compiled against openssl-0.9.6, with SUNWspro & GCC281 on Solaris 2.8 &
Solaris
2002 Jun 15
3
why compact.c needed ?
Hi All,
Why compact.c is needed ? All over the code I could find
checks for "datafellows". Why is this needed ?
Regards
DSA
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp.
2014 Jan 17
15
Call for testing: OpenSSH-6.5
Hi,
OpenSSH 6.5 is almost ready for release, so we would appreciate testing
on as many platforms and systems as possible. This release contains
some substantial new features and a number of bugfixes.
Snapshot releases for portable OpenSSH are available from
http://www.mindrot.org/openssh_snap/
The OpenBSD version is available in CVS HEAD:
http://www.openbsd.org/anoncvs.html
Portable OpenSSH is
2003 Jan 17
2
Guessing in key exchange
Hi,
I was using F-Secure SSH V2.0 client to connect openssh server.
Here the relevant part of the client log.
-----------------------------------------------------
local ip = 172.168.29.8, local port = 4870
remote ip = 172.168.29.7, remote port = 22
remote hostname is "172.168.29.7".
Wrapping...
Remote version: SSH-2.0-OpenSSH_3.2.2p1
CBVersionCheck: remote version
2016 Jan 05
14
[Bug 2521] New: subtract buffer size from computed rekey limit to avoid exceeding it
https://bugzilla.mindrot.org/show_bug.cgi?id=2521
Bug ID: 2521
Summary: subtract buffer size from computed rekey limit to
avoid exceeding it
Product: Portable OpenSSH
Version: 6.8p1
Hardware: amd64
OS: Linux
Status: NEW
Severity: minor
Priority: P5
Component: sshd
2013 May 13
1
Session rekeying support in OpenSSH
Hi,
I am using OpenSSH_5.2p1. It seems ssh server doesn't support key
regeneration after a specified amount of time. I manually verified the
OpenSSH_5.2p1 and OpenSSH-6.2 source codes and haven?t found any code
support for session rekeying in both releases.
SSH2 supports session rekeying using the parameter ?RekeyIntervalSeconds?
with default value 3600 seconds (one hour) in both
2003 Apr 11
2
How often should an encrypted session be rekeyed?
Using OpenSSL, is there a preferred/recommended rate of rekeying an
encrypted stream of data? Does OpenSSL handle this for developers
behind the scenes? Does it even need to be rekeyed?
Thanks in advance. -sc
--
Sean Chittenden
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 202 bytes
Desc: not available
2007 Mar 14
1
sshd gets stuck: select() in packet_read_seqnr waits indefinitely
Dear OpenSSH Portable sshd developers,
I'm having a problem where sshd login sessions are occasionally
(as often as once a day) getting stuck indefinitely. I enabled debug
messages and got a backtrace of a stuck sshd, and I think I've found
the bug. I wanted to run it by the list once before filing.
sshd version:
OpenSSH_4.2p1 FreeBSD-20050903, OpenSSL 0.9.7e-p1 25 Oct 2004
2016 May 26
22
[Bug 2573] New: dead sessions cannot be closed with ~.
https://bugzilla.mindrot.org/show_bug.cgi?id=2573
Bug ID: 2573
Summary: dead sessions cannot be closed with ~.
Product: Portable OpenSSH
Version: 3.7.1p2
Hardware: Other
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: ssh
Assignee: unassigned-bugs at mindrot.org
2000 Feb 15
1
Rekeying
Hello,
I apologize that this is slightly off topic.
According to the Internet Draft I found for SSH ver 1
(draft-ietf-tls-ssh-00.txt from Jun 13, 1996), the client or server can
send a SSH_MSG_KEXINIT at any time to force a new key exchange. I looked
through the code for OpenSSH and ssh-1.2.27 and can't find where it does
this. I then searched the Secure Shell mailing list archives and saw
2005 Jun 13
1
rekeying in SSH-2 and session setup?
Dear all,
while playing around with openssh-4.1p1 (trying to add AFS token
forwarding in SSH-2), I noticed that agressive rekeying (as e.g.
employed by regress/rekey.sh, rekeying every 16bytes) seems to disturb
the various forwardings (X11, agent) set up at the beginning of the
session. These do not trigger regression test errors, since the client
does not ask for confirmation from the server for
2014 Jan 24
1
Question Reagrding open SSH
Hi Team,
I have a question regarding open ssh issue.
We have a SFTP automate process to upload file at customer server using ssh key based authentication. But some simultaneously process going in hung state. I have enable verbose mode but I am not able to understand that log. Can you please let us know by below log why we are facing this issue?
While process going in hung state:-
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