Apache OpenOffice (AOO) Bugzilla – Issue 3394
request for content developer role
Last modified: 2012-01-29 22:13:52 UTC
I would like to request for the role of content developer for TRU64 UNIX port. I am not sure if this is the right place to go. If not, please direct me to the right place/person. Thanks, Vicky
Martin is the project lead of porting. He will handle this.
I granted you the content developer role. Do you already have ssh access to the cvs ? see http://www.openoffice.org/docs/ddSSHGuide.html for more information. what do you prefer: a tru64 (porting.openoffice.org/tru64) of another name ?
I do not have ssh access to cvs yet. I will look into the website you gave me. Also, I'm new to this so it'll be great if you have point me to some guidelines on how to go about putting up documentations for the port. Once I have the ssh access to cvs, where do I go next? And "porting.openoffice.org/tru64" sounds great! Thanks a lot! Vicky
hi, Vicky, You can continue to use this issue, if Martin and Stefan don't mind, for the ssh2 key. just reassign it to me, louis@openoffice.org. louis
Hi, I have a question about tunnelling. After I typed in the following command, I was asked for the tunnel's password. I tried my passphrase and my password for OpenOffice login. Both didn't work. What should this be? Thanks, Vicky > ssh -x -L 2401:localhost:2401 tunnel@openoffice.org Host key not found from database. Key fingerprint: xirof-tugul-zufag-vylyh-fanop-vybov-fuped-cifif-vagid-hahes-roxox You can get a public key's fingerprint by running % ssh-keygen -F publickey.pub on the keyfile. Are you sure you want to continue connecting (yes/no)? yes Host key saved to /usr/local/home/chanv/.ssh2/hostkeys/key_22_openoffice.org.pub host key for openoffice.org, accepted by chanv Fri Mar 08 2002 15:44:26 -0500 tunnel's password:
Created attachment 1182 [details] public key
I forgot to reassign this to Louis.
Vicky, Please go over the ssh2 instructions. Also, please let's not use IZ for this discussion. you entered a command for ssh 1. You need to enter a command for ssh 2: enter this (copy and paste): ssh -2 -x -L 2401:localhost:2401 tunnel@openoffice.org. But it wont' work because I just received the issue for the key. I'll redirect it now. louis
taska, please load Vicky's key if it is in the proper form. Vicky, what client did you use to create your key? thanks Louis
Vicky, I believe you can use cygwin on Windows or ssh-keygen -t dsa on linux to create your key. It should be in the following format: http://www.openoffice.org/issues/showattachment.cgi?attach_id=1175 Thanks!
Created attachment 1187 [details] public key in correct format
Hi, I used ssh-keygen -t dsa to create the public key. It should be in the correct format. Please let me know if it is okay. Louis, I'm not sure what you meant by 'IZ'. Could me explain what it means please? Also, my ssh actually links to ssh2. That's the reason why I used ssh -x -L 2401:localhost:2401 tunnel@openoffice.org Is this right?
Thanks, the key looks good. I've entered this request for the operations team (PCN8639).
Our operations team reports that the key is missing the user@host segment at the very end. Usually ssh-keygen adds this. Could you take a look? Thanks.
Created attachment 1188 [details] public key with user@host
Hi Taska, For some reason my ssh-keygen didn't add the user@host at the end. I added it manually. Please let me know whether this works. Thanks, Vicky
Okay, we've entered this key. Vicky, please test, and reopen this issue if there's any problem. Thanks!
Hi, I tried the following command and typed in my password that was used to generate my public key, and was unsuccessful in connecting. > ssh -x -L 2401:localhost:2401 tunnel@openoffice.org tunnel's password: tunnel's password: tunnel's password: warning: Authentication failed. Disconnected; no more authentication methods available (No further authentication methods available.). (my ssh is pointing to ssh2, so the -2 option was omitted.) Please let me know what I did wrong. Thanks! Vicky
Good question, Vicki. Louis, our community manager, who usually troubleshoots these things, is out of the office, so I'll see what I can find to figure out what's going wrong here.
Vicky, Please follow the guidelines for using ssh2 laid out in http:// www.openoffice.org/docs/ddSSHGuide.html#HowtoConnect. In particular, you must use ssh -2. Just using ssh invokes ssh -1 protocol which is not good enough; OOo uses ssh -2. The correct command is: ssh -2 -x -L 2401:localhost:2401 tunnel@openoffice.org. Use it and it will work (assuming the key is loaded, etc.). You will be asked for a passphrase, not password. If you are asked for a password, things are wrong. Cheers, louis
Hi Louis, I tried the command with the -2 option and I get a FATAL error. So I used "ssh2 -x -L 2401:localhost:2401 tunnel@openoffice.org" and it asked for tunnel's password, not a passphrase. What could be wrong? Thanks so much for any hints! Vicky $ ssh -2 -x -L 2401:localhost:2401 tunnel@openoffice.org ssh: FATAL: Unknown option -2 $ ssh2 -x -L 2401:localhost:2401 tunnel@openoffice.org tunnel's password: tunnel's password: tunnel's password: warning: Authentication failed. Disconnected; no more authentication methods available (No further authentication methods available.).
I'm reassigning this to louis for him to look at.
hi, the problem I would guess is that you are using a slightly different system. Type in the ip number for Ooo. That may resolve it: 2401:localhost:2401 tunnel@64.125.132.236 (you are using TRU64, i would guess, and perhaps not OpenSSH...?) Anyway, my guess is that using IP will resolve it. I had similar problems when tunneling from my os x terminal. louis
Hi Louis, I tried what you suggested and it didn't seem to work. I got the following messages: > ssh -x -L 2401:localhost:2401 tunnel@64.125.132.236 Host key not found from database. Key fingerprint: xirof-tugul-zufag-vylyh-fanop-vybov-fuped-cifif-vagid-hahes-roxox You can get a public key's fingerprint by running % ssh-keygen -F publickey.pub on the keyfile. Are you sure you want to continue connecting (yes/no)? yes Host key saved to /usr/local/home/chanv/.ssh2/hostkeys/key_22_64.125.132.236.pubhost key for 64.125.132.236, accepted by chanv Wed Apr 17 2002 18:26:06 -0400 tunnel's password: tunnel's password: tunnel's password: warning: Authentication failed. Disconnected; no more authentication methods available (No further authentication methods available.). And if I do the command again, I get the following: > ssh -x -L 2401:localhost:2401 tunnel@64.125.132.236 tunnel's password: tunnel's password: tunnel's password: warning: Authentication failed. Disconnected; no more authentication methods available (No further authentication methods available.). Could something be wrong with my password?? And yes, I am using TRU64. Would that cause any problems? Thanks a lot! Vicky
Hi, Vicky, yeah, it could be your pub key. Before you trash it, let's do this: trash your host keys file ( /usr/local/home/chanv/.ssh2/hostkeys) and any thing else that looks like a file for hosts file, keeping your public key, of course. then try again. You should be prompted, again, to accept.... if it doesn't work, regenerate your key, using ssh-keygen -d, or whatever TRU64 uses (man keygen). Once it is done, attach it hereto and we can start again. It may take some slight tweaking to conform to the proper OpenSSH standard we require... sorry for the delays louis
Created attachment 1405 [details] A new public key
Hi Louis, I tried it again and it still didn't work. So I just sent you a new public key. Please let me know if it's in the correct format. Thanks a lot! Vicky
it seems to be the correct format--but, then, after checking the previous two, they seemed okay too. am now officially depressed. okay, I'll ask Taska to upload this new key; let's see if it works. taska, would you upload this and then reassign to me? thanks louis
Actually, I have another idea.... Vicky, could you actually copy that FATAL ERROR you get when you use -d into the issue here and reassign to support? Thanks.
Hi, I'm having problem tunnelling into OpenOffice. My public key is entered into your database and somehow I can't connect. I'm using the following command and getting the following error messages: > ssh -x -L 2401:localhost:2401 tunnel@64.125.132.236 tunnel's password: tunnel's password: tunnel's password: warning: Authentication failed. Disconnected; no more authentication methods available (No further authentication methods available.). Any idea why this doesn't work? Thanks a lot! Vicky
Vicky, could you tell me the response you get to the following two commands on your system: ssh2 -V ssh -V (both of those are with a capital V.) Thanks.
Hi, here are the responses: > ssh2 -V ssh2: SSH Secure Shell 3.1.0 (non-commercial version) on alphaev67-dec-osf5.1 > ssh -V ssh: SSH Secure Shell 3.1.0 (non-commercial version) on alphaev67-dec-osf5.1 Please let me know if you need anything else. Thanks a lot! Vicky
Vicky, it looks like you're using a version of SSH with which I'm not familiar, and it looks like it's refusing to use Version 2 authentication. Could you send me the results of the following command: ssh --help Thanks.
Hi, this is what I get: (should I get another version of ssh??) Thanks! $ ssh --help ssh: SSH Secure Shell 3.1.0 (non-commercial version) on alphaev67-dec-osf5.1 Copyright (c) 1995-2001 SSH Communications Security Corp SSH is a registered trademark and Secure Shell is a trademark of SSH Communications Security Corp (www.ssh.com). All rights reserved. See LICENSE file for usage and distribution terms. Usage: ssh [options] [user@]host[#port] [command] Options: -l user Log in using this user name. -n Redirect input from /dev/null. +a Enable authentication agent forwarding. -a Disable authentication agent forwarding. +x Enable X11 connection forwarding. -x Disable X11 connection forwarding. -i file Identity file for public key authentication -F file Read an alternative configuration file. -t Tty; allocate a tty even if command is given. -v Verbose; display verbose debugging messages. Equal to `-d 2' -d level Set debug level. -V Display version number only. -q Quiet; don't display any warning messages. -f[o] Fork into background after authentication. With optional 'o' argument, goes to "one-shot" mode. -e char Set escape character; ``none'' = disable (default: ~). -c cipher Select encryption algorithm. Multiple -c options are allowed and a single -c flag can have only one cipher. -m MAC Select MAC algorithm. Multiple -m options are allowed and a single -m flag can have only one MAC. -p port Connect to this port. Server must be on the same port. -S Don't request a session channel. -L listen-port:host:port Forward local port to remote address -R listen-port:host:port Forward remote port to local address These cause ssh to listen for connections on a port, and forward them to the other side by connecting to host:port. +g Gateway ports, i.e. remote hosts may connect to locally forwarded ports. -g Don't gateway ports. +C Enable compression. -C Disable compression. -4 Use IPv4 to connect. -6 Use IPv6 to connect. -o 'option' Process the option as if it was read from a configuration file. -1 [ti] Choose ssh1-protocol fallback type. Mandatory argument 'i' specifies internal emulation, 't' specifies traditional fallback mechanism. -h Display this help. Command can be either: remote_command [arguments] ... Run command in remote host. -s service Enable a service in remote server.
Vicky- I've spoken with some of our ssh experts here, and it appears your version of SSH is one which we're not familiar with (we use OpenSSH). As far as I can tell, your public key is fine; it's something within your SSH client which is somehow refusing to use your ssh key. Is there someone in your office (an IT person, maybe), whom you can speak with to figure out how to convince your client to use the ssh2 key? Thanks.
Will investigate.
are there any updates here ?
The Issue you raised regarding SSH / Public key / CVS has not been updated within the last 1year+. I'm assuming that the Issue has been resolved and may now be Closed... A Closed Issue is a Happy Issue (TM). Many thanks, Andrew Cleaning-up and Closing old Issues as part of: ~ The Grand Bug Squash, pre v3 ~
.