Apache OpenOffice (AOO) Bugzilla – Issue 40218
SSH2Guide Update
Last modified: 2013-08-05 13:55:22 UTC
The anchor named Mac is targeted by mac. This causes a dead bookmark in the TOC. Fixing this will (soon) break the related FAQ: http://documentation.openoffice.org/faqs/site_maintainers/003.html. Under http://www.openoffice.org/scdocs/ddSSHGuide.html#Mac the MacSSH link needs change from hhttp://www.macssh.com to http://www.macssh.com. Firefox pops up an error box and cannot handle hhttp files.
http://www.openoffice.org/scdocs/ddSSHGuide.html#tunneling from the TOC is inactive; http://www.openoffice.org/scdocs/ddSSHGuide.html#cygwin or http://www.openoffice.org/scdocs/ddSSHGuide.html#windows could be good replacements
the last entry is wrong. The "Tunneling..." link in the left menu TOC should be changed from http://www.openoffice.org/scdocs/ddSSHGuide.html#tunneling to http://www.openoffice.org/scdocs/ddSSHGuide.html#HowtoConnect.
I've checked out this file (from www/www/docs/ddSSHGuide.html), and will work through the links as I go, then will attach the file to this issue. I could not see the scdocs dir. Did I grab the right file? It seemed like the newest. Please advise if I should grab a different file?
Created attachment 21361 [details] list of changes made to file www/www/docs/ddSSHGuide.html
Created attachment 21362 [details] updated file www/www/docs/ddSSHGuide.html
There's still a bad link, second one up from the bottom, i think, in the list of further documentation. It connects to a site, but doesn't find content.
maybe http://www.linuxhelp.ca/guides/ssh/ is the replacement link? ... or omit it?
reassigning from www (oops!) to issues@www.
thanks diane! I'll take it over... Cheers Louis
reassigning to louis...
*** Issue 40581 has been marked as a duplicate of this issue. ***
thanks diane! I tried fixing things and then realized the whole document was wretched and needed major updating. So I reorganized it and pruned a lot of irrelevant stuff. It needs a small section on putty: I couldn't get it to work last night using an old key as they use a unique format but one which is all the same easy to change to OpenSSH format, which is what we use. if you would like to review the new doc.... And yeah, scdocs is hidden; only some of the files have been placed where we can access them. cheers louis
wow Louis, cool beans!
Here is a tutorial on tunnelling with PuTTY: http://www.cyberknights.com.au/doc/PuTTY-tunnelling-HOWTO.html Authored by Leon and assisted by other PLUG members.
we have some very good notes written in the mail archives which could be used to enhance the ddSSHGuide.html document: http://documentation.openoffice.org/servlets/ReadMsg?list=dev&msgNo=2198 http://documentation.openoffice.org/servlets/ReadMsg?list=dev&msgNo=2216 http://documentation.openoffice.org/servlets/ReadMsg?list=dev&msgNo=2212
thanks Diane, Sigh. I wish then the Documentation project would just rewrite the doc to their satisfaction. :-/ I'll re-address it again.... but at the mo' it's not super high priority. later Louis
more feedback: http://documentation.openoffice.org/servlets/ReadMsg?list=dev&msgNo=2344 no worries, Louis... someone will get to it eventually. This makes a good place to gather more info while folks are thinking about it out loud. We can justify the edits under the category of continuous process improvement. :) I'm willing to work at it too, but like you, it will be a bit before I can make time for it.
Willy wrote a tutorial for PuTTY: http://documentation.openoffice.org/servlets/ReadMsg?list=dev&msgNo=2321
It will be best to link my guide from the ddSSHGuide page, since it contains images (not too big actually), but it's your decision Louis I'm willing to help if you need too. Just let me know Thanks
This faq http://documentation.openoffice.org/faqs/site_maintainers/003.html contains the preliminary steps that Jean requested. Also, a mail message suggests a possible layout and may include more details: http://documentation.openoffice.org/servlets/ReadMsg?list=dev&msgNo=2346
adding myself to cc
changing summary to reflect evolution. adding Lindaw Louis
Created attachment 23000 [details] Linux Guide
thanks, Willy! I've also added Lindaw to this issue. I'm occupied by other things right now but would like to address this issue sooner than later. best Louis
I grabbed a copy of the code via page source, and am working to update this page.
Created attachment 23073 [details] rewrite started; but unfinished. Plan was to Copy&Paste details from FAQs.
I worked on updates to the ddSSHGuide.html by grabbing a copy of the page source, then editing it. I grabbed the file yesterday, but didn't write that I grabbed it until this morning. I put several hours into it, so there may be something useful there, but maybe not too. Meanwhile, Linda has something in the works too after a discussion with Louis, so we likely are duplicating efforts. I'm not sure what to do from here, and the way this issue stands helps to confuse things more, so I've put my stuff on the table and am backing away. :) Please let me know if or how I can help on this task. There's plenty enough to do where I can easily redirect myself. I will also act as support if you need it. I hope it's helpful that I attached my work and not a hindrance. I found it hard to decide what I should do. I'm reassigning this to lindaw. :) If that is not ok, send it back to me. At least this way things will be clear, so we don't have to wonder what we should do. :) I hope this helps!
Created attachment 23080 [details] Revised PuTTY Section, Added Tunnelling Guide
PuTTY can be used to create SSH Keypair and it worked. Jean Hollis Webber has prove that (he used PuTTY 0.56 to produce SSH Keypair). I have correct this in the guide i uploaded. Also, i clarifies information that i succedded in creating tunneling, not keys with PuTTY. I also add my guide here.
.
Hi Linda, Would it be possible for you to tell us what the period means, so that we do not have to guess how to interpret it? Thank you! :) Diane
Sorry for the (.) post everyone. I had a computer issue when filling out the comment section. I just wanted to add that I am working on the page and should have a revision out very soon. My day job has a way of getting in the way sometimes. ;-) Linda
adding self so I can track this louis
I added Willy's fine version. Thanks!! I ought to have done it sooner and assigned it to myself. Lindaw, are you still working on a version? If so, it may not be that necessary....then again, all good things can get better :-) Thanks Louis
Adding Willy's version is not the only fix for this page Louis. The code isn't correct and the information and steps need to be updated. I have been unable to work on this, as the day job tends to get in the way sometimes.
True. My guide was only for Windows user, not for all platforms. The documents should be revised on the structure itself Linda: Can you point what should be updated. Maybe i can help restructuring the document? Thanks
reopening. I'll look at the guide again. From what I can tell, the changes that need to be made are fairly minor. If anyone else wants to fix them, be my guest :-) louis
Since Louis reopened this ticket I am listing him as the owner.
what exactly needs to be done to this guide to fix it?
There are some broken link : - Using the Desktop Terminal which should be pointed to http://www.openoffice.org/docs/ddSSHGuide.html#usingterminals - Content which should be pointed to http://www.openoffice.org/docs/ddSSHGuide.html#mac both of the reference wasn't there Willy
Reassigning ticket
I'll take it... :)
beside the broken links, what else should we do to update this document?
Created attachment 36883 [details] ssh guide-latest
comments for the latest version uploaded by louis : - Use either Cygwin, which we recommend Cygwin, as it works well, although setup can sometimes be difficult. --> i think it will be best to remove the sentence "Use either Cygwin, which" and just say, "We recommend Cygwin... " - But: Your CVSROOT needs to point to your localhost to use the tunnel. --> as long you are not in a directory of other CVS repository and do not set a variable named CVSROOT, it will be empty and it's adequate to make a tunnel to OOo. - Shouldn't submitting keys should be done first before creating your first tunnel connection? SInce it will take few hours/days to confirm this. So, people that have configured their client should have submitted their public key and their public key has been processed by support team before they can start tunneling. I suggest that we make another section, "generating public key" before "submitting your keys" and then followed by "Tunneling". It will a lot cleaner for new person who don't know about CVS/tunneling (like i did at the beginning) :D
Reset QA Contact to new default
This Guide is definitifly no longer needed. close issue