search for: 5.0p1

Displaying 20 results from an estimated 90 matches for "5.0p1".

Did you mean: 5.0.1
2008 Jul 16
3
openssh 5.0p1: Solaris - Failed to allocate internet-domain X11 display socket.
On Solaris 10 (SPARC & x86), I'm seeing the following error: error: Failed to allocate internet-domain X11 display socket. I tracked this down to this code change between openssh 4.7p1 and 5.0p1: *** openssh-4.7p1/channels.c Mon Jun 25 03:04:47 2007 --- openssh-5.0p1/channels.c Wed Apr 2 15:43:57 2008 *************** *** 1,4 **** ! /* $OpenBSD: channels.c,v 1.270 2007/06/25 08:20:03
2008 Jun 20
1
ForceCommand internal-sftp causes sftp logging to fail (openssh-5.0p1)
Hi guys, I have a server setup with openssh-5.0p1 and use some users as sftp-only chroot accounts. The following configuration yields exactly the result I want: user is chrooted, logs to syslog, all is good. #================================================# Subsystem sftp internal-sftp -f AUTHPRIV -l VERBOSE Match User fredwww ChrootDirectory %h #ForceCommand internal-sftp
2008 Jun 30
2
Build bug and execution bug
The build bug: DESTDIR=$SOMEDIR does not work: mkdir ${HOME}/tools/openssh/openssh-5.0p1/_i/usr/local/etc ${HOME}/tools/openssh/openssh-5.0p1/_i/usr/local/sbin/sshd -t -f ${HOME}/tools/openssh/openssh-5.0p1/_i/usr/local/etc/sshd_config Could not load host key: /usr/local/etc/ssh_host_rsa_key Could not load host key: /usr/local/etc/ssh_host_dsa_key Disabling protocol version 2. Could not load
2008 May 01
2
openssh-5.0p1: sftp transfer logging doesn't appear to work with chroot environment
Hi all, I am running Debian Etch. I've compiled openssh-5.0p1 with pam support. I'd like to use a chrooted sftp environment for my users and also log their sftp file transfers. Currently file transfer logging stops working when I implement a jail. Logging from within the chroot seems like a useful feature. I hope it makes it in sooner rather than later. Here's the contents of my
2008 May 12
1
openssh-5.0p1: sftp transfer logging doesn't appear to work with chroot environment [SOLVED]
On Sun, May 4, 2008 at 12:00 PM, Dan Yefimov <dan at nf15.lightwave.net.ru> wrote: > On Sun, 4 May 2008, john wrote: > > > > What exact steps have you taken to accomplish what Damien proposed? > > > > > Yes sorry Dan, I should have been specific. > > > > I created a file in my chroot root called /home/dev/auth.log > > > > Then I
2008 Jun 23
0
openssh-5.0p1: sftp transfer logging doesn't appear to work with
I've implemented the /dev/log socket inside my chroot environment. I'm able to log the users interactions with the server, but I have one remaining issue. The logs don't contain and usernames or userids. The process ID is logged and we could go through and try to associate the process ID with the user who logged in, but I was hoping to find an easier way. We need to be able to
2008 Apr 04
0
GSSAPI Key Exchange Patch for OpenSSH 5.0p1 (plus an added extra)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 It's that time again! There's been another OpenSSH release, and once again, I'm pleased to announce the availability of my GSSAPI Key Exchange patch for it. Whilst OpenSSH contains support for GSSAPI user authentication, this still relies upon SSH host keys to authenticate the server to the user. For sites with a deployed Kerberos
2008 Aug 27
1
5.1p1 doesn't work, 5.0p1 works fine
5.1p1 disconnects after the password prompt when connecting to my router and UPS. 5.1p1 connects fine to other unix hosts, and my Windows client connects fine to 5.1p1 servers. 5.0p1 works fine everywhere. I've tried ssh -T, ssh -t, permutations with ssh -o Compression=no -o TCPKeepAlive=no, etc, to no avail. I've used the default ssh_config file, and it still fails. Can anyone
2014 May 20
1
wrong key directory
Sirs: Trying to update OpenSSH to version openssh-6.6p1 using openssl-1.0.1g and zlib-1.2.3. Updating both openssl and openssh at same time. Have been running openssh on Solaris 8 machines for years. Has occurred on 3 mahines: After "compiling" openssh, try to start: /opt/openssh/sbin/sshd Get error: Could not load host key: /opt/openssh-5.0p1/etc/ssh_host_rsa_key Could not
2008 Apr 20
3
[Bug 1460] New: openssh-4.9p1.tar.gz configure:15943: error: *** Can't find recent OpenSSL libcrypto
https://bugzilla.mindrot.org/show_bug.cgi?id=1460 Summary: openssh-4.9p1.tar.gz configure:15943: error: *** Can't find recent OpenSSL libcrypto Classification: Unclassified Product: Portable OpenSSH Version: 5.0p1
2010 Apr 15
4
Limit number of connections per user?
I'm working from modified 5.0p1 codebase. What I'm looking for is a mechanism to limit the number of simultaneous connections on a per-user/IP basis. That is, disallow multiple simultaneous logins/authentication of the same user from different IP addresses. e.g.: fred from 10.1.1.1 - accept fred from 10.1.1.2 -- reject while fred is still connected from 10.1.1.1 fred from 10.1.1.1 - OK
2008 Dec 11
2
5.0 vs 5.1 remote command execution
Hello, I am experiencing some strange behaviour that I am hoping someone can shed some light on. OS and kernel: Red Hat Enterprise Linux AS release 4 (Nahant Update 5) Linux host135 2.6.9-67.9hp.7sp.XCsmp #1 SMP Thu Jul 3 18:55:59 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux built both openssh-5.0p1 and openssh-5.1p1 with the following options: ./configure --prefix=/usr
2008 Apr 12
2
[Bug 926] pam_session_close called as user or not at all
https://bugzilla.mindrot.org/show_bug.cgi?id=926 Jan Engelhardt <jengelh at gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jengelh at gmx.de --- Comment #33 from Jan Engelhardt <jengelh at
2009 Sep 01
2
ssh_exchange_identification: Connection closed by remote host
I'm randomly getting the following error on a server from various remote hosts: ssh_exchange_identification: Connection closed by remote host The server is running OpenSSH 4.5p1 w/GSSAPI Key Exchange patch. The hosts connecting to it should all be using OpenSSH 5.0p1 w/GSSAPI Key Exchange patch and using gssapi-keyex authentication. Normally, when I've seen this error, it means
2009 Jul 09
0
Hanging ssh sessions with openssh-5.1p1 and Solaris 8 & 10
Hi, Has anyone had any luck looking into this by any chance ? > On Mon, Aug 04, 2008 at 02:34:23PM -0400, Jeff Wieland wrote: >> 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
2008 Apr 08
3
openssh version 5
Greetings, It just strike me that they are no available version of OpenSSH version 5 or any available versions with the ChrootDirectory option. Any reason why ? Thanks,
2015 May 02
10
[Bug 2392] New: unable to ssh with umac has algorithm. error:Disconnecting packet:corrupted MAC on input.
https://bugzilla.mindrot.org/show_bug.cgi?id=2392 Bug ID: 2392 Summary: unable to ssh with umac has algorithm. error:Disconnecting packet:corrupted MAC on input. Product: Portable OpenSSH Version: 5.0p1 Hardware: PPC OS: Linux Status: NEW Severity: critical Priority: P5
2009 Mar 11
1
ssh hang with ForceCommand=internal-sftp
> /usr/sbin/sshd -oForceCommand=internal-sftp > sftp user at host # This connects as expected. > ssh user at host # This hangs...at least from an end-user's perspective. It would be ideal if the connection terminated gracefully. Do others see this same behavior? If so, is there a fix or configuration change that can implemented to eliminate the hang? I'm using OpenSSH
2008 May 15
0
"ServerAliveInterval" and "ServerAliveCountMax" doesnt work in openssh50?
Hi OpenSSH team, We found that openssh5.0 has a bug with the "ServerAliveInterval" and "ServerAliveCountMax" options. This function doesnt work at all, which means when the Maxtime reached, the ssh will not kill the connection and prompt the infomation "Connection Timedout" as it used to do. We built the openssh5.0p1 code on the a Linux box, and use the
2008 Jun 10
1
ibuf_empty delayed efd
I'm seeing something unusual in 5.0p1. Let me start by saying that I'm on kind of an oddball system (HP NonStop). What I'm seeing is that at the end of an scp session, the server gets stuck in a loop. First I see a shutdown failure, followed by looping on an "ibuf_empty delayed efd 9/(0)" condition. This may have to do with some minor semantic differences in the way the