Issue 6241 - tunnel does not work
Summary: tunnel does not work
Status: CLOSED FIXED
Alias: None
Product: Infrastructure
Classification: Infrastructure
Component: _openoffice.org CVS (obsolete) (show other issues)
Version: current
Hardware: PC Linux, all
: P1 (highest) Trivial (vote)
Target Milestone: ---
Assignee: Unknown
QA Contact: issues@www
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-07-02 07:37 UTC by Martin Hollmichel
Modified: 2003-12-06 14:52 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Martin Hollmichel 2002-07-02 07:37:46 UTC 
tunnel login is now asking for password, does not take empty passphrase any more.

debug: got kexinit: none,zlib
debug: got kexinit: none,zlib
debug: got kexinit:
debug: got kexinit:
debug: first kex follow: 0
debug: reserved: 0
debug: done
debug: kex: server->client 3des-cbc hmac-sha1 none
debug: kex: client->server 3des-cbc hmac-sha1 none
debug: Sending SSH2_MSG_KEXDH_INIT.
debug: bits set: 518/1024
debug: Wait SSH2_MSG_KEXDH_REPLY.
debug: Got SSH2_MSG_KEXDH_REPLY.
debug: Host 'openoffice.org' is known and matches the DSA host key.
debug: bits set: 500/1024
debug: len 55 datafellows 0
debug: dsa_verify: signature correct
debug: Wait SSH2_MSG_NEWKEYS.
debug: GOT SSH2_MSG_NEWKEYS.
debug: send SSH2_MSG_NEWKEYS.
debug: done: send SSH2_MSG_NEWKEYS.
debug: done: KEX2.
debug: send SSH2_MSG_SERVICE_REQUEST
debug: service_accept: ssh-userauth
debug: got SSH2_MSG_SERVICE_ACCEPT
debug: authentications that can continue: publickey,password
debug: try pubkey: /root/.ssh/id_dsa
debug: read DSA private key done
debug: sig size 20 20
debug: authentications that can continue: publickey,password
tunnel@openoffice.org's password:
Comment 1 lsuarezpotts 2002-07-02 07:49:31 UTC 
reassigning to support@openoffice.org. Martin: my understanding is
that kat prefers to have issues assigned to support@ rather than kat@.
Either way, they get to the right place.

Kat, I've experienced this, too, just now. I did not experience it
earlier today.


Am filing an issue with internal CN ops: #10422
-louis
Comment 2 lsuarezpotts 2002-07-02 08:03:24 UTC 
closing
Ops fixed it.
louis
Comment 3 michael.bemmer 2003-03-24 08:23:31 UTC 
As agreed by Louis I will close these resolved fixed support-owned issues now.
If you have trouble with that, please re-open the issue.
Comment 4 michael.bemmer 2003-03-24 08:27:56 UTC 
As agreed by Louis I will close these resolved fixed support-owned issues now.
If you have trouble with that, please re-open the issue.