MediaWiki API result

This is the HTML representation of the JSON format. HTML is good for debugging, but is unsuitable for application use.

Specify the format parameter to change the output format. To see the non-HTML representation of the JSON format, set format=json.

See the complete documentation, or the API help for more information. 

{
    "batchcomplete": "",
    "continue": {
        "gapcontinue": "Serial_farming_on_Graham",
        "continue": "gapcontinue||"
    },
    "warnings": {
        "main": {
            "*": "Subscribe to the mediawiki-api-announce mailing list at <https://lists.wikimedia.org/mailman/listinfo/mediawiki-api-announce> for notice of API deprecations and breaking changes."
        },
        "revisions": {
            "*": "Because \"rvslots\" was not specified, a legacy format has been used for the output. This format is deprecated, and in the future the new format will always be used."
        }
    },
    "query": {
        "pages": {
            "415": {
                "pageid": 415,
                "ns": 0,
                "title": "Resolving UWindsor Internet Connectivity Issues",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "=University of Windsor 2022 Connectivity Issues=\n==Notice==\nThe content of this page is current as of Nov. 4, 2022. Should you have issues please create a SHARCNET ticket [mailto:help@sharcnet.ca help@sharcnet.ca] or [mailto:preney@sharcnet.ca email Paul Preney] (SHARCNET staff at UWindsor) to seek more assistance.\n\n==Overview==\n\nIn June 2022, the University of Windsor experienced a serious cyber-security incident, e.g., [https://www.uwindsorsupport.ca/node/3 notice/update page for the incident]. Since the University of Windsor has significantly restricted network service access that affects everyone using the University of Windsor's network.\n\nTo be clear, one is using the University of Windsor's network when:\n* one is physically connected to such on-campus,\n* one is using any of the campus wireless networks, or\n* one is using GlobalProtect VPN (when it is activated/connected).\notherwise one is not on the University of Windsor's network. \n\nIf one is '''not''' on the University of Windsor's network (assuming GlobalProtect VPN, if it is installed, is inactive on your computer), then one should be able to connect normally to external-to-the-UWindsor network resources without issues assuming your network, ISP, etc. is not otherwise blocking you from connecting to various network services.\n\nIf one needs to use the University of Windsor's network, e.g., from home or elsewhere using GlobalProtect VPN installed and activated, then the content of this should help you connect to Digital Research Alliance of Canada (formerly Compute Canada) / SHARCNET resources.\n\nFinally, should you need to submit a ticket to UWindsor's ITS, you can do so via [https://uwindsor.teamdynamix.com/TDClient/1975/Portal/Requests/ServiceCatalog the appropriate link on this page].\n\n===Unofficial Open Source Linux Global Protect Client===\n\nThe official (proprietary) Linux GlobalProtect VPN client program does not work properly under all Linux distributions, e.g., under Ubuntu it reports an \"SSL handshake error\" just when it should start working. Additionally, the official client also doesn't remember one's credentials for 30 days, etc. and prompts one to enter their login, password, and do MFA every single time.\n\nThere is a better, unofficial open source '''Global Protect OpenConnect''' client program that establishes the VPN, behaves better, and is configurable, e.g., one can have to NOT set the default route to rout everything through the UWindsor VPN. The latter may be an issue, e.g., if nothing is done then when you are not at the U traffic not destined to UWindsor can be routed through the UWindsor VPN. (Instructions concerning this appear later on this page.)\n\n==Connectivity From Outside the UWindsor Network==\n\nYou should have no issues when outside the UWindsor network accessing Digital Research Alliance of Canada / SHARCNET resources. If you do have issues:\n\n* ensure that if Global Protect VPN is installed, it is turned off / not active, and,\n* your own and/or your ISP's firewall is not blocking access.\n\n==Connectivity From the UWindsor Network==\n\nIf you are inside the UWindsor Network using a wired or a wireless connection, without SentinelOne or Global Protect VPN installed, know you will only be able to connect to HTTP and HTTPS pages using your web browser. Nothing else will work without further configuration. If all you need to access are web pages using HTTP and/or HTTPS links, then nothing further needs to be done.\n\nShould you need to use anything other than HTTP and/or HTTPS web pages, then you must either:\n* if the machine you are using is '''owned by the University of Windsor''', then the SentinelOne software can be installed on it for full Internet access (local or external to the University network), or,\n* if the machine you are using is '''not owned by the University of Windsor''', then the Global Protect VPN software must be installed.\n\nIf you are unsure if the SentinelOne software is installed on your computer, see [https://uwindsor.teamdynamix.com/TDClient/1975/Portal/KB/ArticleDet?ID=144482 this link]. Your department's computer staff will be able to help you with installing SentinelOne.\n\nTo obtain and install Global Protect VPN on your computer:\n* If using Windows or MacOS:\n*# Go to https://securelogin.uwindsor.ca to download the appropriate Global Protect VPN client.\n*# Install the downloaded client.\n*# Run the Global Protect VPN client program.\n*# In the window that pops up (or look in your status/task bar for an \"Earth\" icon and click it) prompting you for a connection gateway, enter '''securelogin.uwindsor.ca''' and click the '''Connect''' icon.\n*# A browser window will open prompting you to login using your UWinID, password, and will require you to use MFA (e.g., approve the login using your phone).\n* If using Linux (unofficial open source client):\n** NOTE: Generally using this is better than using the official GP VPN client which doesn't work under all Linuxes (including common ones such as Ubuntu).\n*# Follow the installation instructions at [https://github.com/yuezk/GlobalProtect-openconnect].\n*# After installation, the connection gateway to use is <code>securelogin.uwindsor.ca</code>. Test that this works.\n*# Optional: To have only UWindsor traffic flow through the VPN, install [https://github.com/dlenski/vpn-slice vpn-slice] following the instructions on that page (after checking whether or not your distribution's package manager has a package for this).\n*#* Edit <code>/etc/gpservice/gp.conf</code> so that <code>openconnect-args</code> is set to be: <code>openconnect-args=--script \"vpn-slice 137.207.0.0/16 10.0.0.0/8 %192.168.0.0/16 %172.17.0.0/16\"</code>.\n*#* %192.168.0.0/16 ensures the 192.168/16 network address range is not part of the VPN. Most person's home LAN addresses are in the 192.168. range. Modify or delete accordingly per your situation.\n*#* %172.17.0.0/16 is a typical docker0 network address. Modify (if you use Docker) or delete.\n*#* NOTE: Running <code>vpn-slice --help</code> will output help concerning command line options.\n*#* Reconnect to the UWindsor VPN for these settings to take effect.\n* If using Linux (official client):\n** NOTE: Currently Global Protect VPN does not appear to work properly with at least Ubuntu --use the unofficial Global Protect OpenConnect software as that does work (see above) instead.\n*# On the https://www.uwindsor.ca page search for '''Global Protect VPN Linux''' and look in the results for sometihng like \"Installing GlobalProtect VPN client on Linux\" and click on that link.\n*#* As of this writing it is [https://uwindsor.teamdynamix.com/TDClient/1975/Portal/KB/ArticleDet?ID=120611 this link].\n*# If you are not already logged in to the UWindsor page, you will need to log in by clicking the '''Sign in''' link at the top-right hand side of the page.\n*#* ASIDE: Logging in is necessary to see the content which links to the download link.\n*# Under '''Related Articles''' there will be a link to download Global Protect VPN for Linux. Click the link.\n*# On the page that comes up download the appropriate file(s) for your Linux. To help determine which file(s) are needed, note the following:\n*#* If your computer runs on an Intel or Ryzen/Threadripper/EPYC CPU you will need to download the '''amd64''' file(s).\n*#* If your computer runs on an ARM CPU you will need to download the '''arm''' file(s).\n*#* If your computer is running Debian or Ubuntu Linux you will need to download the '''.deb''' file(s).\n*#* If your computer is running RedHat, Fedora, SUSE, etc. Linux you will need to download the '''.rpm''' file(s).\n*#* Realistically, you'll only need the '''UI''' file(s) which installs a graphical tool to use. (The non-UI file installs a command-line only tool that isn't easy to use.)\n*#* If your Linux doesn't support .deb or .rpm files then you will need to download the .tar file and manually install the program. (Follow the instructions given in the tarball.)\n*# If you are not using the KDE desktop environment, before installing Global Protect VPN install KDE, e.g.,\n*#* Under Debian/Ubuntu run <code>sudo apt install kde-standard</code>.\n*#* Otherwise consult your distribution's documentation on how to install KDE.\n*#* ASIDE: Global Protect VPN requires libraries such as QtNetwork, etc.\n*# Install Global Protect VPN.\n*# In the window that pops up (or look in your status/task bar for an \"Earth\" icon and click it) prompting you for a connection gateway, enter '''securelogin.uwindsor.ca''' and click the '''Connect''' icon.\n*# A browser window will open prompting you to login using your UWinID, password, and will require you to use MFA (e.g., approve the login using your phone).\n\nAfter Global Protect VPN is installed and active, you should be able to do the following:\n* connect to any Digital Research Alliance of Canada (formerly Compute Canada) compute cluster login node using SSH\n\nThat said, one still cannot do the following:\n* Globus Connect Personal to transfer files\n* SSH to any of your Digital Research Alliance of Canada '''cloud''' nodes\n** NOTE: You will need to open a ticket with ITS to have them allow this for you and your research team.\n* Connect using VNC to [https://docs.alliancecan.ca/wiki/VNC Digital Research Alliance of Canada VDI nodes]\n** NOTE: You will need to open a ticket with ITS to have them allow this for you and your research team.\n* Connect using SSH, rsync, and other protocols/tools to any other HPC clusters, e.g., CERN, EuroHPC, XSEDE (Access), etc.\n** NOTE: You will need to open a ticket with ITS to have them allow this for you and your research team.\n\n==Work-Around: Connecting to SHARCNET/Compute Ontario/Alliance Resources If Only HTTP/HTTPS Are Available==\n\nIf only HTTP and/or HTTPS are only available then the ability to make full use of various tools to access SHARCNET, Compute Ontario, and/or Alliance systems and resources is limited. Fortunately, a number of clusters are running instances of [https://docs.alliancecan.ca/wiki/JupyterHub#JupyterHub_for_universities_and_schools JupyterHub] which will allow you to connect to the various Alliance clusters to use [https://docs.alliancecan.ca/wiki/JupyterHub#JupyterLab JupyterLab] which will enable you to:\n* use a terminal window on that cluster,\n* use a graphical environment on that cluster (if such is needed),\n\n===Using JupyterHub===\n\n# Go to the [https://docs.alliancecan.ca/wiki/JupyterHub#JupyterHub_on_clusters JupyterHub web page] of the desired cluster.\n# Log in with your Alliance username and password.\n# Select the desired account (if you've more than one available).\n# Specify the amount of time (maximum) you want for this session.\n#* NOTE: The session is a Slurm job. Once the maximum time has been reached, the job will be killed. It is recommended to keep the time asked for restricted to the amount of time you will actively use Jupyter, e.g., 2 or 3 hours.\n# Specify the number of cores needed.\n#* Typically this should be one unless you want to test your program with multiple cores, etc.\n#* If you will be using MPI programs, remember to use <code>srun</code> to run your MPI programs in the terminal window within Jupyter.\n# Specify the total amount of RAM needed.\n#* Ideally keep this figure low to below 4000M per CPU core.\n# Only if you will be using a GPU, specify the desired GPU configuration.\n# Specify JupyterLab for the user interface. (This is the newest and most useful interface.)\n# Click the '''Start''' button.\n\nAfter clicking the '''Start''' button, wait for Jupyter to start.\n* It will timeout after 5 minutes. If it times out, then try it again. It such persists reduce the number of cores, RAM, GPUs, etc. being asked for and try again. If needed, submit a ticket to [mailto:support@computecanada.ca support@computecanada.ca] ask for help with his and/or report a problem connecting.\n\nOnce JupyterLab starts use the Launcher (or File > New Launcher) to start a '''Terminal''' window or '''Desktop''' to start a graphical environment.\n\nKnow there is no need to use an <code>salloc</code> session since one is inside a Slurm job within JuptyerLab. Consequently since this is within a Slurm job, <code>$SLURM_TMPDIR</code> is also set and can/should be used when relevant.\n\n==Work-Around: Connecting to a Cloud Node With SSH==\n\nIf you are unable to SSH to your cloud node but you are able to SSH to a compute cluster login node, then you can use SSH's \"JumpHost\" feature to connect to your cloud node's SSH server. To do this run the following command:\n* <code>ssh -J YOUR_DRAC_USERNAME@DRAC_COMPUTE_CLUSTER.computecanada.ca YOUR_CLOUD_USERNAME@YOUR_CLOUD_IP_ADDRESS</code>\nwhere:\n* <code>YOUR_DRAC_USERNAME</code> is your Digital Research Alliance of Canada username\n* <code>DRAC_COMPUTE_CLUSTER</code> is a desired Digital Research Alliance of Canada's compute cluster name\n* <code>YOUR_CLOUD_USERNAME</code> is the username you log in with SSH on your cloud node\n* <code>YOUR_CLOUD_IP_ADDRESS</code> is your cloud node's IP address or DNS name\n\nWhat the \"JumpHost\" feature does is connect to the \"JumpHost\" machine first and then connects to the desired target machine. This does mean you will need to enter in your password twice: the first time is on the compute cluster login node and the second time will be the password for your cloud instance.\n\nNOTE: You can also use JupyterHub (see earlier on this page), open a Terminal window, and then ssh to your cloud node as well.\n\n==Other Items==\n\n===Running a Licence Server @uwindsor.ca===\n\nIf you need to use proprietary software on SHARCNET, Compute Ontario, Alliance systems where the software requires a licence server which must be physically located on the University of Windsor campus, know this can be done and has always involved doing the following:\n\n# Set up the licence server at a specific IP and port on campus.\n** It is advised to enlist the help of a UWindsor Technician and/or ITS to do this.\n# Enlist the help of a UWindsor Technician and ITS to ensure that IP and Port will be able to be accessed from outside of the UWindsor network.\n# If the cluster you want to use does not allow Internet access from its compute nodes, or, if ITS wants more security than anyone from anywhere on the Internet can access that IP and port, then submit a ticket to [mailto:support@computecanada.ca support@computecanada.ca] asking for a tunnel to be opened up with your research team's jobs to the IP and port AND ask from which DNS name (or IPs) where such queries will appear to be coming from.\n** The latter allows ITS to limit the ability to successfully connect to that IP and Port which helps reduce possible security issues.\n# Arrange to test such with after such as been set up.\n\nThis is very manual process and involves staff within SHARCNET/Compute Ontario/Alliance as well as University of Windsor staff (e.g., technicians and ITS) and requires testing. Nicely, after such has been successfully tested, however, one is able to focus on running research jobs on the cluster (as long as the licence server is up-and-running). Before going down this path, however, we encourage all researchers to first search for and have a look at (if it exists) the software they are using in our [https://docs.alliancecan.ca Documentation Wiki] --a number of programs have specific pages detailing what needs to be done in order to get things to work.\n\n===Opening a Ticket With UWindsor's ITS===\n\nTo open a ticket with UWindsor's ITS, see [https://uwindsor.teamdynamix.com/TDClient/1975/Portal/KB/ArticleDet?ID=11372 this link], or:\n* Go to https://www.uwindsor.ca .\n* Search for \"ITS Open Ticket\".\n* Click on the [https://www.uwindsor.ca/itservices/support/ticket Open a Ticket] link."
                    }
                ]
            },
            "355": {
                "pageid": 355,
                "ns": 0,
                "title": "SSH",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "SSH (secure shell) is a secure method of logging into another computer over the network, and is the only way to access the various SHARCNET machines.  It is usually installed by default under Linux and OS X (Mac).  A free versions can be downloaded for Windows machines.\n\n__TOC__\n\n= Linux, Mac and Cygwin =\n\nUnder Linux ,OS X (Mac), and Windows Cygwin the OpenSSH commands (ssh, sftp and scp) should be available on the command line. \n\n==Public Key Authentication (PKA) between MAC and SHARCNET clusters==\nYou won\u2019t have to type your password when connecting to any SHARCNET cluster when doing\nsomething over SSH, such as: ssh, sftp, scp, rsync, and secure port forwarding. Follow these\ninstructions to install the Public Key Authentication (PKA) on your MAC:\n\n  '''On the MAC:'''\n  \n  From a terminal window on the Mac, go to subdirectory .ssh and do command:\n  \n      ls -lat\n  \n  Start by generating your personal set of keys:\n  \n      ssh-keygen -b 2048 -t rsa\n  \n  Then, when prompted, hit enter three times. Check it by doing command:\n  \n      ls -lat\n  \n  You should see two new files: \u201cid_rsa\u201d, and \u201cid_rsa.pub\u201d.\n\n \n '''On the remote SHARCNET machine:'''\n \n  You must log into the remote SHARCNET machine using the standard ssh method. In your\n  account\u2019s home directory, create a new directory named \u201c.ssh\u201d, if it doesn\u2019t already exist:\n  \n      cd\n      mkdir .ssh\n  \n  Make sure that directory .ssh is accessible only to your account:\n   \n      chmod 700 .ssh\n\n\n '''Back on the MAC:'''\n \n  Open another Terminal window, and navigate to the .ssh directory in your Home. Secure copy\n  your \u201cid_rsa.pub\u201d key file to the remote SHARCNET server, providing the remote server\u2019s user account\n  password when prompted:\n \n     scp  id_rsa.pub username@remoteserver:/path/to/home/.ssh/\n \n  Specific example:\n \n     scp  id_rsa.pub nickc@hound.sharcnet.ca:/home/nickc/.ssh/\n  \n  Keep this Terminal window open after the file has transferred. We will use it to test\n  the public key authentication (PKA) procedure, to ensure it has been activated properly.\n\n\n\n '''Back on the remote SHARCNET machine:'''\n  \n  Drop into your .ssh directory:\n  \n      cd\n      cd .ssh\n  \n  If you have a \u201cauthorized_keys\u201d file do following command:\n  \n      wc authorized_keys\n  \n  to see how many lines you have in that file.\n  \n  You should see in subdirectory .ssh the id_rsa.pub file you just uploaded. Now, add its\n  contents to a file named \u201cauthorized_keys\u201d:\n  \n      cat id_rsa.pub >> authorized_keys\n  \n  If the \u201cauthorized_keys\u201d file doesn\u2019t exist, the command will create one for you, and if\n  the \u201cauthorized_keys\u201d file already exists, the command will simply add the info from your\n  public key to it.\n  \n  Issue commnd wc again to see the number of lines in file \u201cauthorized_keys\u201d:\n  \n      wc authorized_keys\n  \n  Now, log out of that SSH session from the remote SHARCNET machine.\n\n\n\n '''Back on the MAC:'''\n  \n  Connect to the remote machine again using SSH. If all went fine you should not enter any\n  passwords or passphrases this time, since public key authentication (PKA) has been activated.\n  \n  Also try: sftp, scp, rsync.\n\n= Windows =\n\nYou can run the command line OpenSSH as on Linux and MacOS if you want by installing the entire [http://www.cygwin.com/ Cygwin] tool set for Windows or just [http://sshwindows.sourceforge.net/ OpenSSH recompiled for Windows].  You can also use the graphical PuTTY and WinSCP programs or the old non-commercial version of SSH Secure Shell for Workstation.\n\n== PuTTY and WinSCP ==\n\nSHARCNET recommends downloading and installing the graphical PuTTY SSH suite along with the WinSCP program based on it.  We strongly recommend to generate and use ssh keys (using the programs puttygen and pageant, which are available on the Putty web site) to connect to our clusters (instead of using passwords) - this is both more convenient (you don't have to type your password every time), and much more secure (hackers won't be able to sniff out your password). See the section [[#Using ssh keys]] below.\n\n=== Installing ===\n\nDownload the windows putty installer from the [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY homepage] (click the download link and pick the installer) and the WinSCP installer from the [http://winscp.net WinSCP homepage] (click the download link and pick the installation package).  Note that the WinSCP installer will ask about installing a Spyware Terminator.  This is not recommend as it is not required to access SHARCNET systems.\n\n=== Logging In ===\n\nRun ''PuTTY'' from ''Programs'' ''PuTTY'' on the ''Start'' menu.  This will open up PuTTY connection window\n\n[[Image:putty_initial.png|center]]\n\nEnter the full host name of the cluster to connect to in the ''Host Name'' box (e.g., ''graham.computecanada.ca'') and click the ''Open'' button.  If this is your first time connecting to the cluster, you will get the unknown key window\n\n[[Image:putty_newkey.png|center]]\n\nYou can pick ''Yes'' to store a copy of the servers key.  Your system will then store a copy of the server's key and only warn you next time you connect if the key has changed.  If you do see a message in the future about the stored key not matching, it could theoretically mean someone was spoofing being our server in order to collect your password, but more likely means we updated our system without preserving our old key.\n\nThis will then open a terminal connection to the login node on the desired SHARCNET cluster\n\n[[Image:putty_terminal.png|center]]\n\nOnce you enter your SHARCNET user name and password you will be presented with a shell prompt where you can enter commands. (If you don't want to type your password every time you connect to our clusters, see the section [[#Using ssh keys]] below.)\n\n=== Transfering Files ===\n\nRun ''WinSCP'' from ''Programs'' ''WinSCP'' on the ''Start'' menu.  This will open up WinSCP connection window\n\n[[Image:winscp_initial.png|center]]\n\nEnter the full host name name of the cluster to connect to in the ''Host name'' box (e.g., ''graham.computecanada.ca''), your SHARCNET user name and password in the ''User name'' and ''Password' boxes, and click ''Login''. (If you don't want to type your password every time you connect to our clusters, see the section [[#Using ssh keys]] below.) If this is your first time connecting to the cluster, you will get the unknown key window\n\n[[Image:winscp_newkey.png|center]]\n\nYou can pick ''Yes'' to store a copy of the servers key.  Your system will then store a copy of the server's key and only warn you next time you connect if the key has changed.  If you do see a message in the future about the stored key not matching, it could theoretically mean someone was spoofing being our server in order to collect your password, but more likely means we updated our system without preserving our old key.\n\nYou will then be presented with a side-by-side listing of your files on your computer (on the left) and the SHARCNET system you connected to (on the right).\n\n[[Image:winscp_folders.png|center]]\n\nTo copy files around, drag and drop between the left and right panes.  A file that starts with a period is considered to be hidden in UNIX and will not be displayed in a terminal by the <tt>ls</tt> command unless the <tt>-a</tt> (all) flag is used.\n\n=== Using ssh keys ===\n\nFor convenience, and for security reasons, we strongly recommend using ssh key authentication instead of a password to connect to our clusters. It can be done under Windows using two more putty executables (available from the [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Putty download page]) - puttygen.exe and pageant.exe. Download them into the same folder as the other putty binaries (putty.exe). Make sure to download \"A. Windows installer for everything except PuTTytel\" which is half-way down the download screen. \n\nTo generate an ssh key pair, execute puttygen.exe. You'll be presented with this window:\n\n[[Image:puttygen1.png|center]]\n\nNext, you press the \"Generate\" button. The program will ask you to randomly move the mouse cursor around. Once it's done, the key pair will be generated, and you will see something like this:\n\n[[Image:puttygen2.png|center]]\n\nThen you have to come up with a passphrase - something you can remember, but something which cannot be easily guessed. It doesn't have to be a single word - it can be a phrase, with spaces. Please don't use your SHARCNET password as a passphrase! And please choose a passphrase (don't leave the fields blank) - this is important for security.\n\nAfter that, you should press the button \"Save private key\" - choose some appropriate name (e.g., \"sharcnet.ppk\"):\n\n[[Image:puttygen4.png|center]]\n\nFinally, using your mouse, highlight the content of the window \"Public key for pasting into OpenSSH authorized_keys file\",\n\n[[Image:puttygen5.png|center]]\n\ncopy it (Ctrl-Insert), and paste as one line at the end of your ~/.ssh/authorized_keys file on SHARCNET: simply login to SHARCNET using your ssh client (putty.exe), execute \"mkdir -p .ssh && cat >> .ssh/authorized_keys\", press \"Shift-Insert\" to paste the key to the file, and then press  \"Return\" once and finally press \"Ctrl-d\". You should make sure this file has proper permissions, by executing \"chmod og-rwx .ssh/authorized_keys\".\n\nAt this point, you have created a matched pair of ssh keys - one is private, and is residing on your Windows computer (*.ppk file; please don't copy it to SHARCNET, and don't share it with anyone!); the second is a public key, which you pasted as one line in the ~/.ssh/authorized_keys file on the remote  SHARCNET cluster. \n\n==== Permissions of public keys====\nThe public key generated by PuTTygen must be placed in the \"authorized_keys\" file  and satisfy the following conditions:  \n      (1) The file name must be \"authorized_keys\"\n      (2) the file \"authorized_keys\" can contain one or more public keys\n      (3) but each public key must be one line\n      (2) additional characters can be appended to the end of the public key in each line\n      (3) permissions of file  \"authorized_keys\" must be set to octal 600 (rw- --- ---)\n      (5) the \"authorized_keys\" file must be placed in subdirectory  \"~/.ssh\"  on the remote host\n      (6) the permissions for the subdirectory \"~/.ssh\" must be set to octal 700 (rwx  --- ---)\n\nIf above conditions are not met the public key authentication will fail. To verify/set these conditions use following commands:\n      chmod 600 ~/.ssh/authorized_keys\n      chmod 700 ~/.ssh\n      wc ~/.ssh/authorized_keys\n\n====Configuring Pageant ====\nPageant can be loaded on demand or can be setup to load  when you start Windows.\n=====When Pageant is not running ... =====\n... you can execute the program \"pageant.exe\" from Windows as follows:\n Click on Start and select \"All Programs\"\n  locate PuTTy and move cursor to the right and select Pageant and click on it\n   \nIf you get a small \"Pageant Error\" icon with the message \"Pageant is already running\" then click on OK and\ngo to the next subsection \"When Pageant is running ...:\n\nOtherwise it will immediately become an icon:\n\n[[Image:pageant1.png|center]]\n\nDouble-click on the icon to get this window:\n\n[[Image:pageant2.png|center]]\n\nThen press the button \"Add key\", and choose the ppk file you created with puttygen.exe (see above). It will ask for your passphrase - enter it now. Then press \"Close\", and you are good to go. As long as the program runs (stays as icon), you can use putty.exe to login to our clusters, and you will not be asked any passwords (or passphrases). \n\n=====When Pageant is running...=====\n... it means that pageant.exe has already been set up to execute automatically every time you restart Windows - and most probably\nwith an empty passphrase so you do not need to provide the passphrase when you restart Windows.\n\nTo have Pageant start up and load the key automatically whenever you log into\nyour Windows desktop we need to create a shortcut in your Startup folder as follows:\n\nGo to the Startup folder by right-clicking the Start button, select Open, double-click on the Programs\nfolder, then double-click on the Startup folder. Inside the Startup folder, right-click and select\nNew -> Shortcut. In the \"Type the location of the item\" text box, enter the full path to the Pageant\nprogram followed by the full path to the key file.\n\nFor example,\n\n\"c:\\program files\\putty\\pageant.exe\" \"c:\\documents and settings\\esumbar\\pka-putty\\mykey.ppk\"\n\nClick Next. Enter \"mypageant\" (or a name of your choice) in the \"Type a name for this shortcut\" box,\nthen click Finish.\n\nYou can also add the option -c to the \"Type the location of the item\" text box, followed by an argument\nwhich is the pathname of an executable.\n\nIf -c and argument are included - it means that the executable (argument) will be executed next, i.e.\nonce pageant.exe terminates.\n\nExample: If following is entered into the \"Type the location of the item\" text box:\n\n \"C:\\Program Files\\PuTTY\\pageant.exe\"  \"C:\\Documents and Settings\\Nick.DAISYLAND\\My Documents\\SHARCNET\\private.ppk\" -c \"C:\\Program Files\\PuTTY\\putty.exe\"\n\nthen pageant.exe will add the private key pointed by the second full path to the key file and after\nthat the program putty.exe will open up the folder \"C:\\Program Files\\PuTTY\" for the user to\nselect one of the executables in that folder.\n\nNext time Windows is restarted the key embedded in the shortcut will be loaded automatically and in this\ncase putty will be started since we had \"-c and argument\" included !\n\nYou will be asked the enter the passphrase only when Windows is started.\n\n====Configuring a PuTTy Saved Profile which uses agent forwarding====\nOnce you connect from Windows to a remote server and your keys are loaded automatically you will not\nbe required to enter the passphrase. If you like to make a new connection from this server to\nanother server and avoid passwords and passphrase then you need to use \"agent forwarding\".\nFollowing instructions show how this can be accomplished and also how to save this session in PuTTy\nso next time you are not required to set these options again:\n\n      click on the PuTTY icon and select \"Session\" on left side\n      Enter in the Hostname or IP, etc ... on right side\n      Enter a name in the \"Saved Sessions\" field\n\n      Under Connections -> SSH -> Auth    click on Auth\n      and Check \"Attempt authentication using Pageant\"\n\n      Under \"Session\" Click Save\n\n      double-click on Open to start connection\n\nNext time all you need is to \"Load\" the name in the \"Saved Sessions\" field that you saved in PuTTy.\n\n====WinScp====\nWinScp.exe (the file copy utility; see [[#Transfering Files|above]]) also works with pageant.exe, by default. You simply launch WinScp, and type in the address of the cluster (e.g., orca.sharcnet.ca), your login name, and then click on \"Login\" - you will be connected to the cluster without been asked for a password or a passphrase - as long as pageant.exe is running."
                    }
                ]
            }
        }
    }
}
Retrieved from "https://helpwiki.sharcnet.ca/wiki/Special:ApiHelp"