Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Search results

  • * Since the webserver is public but builds should only be run by authorized users, we must secure access to the <tt style="color:DarkGreen">build.php</ could be a problem with ssh keys (see above - [[#Fix web user (apache)]]) or the method CVS uses to
    23 KB (3,394 words) - 22:45, 16 July 2008
  • ...the daily automated builds, a manual build can be started by those who are authorized to do so.<br/> Only authorized users have access to eclipse server. To make password-less connection to e
    25 KB (4,158 words) - 17:59, 19 January 2010
  • *[http://www.youtube.com/watch?v=WU9xYP_NScQ Setting up SSH authorized keys in Eclipse] [http://www.youtube.com/watch?v=Lhwi3z2DyzQ&feature=related] == Setting up SSH keys for committers ==
    12 KB (2,071 words) - 22:14, 3 October 2022
  • ...e user's machine, then the public key is added on the remote machine as an authorized client. The private key is then signed by the client. This allows the user ...between the encryption algorithms that generate the imported and exported keys rather than a misconfiguration.
    7 KB (1,150 words) - 11:42, 2 February 2012
  • ...e user's machine, then the public key is added on the remote machine as an authorized client. The private key is then signed by the client. This allows the user ...between the encryption algorithms that generate the imported and exported keys rather than a misconfiguration.
    7 KB (1,151 words) - 21:11, 6 February 2012

Back to the top