Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | acces to cvs-tunnel failed | ||||||
---|---|---|---|---|---|---|---|
Product: | Infrastructure | Reporter: | Martin Hollmichel <nesshof> | ||||
Component: | _openoffice.org CVS (obsolete) | Assignee: | Unknown <non-migrated> | ||||
Status: | CLOSED FIXED | QA Contact: | issues@www <issues> | ||||
Severity: | Trivial | ||||||
Priority: | P2 | CC: | issues | ||||
Version: | current | ||||||
Target Milestone: | --- | ||||||
Hardware: | PC | ||||||
OS: | Windows 2000 | ||||||
Issue Type: | DEFECT | Latest Confirmation in: | --- | ||||
Developer Difficulty: | --- | ||||||
Attachments: |
|
Description
Martin Hollmichel
2001-02-09 16:38:55 UTC
Created attachment 69 [details]
public key
This is the output Joerg Brunsmann get. His public key is attached to this issue. debug: next auth method to try is publickey debug: try pubkey: /home/joerg/.ssh/id_dsa debug: PEM_read_bio_DSAPrivateKey failed debug: read DSA private key done Enter passphrase for DSA key '/home/joerg/.ssh/id_dsa': debug: read DSA private key done debug: sig size 20 20 debug: authentications that can continue: publickey,password debug: next auth method to try is publickey debug: next auth method to try is password tunnel@64.208.42.22's password: debug: authentications that can continue: publickey,password debug: next auth method to try is password This is the key I added to the tunnel file a few days ago and received word from Jorg that he was able to access the repository after this. The server has been responding slowly and could be timing out. I will continue to investigate, and if this continues please let me know to take further action. Thank you Kathy I am closing this issue after hearing from Jorg that he is able to establish a tunnel. Kathy As agreed by Louis I will close these resolved fixed kat (support)-owned issues now. If you have trouble with that, please re-open the issue. As agreed by Louis I will close these resolved fixed kat (support)-owned issues now. If you have trouble with that, please re-open the issue. |