Apache OpenOffice (AOO) Bugzilla – Issue 48005
Submission of SSH2 Key for access to www component
Last modified: 2008-05-17 23:17:36 UTC
I want to upload the website developed for bn.openoffice.org. I'll be grateful if my SSH2 key is accepted, and I'm given CVS access. Thank you, Soumyadip Modak
Created attachment 25377 [details] SSH2 Public Key
Confirming that we have assigned Soumyadip the job of handling the website.
Reassign issue to ssh2key
support please add Soumyadip key to the group. thanks louis
Issue taken, will revert on the status. Thanks Kavitha-Helpdesk
As per your request, the attachment has been deleted. Thanks Kavitha-Helpdesk
I'm still unable to connect to tunnel.openoffice.org, by following instructions from http://www.openoffice.org/scdocs/ddSSHGuide.html. I'm receiving this error: Connection closed by 64.125.133.202 Any suggestions ?
Filed an internal ticket to operations, will let you know the status. Thanks, Kavitha-Helpdesk
The public key has been uploaded, please verify. Thanks, Kavitha-Helpdesk
The same response: Connection closed by 64.125.133.202 Any settings that I should have set at my end ?
btw note that sayamindu's report echoes that of computerdork's in http://www.openoffice.org/issues/ show_bug.cgi?id=47994.
Unfortunately I'm being forced to reopen the issue, since I still cannot ssh into tunnel.openoffice.org. I'm still getting : Connection closed by 64.125.133.202 Can Ms.Kavitha please spell out the details how to ssh into the server ? Thanks
reassigning to support. louis
I have filed an internal ticket for this issue.Will revert when I get further information. Aarthi-Helpdesk.
Can you please provide the output from the "ssh -v ...", the user's IP address, time of attempt and the screenshot of the message ? Please confirm that you're not behind a corporate firewall which prohibits direct ssh access. Thanks, Kavitha-Helpdesk
Additional information as requested by Ms.J.Kavitha (jkavitha at openoffice.org) $sudo iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination $ifconfig eth0 Link encap:Ethernet HWaddr 00:11:09:99:86:7B inet addr:192.168.1.3 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::211:9ff:fe99:867b/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:204612 errors:0 dropped:0 overruns:0 frame:0 TX packets:200687 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:290477871 (277.0 MiB) TX bytes:13585299 (12.9 MiB) Interrupt:20 Base address:0xa000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:59524 errors:0 dropped:0 overruns:0 frame:0 TX packets:59524 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:15213433 (14.5 MiB) TX bytes:15213433 (14.5 MiB) ppp0 Link encap:Point-to-Point Protocol inet addr:59.93.163.69 P-t-P:59.93.160.1 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1 RX packets:201525 errors:0 dropped:0 overruns:0 frame:0 TX packets:199438 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:285629455 (272.3 MiB) TX bytes:9158707 (8.7 MiB) $ date Tue May 10 01:08:12 IST 2005 $ ssh -2 -x -L 2401:localhost:2401 tunnel@openoffice.org -v OpenSSH_3.9p1 Debian-1ubuntu2, OpenSSL 0.9.7e 25 Oct 2004 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to openoffice.org [64.125.133.202] port 22. debug1: Connection established. debug1: identity file /home/soumyadip/.ssh/id_rsa type -1 debug1: identity file /home/soumyadip/.ssh/id_dsa type 2 debug1: Remote protocol version 1.99, remote software version OpenSSH_3.6.1p2 debug1: match: OpenSSH_3.6.1p2 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_3.9p1 Debian-1ubuntu2 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 'openoffice.org' is known and matches the RSA host key. debug1: Found key in /home/soumyadip/.ssh/known_hosts:3 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: Trying private key: /home/soumyadip/.ssh/id_rsa debug1: Offering public key: /home/soumyadip/.ssh/id_dsa Connection closed by 64.125.133.202
Thanks for the information. Will revert soon on the status as i get the update from the operations. Thanks, Kavitha-Helpdesk
Created attachment 25940 [details] Screenshot of the error I'm facing while trying to ssh into openoffice.org
The error is fixed now. Please check and revert on any clarifications. Thanks, Kavitha-Helpdesk
Created attachment 25953 [details] New SSH key
It's working. Thanks a lot. However, it seems I'm having problems with the passphrase of the previous key. Can you please replace it with the new key I just posted. Thanks a lot, and sorry for being so sloppy.
I have updated the engineers.Will update you as soon as possible. Thanks Karthik-Helpdesk
The new key has been uploaded.Closing the issue. Thanks Karthik-Helpdesk
Thanks a lot.
The Issue you raised has been marked as 'Resolved' and not updated within the last 1 year+. I am therefore setting this issue to 'Verified' as the first step towards Closing it. If you feel this is incorrect, please re-open the issue and add any comments. Many thanks, Andrew Cleaning-up and Closing old Issues ~ The Grand Bug Squash, pre v3 ~ http://marketing.openoffice.org/3.0/announcementbeta.html
As per previous posting: Verified -> Closed. A Closed Issue is a Happy Issue (TM). Regards, Andrew