Created attachment 18083 [details]
This is my public key

support, please add this key.
thanks
Louis 

Created attachment 18108 [details]
File renamed to icobgr.pub and all enters are removed

Hi Icobgr,

Can you please submit the id_dsa.pub keyfile itself and not a cmd-generated 
version.

The file should begin with a string like "ssh-dss" and end with the e-mail 
string.

Thanks

Created attachment 18120 [details]
Sorry for my mistake. I have made a mistake. I think that this is what you need.

Thanks Hristo for this new key.

Internal ticket created. Will update as soon as we have it uploaded.

This is now done. Resolving.

Please update the STATUS WHITEBORAD with your experience on this issue.
Satisfaction Level: 1 to 5 (5 being the highest)

When I try to login it said that such user "icobgr" do not exist.
I use fo tunneling this:
ssh -4 -i ~/.ssh/id_dsa_openoffice.org -2 -x -L 2402:localhost:2401
tunnel@openoffice.org

I use 2402 port because it didn't want to lisent on 2401. Here what I get when I
use 2401:
[icobgr@icobgr www]$ ssh -4 -i ~/.ssh/id_dsa_openoffice.org -2 -x -L
2401:localhost:2401 tunnel@openoffice.org
Enter passphrase for key '/home/icobgr/.ssh/id_dsa_openoffice.org':
bind: Address already in use
channel_setup_fwd_listener: cannot listen to port: 2401
Could not request local forwarding.

So, when I use 2402 and try to login, I get this:
[icobgr@icobgr www]$ cvs -d :pserver:icobgr@localhost:2402/cvs login
Logging in to :pserver:icobgr@localhost:2402/cvs
CVS password:
Fatal error, aborting.
icobgr: no such user

Where is the problem?

try this:

ssh -2  -x -L 2401:localhost:2401 tunnel@openoffice.org

I don't think you need the -4 (forces IPv4).  Also, it seems as if your id is the same as on your computer, 
you don't seem to need the -i. If you do, it would be, - i ~/.ssh/id_dsa_openoffice.org 

so, let's try that, first. But using port 2402 will result in failure.
louis

Why using port 2402 will result in failure? It is only used to make internal
connection between cvs client and the tunnel. If I use 2401 to listen it didn't
work. I suppose that it maybe because it has a program which also listen on that
port 2401. So, I don't think that the port is the problem.

my understanding is that may interfere with port forwarding here.
louis

You were right. I found which service was capture the 2401 port and stoped it.
Now everythink is working. The site is on.

great.
closing issue.
louis