similar to: openssh 3.7p1 and 3.7.1p1 Solaris problems

On 13 Mar 99, Luke Kenneth Casson Leighton had this to say about about cmdat utility...: > this small utility can be used to run an arbitrary program by clicking > right-mouse-button on a directory. the default action is to run "ssh.exe" > on a Samba server and a command prompt "cmd.exe" on an NT server. Excuse me for being ignorant, but what is ssh.exe? A win32

Hi all, We've got server-based application that runs on CentOS. Until now, most of our customer's end-users have accessed the application using either PuTTY or Teraterm. I was asked yesterday to try and find internationalized add ons or alternatives for our new Asian customers (Japan, Korea and China atm). I figured if anyone would be able to recommend terminal emulation

Hi everyone. I want to point out some facts about TTSSH that may be relevant to the claims of trademark infringement by OpenSSH. I'll confine my opinions to another message :-). I released my product, which has always been named "Teraterm SSH" and is usually abbreviated to "TTSSH", to the public in May 1998. TTSSH is a free software Windows client for the SSH1 protocol.

http://bugzilla.mindrot.org/show_bug.cgi?id=648 Summary: Cannot login using SecureCRT since openssh 3.7p1 Product: Portable OpenSSH Version: -current Platform: ix86 OS/Version: Linux Status: NEW Severity: critical Priority: P2 Component: sshd AssignedTo: openssh-bugs at mindrot.org

SSH server specs: ----------------------- Redhat Linux 6.2 Custom built 2.2.17 kernel OpenSSL 0.9.5a (update from RedHat). OpenSSH 2.5.1p1 I am using my Linux box as an Internet gateway. I wanted to keep the box as secure as possible while still having the functionality I needed. The only way to connect to my server is through SSH. A fair majority of the time I am attempting to

http://bugzilla.mindrot.org/show_bug.cgi?id=696 Summary: PAM modules getting bypassed when connecting from f- secure ssh client to openssh 3.7p1 or 3.7.1p1 servers Product: Portable OpenSSH Version: 3.7.1p1 Platform: Sparc OS/Version: Solaris Status: NEW Severity: minor Priority: P2

hi, i don't understand how 3.6.1p2 breaks ssh1.... On Fri, Sep 12, 2003 at 10:27:15AM -0700, Mike Bethune wrote: > Hello, > the new way this works breaks windows ssh clients using v1 (I know, who cares :) > since when these options are enabled and you connect w/v1, the server asks: > Password: > Response: > and I guess these clients (tested putty, pscp, vandyke) expect

I see that commercial SSH version it is possible to run sshd in SSH1 using DES (i.e, accepting SSH-DES clients). I understand from Damien Miller that Cisco routers also run in only SSH1 DES mode. Is it possible in openSSH to configure sshd (compile-time/runtime) to run sshd in SSH1 or SSH2 mode and accept SSH1 or SSH2 DES clients ? [I would like to be able to run sshd in SSH1/DES mode ] Is

No, I just think 15 years or so is more than enough time to have addressed the issue. On Thu, Mar 26, 2015 at 14:05:08 -0700, Dan Kaminsky wrote: > So, this isn't your problem and you don't respect the people's whose > problem it is. > > On Thu, Mar 26, 2015 at 12:43 PM, Iain Morgan <imorgan at nas.nasa.gov> wrote: > > > On Thu, Mar 26, 2015 at 11:55:18

On Thu, Mar 26, 2015 at 11:55:18 -0700, Dan Kaminsky wrote: > You're right. My argument the is the next build of OpenSSH should be > OpenSSH 7, and the one after that 8, then 9, then 10. No minor releases? > Sure, go ahead. Deprecate the point, > > Do you manage any machines running SSHv1? > If by "running" you mean accepting SSH1, of course not. From a

On Tue, 3 May 2016, Colin Watson wrote: > Debian takes the latter approach. Specifically, we have an > "openssh-client-ssh1" binary package that includes only scp1, ssh1, and > ssh-keygen1 binaries; we do not ship any server-side SSHv1 support. I > modelled this on Fedora's approach, which is basically the same aside > from a slightly different package name. >

Hello, I was searching for this information virtually everywhere, but as I couldn't find it - I'm asking here. I was wondering, why setting the Compression Level was removed in SSH2, and if on, is always set to 6. In SSH1 it was possible to set the Compression Level from 1 to 9. I have made some tests with Compression Levels using scp: SSH1, compression 9 (highest available for

Hi, the OpenSSH installation script for Cygwin still creates a SSH1 host key by default. My question is, wouldn't it make more sense to drop all auto-generation of SSH1 keys from the default installation procedure? I mean, nobody should use SSH1 anymore, right? Or should the script stick to it for some reason? Corinna -- Corinna Vinschen Cygwin Project Co-Leader Red Hat

I think I've found a bug with sshd handling audit events for commands (like scp) over ssh1 connections. Specifically, after updating to a recent FreeBSD 6.x with audit support, I'm getting log messages like these when using scp over ssh1: Sep 12 14:13:16 <auth.info> bm55 sshd[12335]: Accepted rsa for xxx from A.B.C.D port 2981 Sep 12 14:13:16 <auth.crit> bm55 sshd[12335]:

OpenSSH still has this feature, SSH-1.2.27 no longer has it. Admittedly it can be useful sometimes, even though I'd prefer this to be done using a trivial shell wrapper, which would be the UNIX way of doing things. Not being able to call OpenSSH's ssh by another name (say ``ssh1'') can get in the way when having to maintain two versions of ssh in parallel because the ``ssh ->

Hello, I am using the latest prepackaged version of wine (apparently 0.0.20010326) under Debian/unstable and I am completely unable to do anything network related. I tried 'Ping Plotter' as root and TeraTerm Pro as both root and regular user. I also tried Becky, but that's another thing entirely. All these applications did not seem to have access to the network at all. I am using the

Hi Mr newbie here. Using 32-bit Ubuntu 11.10 and Wine 1.3.28. I have installed a Creative PCI Modem and that works well as /dev/modem from things like putty. I've done the link ln -s /dev/modem ~/.wine/dosdevices/com6 so it's now my com6 within wine. However, using teraterm the response from the modem is bitty and slow and pretty useless. If I do something like AT\r the OK\r does come

To allow easier targeting of users of old protocols I would find it useful for the syslog "Accepted" messages to be more uniform. 1. Include the string "ssh1" for ssh1 connections as is done for ssh2 connections. 2. Change the "publickey" message for ssh2 connections to specify which publickey, "dsa" or "rsa". This is already the case for

Mr. Lindstrom, I am trying to upgrade from ssh1 to ssh2. I am getting the following error when I start sshd: Disabling protocol version 2. Could not load host key SSHD does start, however, ssh1 is functional, but ssh2 is not. Please advise, William 770-671-1888, ext-240 -------------- next part -------------- An HTML attachment was scrubbed... URL:

On Solaris 8, I have ssh 3.1.0 and on other box Sol 7 I have 1.2.26 (min version for comtable with ssh 3), I checked also /etc/ssh2/sshd2_config file ## SSH1 compatibility # Ssh1Compatibility <set by configure by default> # Sshd1Path <set by configure by default 2) generate key for ssh3 # ssh-keygen2 -P /etc/ssh2/hostkey