Displaying 20 results from an estimated 20000 matches similar to: "invalid packet type ?"
2008 Feb 09
1
Problems connecting with SSH2
Hello,
I've been using OpenSSH 3.6.1p2 for quite some time at work. We have a
firewall, and I had no problems connecting to external machines.
Today my machine was updated to version 4.1p1 and it has a problem.
When I try to make an SSH2 connection to an external machine,
everything seems to work right up to the very end:
debug1: Authentication succeeded (publickey)
debug1: channel
2005 Apr 28
1
ssh 4.0 under AIX 5.3 password expiration
I have a user who's password has expired (ADMCHG) flag
is set in /etc/security/passwd under AIX 5.3. For
some reason it is not prompting for new passwd. This
worked in 3.9. Any ideas?
Thanks,
Ryan
# /usr/sbin/sshd -d
debug1: sshd version OpenSSH_4.0p1
debug1: private host key: #0 type 0 RSA1
debug1: read PEM private key done: type RSA
debug1: private host key: #1 type 1 RSA
debug1: read
2003 Sep 26
0
openssh 3.7.1p2 linux port problem
Hello,
after upgrading my redhat 8.0 notebook to
openssh3.7.1p2 linux port I now could not login/scp
into it (as root or myself). /var/log/messages said
the authentication was successful, then the connection
closed immediately. I was using the default
sshd_config that comes from the installation (via
rpmbuild from the srpms file under the portable
directory).
(The client connection was initiated
2005 Apr 21
0
openssh 4.0p1 under OSX
I'm having difficulty getting ssh to connect as any
local user under OSX 10.3.8. The odd thing is ssh -l
root localhost works fine as a normal user, whereas
ssh -l themac localhost (or from any host for that
matter) does not.
Thanks
===============================
debug1: sshd version OpenSSH_4.0p1
debug1: private host key: #0 type 0 RSA1
debug1: read PEM private key done: type RSA
debug1:
2003 Jul 10
0
[Bug 615] OpenSSH 3.6.1p2 ON SCO 3.2v4.2 + STRICTMODES -->yes
http://bugzilla.mindrot.org/show_bug.cgi?id=615
Summary: OpenSSH 3.6.1p2 ON SCO 3.2v4.2 + STRICTMODES -->yes
Product: Portable OpenSSH
Version: 3.6.1p2
Platform: ix86
OS/Version: other
Status: NEW
Severity: major
Priority: P2
Component: sshd
AssignedTo: openssh-bugs at mindrot.org
2002 Jul 25
0
scp hangs
Hello,
When running scp (from openssh-3.4p1) on our linux systems we are
experiencing hangs after authentication. According to the debug
messages, authentication succeeds but the file itself is not
transferred. Openssh is built using OpenSSL 0.9.6d.
The command
scp foo 192.168.1.111:/tmp
will hang until the connection times out.
Below are the client and server side logs. An strace of the
2000 Dec 06
1
openssh-2.3.0p1 (Linux) fails using options with dss key
I'm trying to change my local setup from ssh2 to openssh-2.3.0p1. I need
captive comands and specific environments for each key, i.e. the
"command=XXX" and "environment=X=y" options. Unfortunately I *also* need
to support the existing ssh2 client for a transition period, since it's
impractical to change all user's environments to openssh in one go.
I have converted
2003 Jul 11
0
OpenSSH 3.6.1p2 +UnixWare 7.1.1 +SSH2 + PasswordAuthenticatio n no + PermitEmptyPasswords yes (followup)
Greetings,
complete debug below
> -----Original Message-----
> From: Ben Lindstrom [mailto:mouring at etoh.eviladmin.org]
> Sent: 10 July 2003 03:32
> To: Vikash Badal - PCS
> Cc: 'openssh-unix-dev at mindrot.org'
> Subject: Re: OpenSSH 3.6.1p2 +UnixWare 7.1.1 +SSH2 +
> PasswordAuthentication no + PermitEmptyPasswords yes (followup)
>
>
>
> Would be
2000 Nov 30
1
Problem and Patch: Multiple keys in ssh.com V2 agent
Hello!
I recently discoverd a problem with ssh.com's ssh-agent2 and OpenSSH:
If I have more than one key in my agent, then the agent tries to
authenticicate me with every one of them at the OpenSSH server; but none
of them is a valid key for that server. The Problem is that the Server
increments the authctxt->attempt at every of that tries. So even if you
want to login with a password at
2002 Mar 11
0
Password-Authentication with openssh-3.1p1 fails
Hallo out there,
I've got a strange problem after updating my openssh-installation
from 2.9.9p2 (SuSE-package) to openssh-3.1p1 (Installation from the
source with a modified src.rpm). I will give you as much information
as possible and I hope there is anybody who can help me. I asked in
detail in usenet-groups but nobody had any idea to fix my problem by
configuration.
My system is a
2003 Jul 09
3
OpenSSH 3.6.1p2 ON SCO 3.2v4.2 + STRICTMODES -->yes
Greetings,
I have compiled OpenSSH-3.6.1p2 on SCO 3.2v4.2 and
the following problem occurs:
I am unable to login as root using when strictmode is set to yes.
output of debug:
Failed none for root from 192.168.1.1 port 1199 ssh2
debug1: userauth-request for user root service ssh-connection method
publickey
debug1: attempt 1 failures 1
debug2: input_userauth_request: try method publickey
debug1:
2002 Mar 12
0
[Bug 159] New: Password-Authentication with openssh-3.1p1 fails
http://bugzilla.mindrot.org/show_bug.cgi?id=159
Summary: Password-Authentication with openssh-3.1p1 fails
Product: Portable OpenSSH
Version: 3.1p1
Platform: ix86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: sshd
AssignedTo: openssh-unix-dev at mindrot.org
2001 Apr 04
0
Heh?
On Tue, 3 Apr 2001, Niels Provos wrote:
> Paul, something is broken in your openssh install.
Definately. But is it the client or the server?
I've sent it to the portable OpenSSH bug address.
I'm using OpenSSH 2.5.2p2-1.7 on a RedHat 7.0 with all updates.
Sometimes I can login fine, and sometimes I can't. It actually seems to
almost alternate,
2001 May 04
1
2.9: RSAAuthentication problems
I'm using an OpenBSD 2.9 snapshot on i386. "ssh -V" reveals
OpenSSH_2.9, yada yada.
I generated a keypair using ssh-keygen and accepting defaults. I copied
the public key to another box, stuck it in ~/.ssh/authorized_keys with
host restriction and then tried to use it. Failed. Removed the host
restriction, still failed. Just get asked for password.
So I cut out the extra box.
2002 Aug 08
0
Bugzilla bug entry #342
I may have found a similar issue with plain old RSAAuthentication. After
upgrading to 3.4p1 on Solaris 8, I am no longer able to use RSAAuthentication
with
PermitRootLogin forced-commands-only
Following is output from sshd -d -d:
Connection from 10.100.100.8 port 39955
debug1: Client protocol version 2.0; client software version OpenSSH_3.4p1
debug1: match: OpenSSH_3.4p1 pat OpenSSH*
Enabling
2003 Feb 24
1
[Bug 502] New: sshd fails when "Compression yes" set on HPUX
http://bugzilla.mindrot.org/show_bug.cgi?id=502
Summary: sshd fails when "Compression yes" set on HPUX
Product: Portable OpenSSH
Version: 3.5p1
Platform: HPPA
OS/Version: HP-UX
Status: NEW
Severity: normal
Priority: P2
Component: sshd
AssignedTo: openssh-unix-dev at mindrot.org
2003 Jul 17
1
possible bug + patch : OpenSSH 3.6.1p2 +UnixWare 7.1.1 +SSH2 + P asswordAuthentication no + PermitEmptyPasswords yes
Greetings,
When PasswordAuthentication no + PermitEmptyPasswords yes
SSH2 allows access to a passwordless account without a valid key.
This is my patch:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
wormhole# diff -u auth2-none.c.old auth2-none.c
--- auth2-none.c.old Thu Jul 17 06:23:24 2003
+++ auth2-none.c Thu Jul 17 06:44:42 2003
@@ -100,7 +100,9 @@
if (check_nt_auth(1,
2001 Jun 26
1
OpenSSH 2.9p2 with PAMAuthenticationViaKbdInt
When using PAM to do password authenticaion the attempt/failure counter
appears to be getting confused. This is using a rh62 system with the
openssh-2.9p2-1 rpms...
On the client side...
[matthewm at toadhall (7) matthewm]$ grep Auth /etc/ssh/ssh_config
RhostsAuthentication no
RhostsRSAAuthentication no
HostbasedAuthentication no
RSAAuthentication no
PubkeyAuthentication yes
2003 Sep 22
1
Problem with non-interactive shells on Sol8 with 3.7.1p1
We recently started upgrading OpenSSH on our Sol8 systems and we've run
into a problem were we can run commands on a remote system since we
installed 3.7.1p1. The debug output from sshd is attached below. We use
PAM in our environment, and have since 2.9.9p2. I think most of the
systems were running 3.4p1 prior installing 3.7.1p1 and they were working
- the only thing we replaced was
2002 Aug 12
1
PermitRootLogin=forced-commands-only does not work with UsePrivilegeSeparation=yes
Using openssh-3.4p1 on Linux I noticed that PermitRootLogin=forced-commands-only
does not work if UsePrivilegeSeparation is enabled; but it does work if privsep
is disabled.
Here are excerpts of debug from the server.
-----------UsePrivilegeSeparation DISABLED-------
...
Found matching DSA key: 56:9d:72:b0:4f:67:2e:ed:06:e7:41:03:e2:86:52:0d^M
debug1: restore_uid^M
debug1: ssh_dss_verify: