On 28/11/05, Josh Grosse <[EMAIL PROTECTED]> wrote:
> On Mon, Nov 28, 2005 at 03:04:45PM -0700, Theo de Raadt wrote:
> > This is why OpenBSD/OpenSSH does not need to hire a spin doctor.
> >
> > Other people do it for us ;)
> >
> > http://www.ssh.com/company/newsroom/article/684/
> >
> > And... thanks to those of you who supported us when they were
> > threatening to sue us years ago..
> >
> There's a little negative spin in that press release:
>
> "...However, OpenSSH deviates from the standards in its SCP (Secure Copy
> Protocol) implementation.
> SSH Tectia Client and Server now incorporate a compatibility mode for
> OpenSSH SCP, which still uses
> the old Secure Shell version 1 (SSH1)...."
$vendor is smoking something very funky... Trace below says OpenSSH
uses protocol 2 just fine.
# scp -v [EMAIL PROTECTED]:groklease .
Executing: program /usr/bin/ssh host wifi-gw, user root, command scp
-v -f groklease
OpenSSH_4.2, OpenSSL 0.9.7g 11 Apr 2005
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to wifi-gw [129.128.5.133] port 22.
debug1: Connection established.
debug1: identity file /home/ckuethe/.ssh/identity type 0
debug1: identity file /home/ckuethe/.ssh/id_rsa type 1
debug1: identity file /home/ckuethe/.ssh/id_dsa type 2
debug1: Remote protocol version 2.0, remote software version OpenSSH_4.2
debug1: match: OpenSSH_4.2 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_4.2
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-cbc hmac-md5 none
debug1: kex: client->server aes128-cbc hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host 'wifi-gw' is known and matches the RSA host key.
debug1: Found key in /home/ckuethe/.ssh/known_hosts:247
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue:
publickey,password,keyboard-interactive
debug1: Next authentication method: publickey
debug1: Offering public key: /home/ckuethe/.ssh/id_rsa
debug1: Server accepts key: pkalg ssh-rsa blen 149
debug1: Authentication succeeded (publickey).
debug1: channel 0: new [client-session]
debug1: Entering interactive session.
debug1: Sending command: scp -v -f groklease
Sending file modes: C0755 2031 groklease
Sink: C0755 2031 groklease
groklease
100% 2031
2.0KB/s 00:00
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug1: channel 0: free: client-session, nchannels 1
debug1: fd 0 clearing O_NONBLOCK
debug1: fd 1 clearing O_NONBLOCK
debug1: Transferred: stdin 0, stdout 0, stderr 0 bytes in 0.3 seconds
debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 0.0
debug1: Exit status 0
--
GDB has a 'break' feature; why doesn't it have 'fix' too?
