Issue 34622 - Attach SSH2 Key to Sango Laguage Project
Summary: Attach SSH2 Key to Sango Laguage Project
Status: CLOSED FIXED
Alias: None
Product: Native-Lang
Classification: NLC
Component: www (show other issues)
Version: OOo 1.0.1
Hardware: All All
: P2 Trivial
Target Milestone: ---
Assignee: mdkidiri
QA Contact: Unknown
URL:
Keywords: oooqa, TSK-DEF
Depends on:
Blocks:
 
Reported: 2004-09-25 18:58 UTC by ooomod
Modified: 2008-05-17 23:28 UTC (History)
2 users (show)

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


Attachments
A new SSH2 public key for Sango Language Project (1.21 KB, text/txt)
2005-02-02 17:21 UTC, mdkidiri
no flags Details
A new SSH2 public key for Sango Language Project (1.21 KB, text/txt)
2005-02-02 17:24 UTC, mdkidiri
no flags Details
A better SSH public key in -rsa format for Sango (294 bytes, text/txt)
2005-02-04 18:31 UTC, mdkidiri
no flags Details
A better SSH public key in -dsa format for Sango (675 bytes, text/txt)
2005-02-04 18:32 UTC, mdkidiri
no flags Details
The ultimate DSA/SSH2 public key for Sango Lg Proect (602 bytes, text/txt)
2005-02-26 22:12 UTC, mdkidiri
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description ooomod 2004-09-25 18:58:08 UTC
Louis,
could you please set up the Sango Native-Lang Project?
Desired domain name: "sg"
Username of the Project Lead: mdkidiri

JCA signed and sent.

Thanks,

Charles.
Comment 1 lsuarezpotts 2004-11-17 21:37:27 UTC
project created.  
Louis
Comment 2 mdkidiri 2005-02-02 17:21:40 UTC
Created attachment 22136 [details]
A new SSH2 public key for Sango Language Project
Comment 3 mdkidiri 2005-02-02 17:24:02 UTC
Created attachment 22137 [details]
A new SSH2 public key for Sango Language Project
Comment 4 mdkidiri 2005-02-02 17:40:29 UTC
Would you, please, attach the new SSH2 public Key to Sango Language Project. 
It would be great if you could do it as soon as possible. Thanks in advance!
Marcel Diki-Kidiri
Comment 5 mdkidiri 2005-02-03 22:06:54 UTC
Please, consider resolving this request as soon as possible. Thanks!
Marcel Diki-Kidiri
Comment 6 Unknown 2005-02-03 22:37:28 UTC
Hello Marcel,

Please attach your key file instead of this version. The standard open source 
version is sufficient. If using the ssh-keygen, please don't use the "-e" 
option which will output the 'SECSH Public key format'

The key should look like this "ssh-rsa AAAAB3Nz.........== <e-mail address>"

Reducing priority to P2, since this is not site down or security issue.

Thanks
Comment 7 mdkidiri 2005-02-04 13:17:56 UTC
I am using a SSH2 client to generate the keys and I systematically got files 
starting with a comment like this:

---- BEGIN SSH2 PUBLIC KEY ---- Comment: "[2048-bit rsa, YSB@PCYSB, Fri Feb 04 
2005 10:22:08]"AAAAB3 ...

Should I just remove the comment heading and let the file start just 
with "AAAB3 ..." ?

Up to now I have got the same result whether I use option "-t dsa" or "-t rsa" 
or nothing.
Comment 8 mdkidiri 2005-02-04 18:31:15 UTC
Created attachment 22213 [details]
A better SSH public key in -rsa format for Sango
Comment 9 mdkidiri 2005-02-04 18:32:51 UTC
Created attachment 22214 [details]
A better SSH public key in -dsa format for Sango
Comment 10 mdkidiri 2005-02-04 18:40:47 UTC
Hello,

I have been using PUTTY to create better files just as you like them :-)
But I don't know which format between -rsa and -dsa should be prefered. So I 
propose both for you to choose. Please let me know which one you set up after 
you did it. Also, how do I do to remove unwanted attachments? 
Thank you very much!
Marcel Diki-Kidiri
Comment 11 lsuarezpotts 2005-02-05 06:41:30 UTC
Hi
We require DSA. 
As to unwanted attachments: it's hard to remove them. Easier not to worry about it.

Support, would you be able to upload the better DSA key from Sango?
thanks


-louis

Comment 12 mdkidiri 2005-02-05 09:59:58 UTC
Hello,
Thanks for the informations! It seems to me that the file "sgdsa.pub" already
attached is the right one. Please, check its format and if it is good, just
mount it.
Thanks a lot again!
Marcel Diki-Kidiri
Comment 13 Unknown 2005-02-08 19:59:00 UTC
Not the format we were looking for, but will try anyway.
Using the -dsa format. Opened internal ticket.
Comment 14 Unknown 2005-02-08 20:05:25 UTC
This is now done. Please verify.
Comment 15 mdkidiri 2005-02-26 22:12:08 UTC
Created attachment 23072 [details]
The ultimate DSA/SSH2 public key for Sango Lg Proect
Comment 16 mdkidiri 2005-02-26 22:21:55 UTC
Please Support,

I could not change the status of this issue to REOPENED nor its resolution to 
NEW or UNCONFIRMED. Could you do that for me?
Thanks again!

Marcel
Comment 17 Unknown 2005-02-28 18:28:42 UTC
Re-opening to add key.
Comment 18 Unknown 2005-02-28 18:33:38 UTC
Marcel,

I opened an internal ticket to get this key uploaded.
Comment 19 Unknown 2005-02-28 21:07:03 UTC
And, it is done. Closing.
Comment 20 mdkidiri 2005-03-04 13:11:54 UTC
Hi!
Using Cygwin on Windows XP Pro, I entered the following command line :

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

I got connected and then got the following prompt :

Enter tunnel@openoffice.org's password :_

When I entered my public key phraseword, I got the following message :

Permission denied, try again :

After three tries, I deconnects saying : 

Permission denied (publc key, password, key-interactive)

After sevreval unsuccessful tries, I am wonderinf if this is not due to the 
presence of several keys attached to my repository? If I have to redo 
everything from the begining, starting with the generation of a new pair of 
certificates, then I whish all the previous keys to be removed. Is that 
possible?  Only what I ultimately want is to get through and go ahead with my 
work without wasting so much time on scratches!
Thanks for your time and help!
Marcel.
Comment 21 Unknown 2006-10-25 14:12:26 UTC
Are you still having problems with your key.
Comment 22 lsuarezpotts 2006-10-26 17:05:07 UTC
reassigning to mdkidiri
Comment 23 ace_dent 2008-05-17 21:24:49 UTC
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
Comment 24 ace_dent 2008-05-17 23:28:06 UTC
As per previous posting: Verified -> Closed.
A Closed Issue is a Happy Issue (TM).

Regards,
Andrew