TRACC Wiki - User contributions [en]

Private/Public Key Authentication

2026-04-15T14:51:02Z

Ley: /* Configuring WinSCP */

==Creating a Private/Public Key Pair==

If you have never use public key authentication before, you will have to start by creating a key pair. Once the key pair is created, you need to keep the private key in a safe location. Never upload the private key, and never send it by Email. Whoever has your private key can use it to try logging in to ARROW. So, treat the private key as a secret at all times.

The easiest way to prepare a key pair is the use of "puttygen", part of the "putty" software on Windows. Pressing the Windows Key together with R will open a window where you enter "puttygen". Once you press "Ok", the software opens up:

[[File:Puttygen1.png]]

We can go with the defaults and just click on the "Generate" button. Some randomness depends on you moving the mouse around on the screen. Once enough random data is gathered, the private and public key will be generated.

[[File:Puttygen2.png]]

Once the keys have been generated, you need to store the private key in a easy to find location on your local file system. I recommend creating a folder "Keys" within your "Documents" folder, but any other location is fine as well. The idea is that you may easily forget where the key is stored when you need it a later point in time.

[[File:Puttygen3.png]]

Click on "Save private key", which will create the following dialog box for you:

[[File:Puttygen4.png]]

In an ideal world, assigning a password for your private key would be best, but that also means that you may have to enter that password every time you use the key, which can be a problem. Not assigning a password is one more reason to never risk losing this private key file.

Navigate to the "Keys" folder in the "Documents: folder, and give the key a meaningful name. Something that tells you what it is used for, like "arrow-private". The extension ppk is automatically added when the key is saved.

Regarding the public key: It is not necessary to save the public key. When loading a private key, the public key is automatically displayed again at the top of the "puttygen" window. It looks somewhat like this:

==Uploading the public key to one of the ARROW login nodes==

The "puttygen" window still shows the public key at the top.

<PRE>
ssh-rsa AAAAB3NzaC1yc2EAfAADAQABAAABAQDOHgbwUYAAo+BMpvskvLw6eTqqs8OVUMSbAIobbC2/518PpJ/b
jW0n9NM4jlNJlEpuT79ZSv5RwSW8rP82qtcLdSEisxhXkyRLLjbzRWQSGxlVUI+K6MfZeFRYD+nqEH4Q1nSvxWJM
FigswLuWsygcJnGxv0FBGBP7pUrK5pz6AEv5Blf0MCuy0bvuIGhOYEMO4JeId6WYrAwJmZ3mjHqVwO3uQtrYP1Gi
71A+yk4x2hZepwW5fHiTbeCU/kDycqWPsXOI3e+eBIDBHmaaD7uOkIWT/GnSBTvYr4NkF2xVxnmCsQ5eks13QdY6
MX1/gjwLl3nOPl6HBLc+KiHPLlMB rsa-key-20260325
</PRE>

You can use your mouse to highlight the entire string (starting at ssh-rsa and ending with the date) and copy it into your copy and paste buffer (this is actually a single line altogether). But first we want to do the following:

* create a terminal connection to one of the login nodes (putty, or even ThinLinc)
* navigate to the folder "~/.ssh"
* edit or create a file called "authorized_keys"
* paste the key from puttygen into this file (it should be a single line of text)
* save the file

==Using the private key to log in==

The procedure is different for the various pieces of software that can be used to connect to the cluster.

==Configuring PuTTY Connections==

When creating or editing a PuTTY connection, connect your private key as shown here:

[[File:Putty.png]]

Once you save your connection, the key is stored for all future connections to this machine.

==Configuring WinSCP==

When creating or editing a WinSCP connection, connect your private key as shown here. Start with the WinSCP page where you choose your connection, then click on "Advanced", and configure the connection as shown:

[[File:Winscp.png]]

Once you save your connection, the key is stored for all future connections to this machine.

==Configuring FileZilla==

When creating or editing a FileZilla connection (see Edit/Settings), connect your private key as shown here:

[[File:Filezilla.png]]

Once you save your connection, the key is stored for all future connections to this machine.

Private/Public Key Authentication

2026-03-25T21:09:29Z

Ley: /* Configuring FileZilla */

==Creating a Private/Public Key Pair==

If you have never use public key authentication before, you will have to start by creating a key pair. Once the key pair is created, you need to keep the private key in a safe location. Never upload the private key, and never send it by Email. Whoever has your private key can use it to try logging in to ARROW. So, treat the private key as a secret at all times.

The easiest way to prepare a key pair is the use of "puttygen", part of the "putty" software on Windows. Pressing the Windows Key together with R will open a window where you enter "puttygen". Once you press "Ok", the software opens up:

[[File:Puttygen1.png]]

We can go with the defaults and just click on the "Generate" button. Some randomness depends on you moving the mouse around on the screen. Once enough random data is gathered, the private and public key will be generated.

[[File:Puttygen2.png]]

Once the keys have been generated, you need to store the private key in a easy to find location on your local file system. I recommend creating a folder "Keys" within your "Documents" folder, but any other location is fine as well. The idea is that you may easily forget where the key is stored when you need it a later point in time.

[[File:Puttygen3.png]]

Click on "Save private key", which will create the following dialog box for you:

[[File:Puttygen4.png]]

In an ideal world, assigning a password for your private key would be best, but that also means that you may have to enter that password every time you use the key, which can be a problem. Not assigning a password is one more reason to never risk losing this private key file.

Navigate to the "Keys" folder in the "Documents: folder, and give the key a meaningful name. Something that tells you what it is used for, like "arrow-private". The extension ppk is automatically added when the key is saved.

Regarding the public key: It is not necessary to save the public key. When loading a private key, the public key is automatically displayed again at the top of the "puttygen" window. It looks somewhat like this:

==Uploading the public key to one of the ARROW login nodes==

The "puttygen" window still shows the public key at the top.

<PRE>
ssh-rsa AAAAB3NzaC1yc2EAfAADAQABAAABAQDOHgbwUYAAo+BMpvskvLw6eTqqs8OVUMSbAIobbC2/518PpJ/b
jW0n9NM4jlNJlEpuT79ZSv5RwSW8rP82qtcLdSEisxhXkyRLLjbzRWQSGxlVUI+K6MfZeFRYD+nqEH4Q1nSvxWJM
FigswLuWsygcJnGxv0FBGBP7pUrK5pz6AEv5Blf0MCuy0bvuIGhOYEMO4JeId6WYrAwJmZ3mjHqVwO3uQtrYP1Gi
71A+yk4x2hZepwW5fHiTbeCU/kDycqWPsXOI3e+eBIDBHmaaD7uOkIWT/GnSBTvYr4NkF2xVxnmCsQ5eks13QdY6
MX1/gjwLl3nOPl6HBLc+KiHPLlMB rsa-key-20260325
</PRE>

You can use your mouse to highlight the entire string (starting at ssh-rsa and ending with the date) and copy it into your copy and paste buffer (this is actually a single line altogether). But first we want to do the following:

* create a terminal connection to one of the login nodes (putty, or even ThinLinc)
* navigate to the folder "~/.ssh"
* edit or create a file called "authorized_keys"
* paste the key from puttygen into this file (it should be a single line of text)
* save the file

==Using the private key to log in==

The procedure is different for the various pieces of software that can be used to connect to the cluster.

==Configuring PuTTY Connections==

When creating or editing a PuTTY connection, connect your private key as shown here:

[[File:Putty.png]]

Once you save your connection, the key is stored for all future connections to this machine.

==Configuring WinSCP==

When creating or editing a WinSCP connection, connect your private key as shown here:

[[File:Winscp.png]]

Once you save your connection, the key is stored for all future connections to this machine.

==Configuring FileZilla==

When creating or editing a FileZilla connection (see Edit/Settings), connect your private key as shown here:

[[File:Filezilla.png]]

Once you save your connection, the key is stored for all future connections to this machine.

File:Filezilla.png

2026-03-25T21:08:27Z

Ley:

Private/Public Key Authentication

2026-03-25T21:06:58Z

Ley: /* Configuring WinSCP */

==Creating a Private/Public Key Pair==

If you have never use public key authentication before, you will have to start by creating a key pair. Once the key pair is created, you need to keep the private key in a safe location. Never upload the private key, and never send it by Email. Whoever has your private key can use it to try logging in to ARROW. So, treat the private key as a secret at all times.

The easiest way to prepare a key pair is the use of "puttygen", part of the "putty" software on Windows. Pressing the Windows Key together with R will open a window where you enter "puttygen". Once you press "Ok", the software opens up:

[[File:Puttygen1.png]]

We can go with the defaults and just click on the "Generate" button. Some randomness depends on you moving the mouse around on the screen. Once enough random data is gathered, the private and public key will be generated.

[[File:Puttygen2.png]]

Once the keys have been generated, you need to store the private key in a easy to find location on your local file system. I recommend creating a folder "Keys" within your "Documents" folder, but any other location is fine as well. The idea is that you may easily forget where the key is stored when you need it a later point in time.

[[File:Puttygen3.png]]

Click on "Save private key", which will create the following dialog box for you:

[[File:Puttygen4.png]]

In an ideal world, assigning a password for your private key would be best, but that also means that you may have to enter that password every time you use the key, which can be a problem. Not assigning a password is one more reason to never risk losing this private key file.

Navigate to the "Keys" folder in the "Documents: folder, and give the key a meaningful name. Something that tells you what it is used for, like "arrow-private". The extension ppk is automatically added when the key is saved.

Regarding the public key: It is not necessary to save the public key. When loading a private key, the public key is automatically displayed again at the top of the "puttygen" window. It looks somewhat like this:

==Uploading the public key to one of the ARROW login nodes==

The "puttygen" window still shows the public key at the top.

<PRE>
ssh-rsa AAAAB3NzaC1yc2EAfAADAQABAAABAQDOHgbwUYAAo+BMpvskvLw6eTqqs8OVUMSbAIobbC2/518PpJ/b
jW0n9NM4jlNJlEpuT79ZSv5RwSW8rP82qtcLdSEisxhXkyRLLjbzRWQSGxlVUI+K6MfZeFRYD+nqEH4Q1nSvxWJM
FigswLuWsygcJnGxv0FBGBP7pUrK5pz6AEv5Blf0MCuy0bvuIGhOYEMO4JeId6WYrAwJmZ3mjHqVwO3uQtrYP1Gi
71A+yk4x2hZepwW5fHiTbeCU/kDycqWPsXOI3e+eBIDBHmaaD7uOkIWT/GnSBTvYr4NkF2xVxnmCsQ5eks13QdY6
MX1/gjwLl3nOPl6HBLc+KiHPLlMB rsa-key-20260325
</PRE>

You can use your mouse to highlight the entire string (starting at ssh-rsa and ending with the date) and copy it into your copy and paste buffer (this is actually a single line altogether). But first we want to do the following:

* create a terminal connection to one of the login nodes (putty, or even ThinLinc)
* navigate to the folder "~/.ssh"
* edit or create a file called "authorized_keys"
* paste the key from puttygen into this file (it should be a single line of text)
* save the file

==Using the private key to log in==

The procedure is different for the various pieces of software that can be used to connect to the cluster.

==Configuring PuTTY Connections==

When creating or editing a PuTTY connection, connect your private key as shown here:

[[File:Putty.png]]

Once you save your connection, the key is stored for all future connections to this machine.

==Configuring WinSCP==

When creating or editing a WinSCP connection, connect your private key as shown here:

[[File:Winscp.png]]

Once you save your connection, the key is stored for all future connections to this machine.

==Configuring FileZilla==

When creating or editing a FileZilla connection, connect your private key as shown here:

[[File:Filezilla.png]]

Once you save your connection, the key is stored for all future connections to this machine.

Private/Public Key Authentication

2026-03-25T21:06:07Z

Ley: /* Configuring PuTTY Connections */

==Creating a Private/Public Key Pair==

If you have never use public key authentication before, you will have to start by creating a key pair. Once the key pair is created, you need to keep the private key in a safe location. Never upload the private key, and never send it by Email. Whoever has your private key can use it to try logging in to ARROW. So, treat the private key as a secret at all times.

The easiest way to prepare a key pair is the use of "puttygen", part of the "putty" software on Windows. Pressing the Windows Key together with R will open a window where you enter "puttygen". Once you press "Ok", the software opens up:

[[File:Puttygen1.png]]

We can go with the defaults and just click on the "Generate" button. Some randomness depends on you moving the mouse around on the screen. Once enough random data is gathered, the private and public key will be generated.

[[File:Puttygen2.png]]

Once the keys have been generated, you need to store the private key in a easy to find location on your local file system. I recommend creating a folder "Keys" within your "Documents" folder, but any other location is fine as well. The idea is that you may easily forget where the key is stored when you need it a later point in time.

[[File:Puttygen3.png]]

Click on "Save private key", which will create the following dialog box for you:

[[File:Puttygen4.png]]

In an ideal world, assigning a password for your private key would be best, but that also means that you may have to enter that password every time you use the key, which can be a problem. Not assigning a password is one more reason to never risk losing this private key file.

Navigate to the "Keys" folder in the "Documents: folder, and give the key a meaningful name. Something that tells you what it is used for, like "arrow-private". The extension ppk is automatically added when the key is saved.

Regarding the public key: It is not necessary to save the public key. When loading a private key, the public key is automatically displayed again at the top of the "puttygen" window. It looks somewhat like this:

==Uploading the public key to one of the ARROW login nodes==

The "puttygen" window still shows the public key at the top.

<PRE>
ssh-rsa AAAAB3NzaC1yc2EAfAADAQABAAABAQDOHgbwUYAAo+BMpvskvLw6eTqqs8OVUMSbAIobbC2/518PpJ/b
jW0n9NM4jlNJlEpuT79ZSv5RwSW8rP82qtcLdSEisxhXkyRLLjbzRWQSGxlVUI+K6MfZeFRYD+nqEH4Q1nSvxWJM
FigswLuWsygcJnGxv0FBGBP7pUrK5pz6AEv5Blf0MCuy0bvuIGhOYEMO4JeId6WYrAwJmZ3mjHqVwO3uQtrYP1Gi
71A+yk4x2hZepwW5fHiTbeCU/kDycqWPsXOI3e+eBIDBHmaaD7uOkIWT/GnSBTvYr4NkF2xVxnmCsQ5eks13QdY6
MX1/gjwLl3nOPl6HBLc+KiHPLlMB rsa-key-20260325
</PRE>

You can use your mouse to highlight the entire string (starting at ssh-rsa and ending with the date) and copy it into your copy and paste buffer (this is actually a single line altogether). But first we want to do the following:

* create a terminal connection to one of the login nodes (putty, or even ThinLinc)
* navigate to the folder "~/.ssh"
* edit or create a file called "authorized_keys"
* paste the key from puttygen into this file (it should be a single line of text)
* save the file

==Using the private key to log in==

The procedure is different for the various pieces of software that can be used to connect to the cluster.

==Configuring PuTTY Connections==

When creating or editing a PuTTY connection, connect your private key as shown here:

[[File:Putty.png]]

Once you save your connection, the key is stored for all future connections to this machine.

==Configuring WinSCP==

When creating or editing a WinSCP connection, connect your private key as shown here:

[[File:Winscp.png]]

Once you save your connection, the key is stored for all future connections to this machine.

Private/Public Key Authentication

2026-03-25T21:05:54Z

Ley: /* Configuring WinSCP */

==Creating a Private/Public Key Pair==

If you have never use public key authentication before, you will have to start by creating a key pair. Once the key pair is created, you need to keep the private key in a safe location. Never upload the private key, and never send it by Email. Whoever has your private key can use it to try logging in to ARROW. So, treat the private key as a secret at all times.

The easiest way to prepare a key pair is the use of "puttygen", part of the "putty" software on Windows. Pressing the Windows Key together with R will open a window where you enter "puttygen". Once you press "Ok", the software opens up:

[[File:Puttygen1.png]]

We can go with the defaults and just click on the "Generate" button. Some randomness depends on you moving the mouse around on the screen. Once enough random data is gathered, the private and public key will be generated.

[[File:Puttygen2.png]]

Once the keys have been generated, you need to store the private key in a easy to find location on your local file system. I recommend creating a folder "Keys" within your "Documents" folder, but any other location is fine as well. The idea is that you may easily forget where the key is stored when you need it a later point in time.

[[File:Puttygen3.png]]

Click on "Save private key", which will create the following dialog box for you:

[[File:Puttygen4.png]]

In an ideal world, assigning a password for your private key would be best, but that also means that you may have to enter that password every time you use the key, which can be a problem. Not assigning a password is one more reason to never risk losing this private key file.

Navigate to the "Keys" folder in the "Documents: folder, and give the key a meaningful name. Something that tells you what it is used for, like "arrow-private". The extension ppk is automatically added when the key is saved.

Regarding the public key: It is not necessary to save the public key. When loading a private key, the public key is automatically displayed again at the top of the "puttygen" window. It looks somewhat like this:

==Uploading the public key to one of the ARROW login nodes==

The "puttygen" window still shows the public key at the top.

<PRE>
ssh-rsa AAAAB3NzaC1yc2EAfAADAQABAAABAQDOHgbwUYAAo+BMpvskvLw6eTqqs8OVUMSbAIobbC2/518PpJ/b
jW0n9NM4jlNJlEpuT79ZSv5RwSW8rP82qtcLdSEisxhXkyRLLjbzRWQSGxlVUI+K6MfZeFRYD+nqEH4Q1nSvxWJM
FigswLuWsygcJnGxv0FBGBP7pUrK5pz6AEv5Blf0MCuy0bvuIGhOYEMO4JeId6WYrAwJmZ3mjHqVwO3uQtrYP1Gi
71A+yk4x2hZepwW5fHiTbeCU/kDycqWPsXOI3e+eBIDBHmaaD7uOkIWT/GnSBTvYr4NkF2xVxnmCsQ5eks13QdY6
MX1/gjwLl3nOPl6HBLc+KiHPLlMB rsa-key-20260325
</PRE>

You can use your mouse to highlight the entire string (starting at ssh-rsa and ending with the date) and copy it into your copy and paste buffer (this is actually a single line altogether). But first we want to do the following:

* create a terminal connection to one of the login nodes (putty, or even ThinLinc)
* navigate to the folder "~/.ssh"
* edit or create a file called "authorized_keys"
* paste the key from puttygen into this file (it should be a single line of text)
* save the file

==Using the private key to log in==

The procedure is different for the various pieces of software that can be used to connect to the cluster.

==Configuring PuTTY Connections==

When creating or editing a PuTTY, connect your private key as shown here:

[[File:Putty.png]]

Once you save your connection, the key is stored for all future connections to this machine.

==Configuring WinSCP==

When creating or editing a WinSCP connection, connect your private key as shown here:

[[File:Winscp.png]]

Once you save your connection, the key is stored for all future connections to this machine.

File:Winscp.png

2026-03-25T21:04:27Z

Ley:

Private/Public Key Authentication

2026-03-25T21:03:54Z

Ley: /* Configuring WinSCP */

==Creating a Private/Public Key Pair==

If you have never use public key authentication before, you will have to start by creating a key pair. Once the key pair is created, you need to keep the private key in a safe location. Never upload the private key, and never send it by Email. Whoever has your private key can use it to try logging in to ARROW. So, treat the private key as a secret at all times.

The easiest way to prepare a key pair is the use of "puttygen", part of the "putty" software on Windows. Pressing the Windows Key together with R will open a window where you enter "puttygen". Once you press "Ok", the software opens up:

[[File:Puttygen1.png]]

We can go with the defaults and just click on the "Generate" button. Some randomness depends on you moving the mouse around on the screen. Once enough random data is gathered, the private and public key will be generated.

[[File:Puttygen2.png]]

Once the keys have been generated, you need to store the private key in a easy to find location on your local file system. I recommend creating a folder "Keys" within your "Documents" folder, but any other location is fine as well. The idea is that you may easily forget where the key is stored when you need it a later point in time.

[[File:Puttygen3.png]]

Click on "Save private key", which will create the following dialog box for you:

[[File:Puttygen4.png]]

In an ideal world, assigning a password for your private key would be best, but that also means that you may have to enter that password every time you use the key, which can be a problem. Not assigning a password is one more reason to never risk losing this private key file.

Navigate to the "Keys" folder in the "Documents: folder, and give the key a meaningful name. Something that tells you what it is used for, like "arrow-private". The extension ppk is automatically added when the key is saved.

Regarding the public key: It is not necessary to save the public key. When loading a private key, the public key is automatically displayed again at the top of the "puttygen" window. It looks somewhat like this:

==Uploading the public key to one of the ARROW login nodes==

The "puttygen" window still shows the public key at the top.

<PRE>
ssh-rsa AAAAB3NzaC1yc2EAfAADAQABAAABAQDOHgbwUYAAo+BMpvskvLw6eTqqs8OVUMSbAIobbC2/518PpJ/b
jW0n9NM4jlNJlEpuT79ZSv5RwSW8rP82qtcLdSEisxhXkyRLLjbzRWQSGxlVUI+K6MfZeFRYD+nqEH4Q1nSvxWJM
FigswLuWsygcJnGxv0FBGBP7pUrK5pz6AEv5Blf0MCuy0bvuIGhOYEMO4JeId6WYrAwJmZ3mjHqVwO3uQtrYP1Gi
71A+yk4x2hZepwW5fHiTbeCU/kDycqWPsXOI3e+eBIDBHmaaD7uOkIWT/GnSBTvYr4NkF2xVxnmCsQ5eks13QdY6
MX1/gjwLl3nOPl6HBLc+KiHPLlMB rsa-key-20260325
</PRE>

You can use your mouse to highlight the entire string (starting at ssh-rsa and ending with the date) and copy it into your copy and paste buffer (this is actually a single line altogether). But first we want to do the following:

* create a terminal connection to one of the login nodes (putty, or even ThinLinc)
* navigate to the folder "~/.ssh"
* edit or create a file called "authorized_keys"
* paste the key from puttygen into this file (it should be a single line of text)
* save the file

==Using the private key to log in==

The procedure is different for the various pieces of software that can be used to connect to the cluster.

==Configuring PuTTY Connections==

When creating or editing a PuTTY, connect your private key as shown here:

[[File:Putty.png]]

Once you save your connection, the key is stored for all future connections to this machine.

==Configuring WinSCP==

When creating or editing a PuTTY, connect your private key as shown here:

[[File:Winscp.png]]

Once you save your connection, the key is stored for all future connections to this machine.

Private/Public Key Authentication

2026-03-25T21:03:26Z

Ley: /* Configuring PuTTY Connections */

==Creating a Private/Public Key Pair==

If you have never use public key authentication before, you will have to start by creating a key pair. Once the key pair is created, you need to keep the private key in a safe location. Never upload the private key, and never send it by Email. Whoever has your private key can use it to try logging in to ARROW. So, treat the private key as a secret at all times.

The easiest way to prepare a key pair is the use of "puttygen", part of the "putty" software on Windows. Pressing the Windows Key together with R will open a window where you enter "puttygen". Once you press "Ok", the software opens up:

[[File:Puttygen1.png]]

We can go with the defaults and just click on the "Generate" button. Some randomness depends on you moving the mouse around on the screen. Once enough random data is gathered, the private and public key will be generated.

[[File:Puttygen2.png]]

Once the keys have been generated, you need to store the private key in a easy to find location on your local file system. I recommend creating a folder "Keys" within your "Documents" folder, but any other location is fine as well. The idea is that you may easily forget where the key is stored when you need it a later point in time.

[[File:Puttygen3.png]]

Click on "Save private key", which will create the following dialog box for you:

[[File:Puttygen4.png]]

In an ideal world, assigning a password for your private key would be best, but that also means that you may have to enter that password every time you use the key, which can be a problem. Not assigning a password is one more reason to never risk losing this private key file.

Navigate to the "Keys" folder in the "Documents: folder, and give the key a meaningful name. Something that tells you what it is used for, like "arrow-private". The extension ppk is automatically added when the key is saved.

Regarding the public key: It is not necessary to save the public key. When loading a private key, the public key is automatically displayed again at the top of the "puttygen" window. It looks somewhat like this:

==Uploading the public key to one of the ARROW login nodes==

The "puttygen" window still shows the public key at the top.

<PRE>
ssh-rsa AAAAB3NzaC1yc2EAfAADAQABAAABAQDOHgbwUYAAo+BMpvskvLw6eTqqs8OVUMSbAIobbC2/518PpJ/b
jW0n9NM4jlNJlEpuT79ZSv5RwSW8rP82qtcLdSEisxhXkyRLLjbzRWQSGxlVUI+K6MfZeFRYD+nqEH4Q1nSvxWJM
FigswLuWsygcJnGxv0FBGBP7pUrK5pz6AEv5Blf0MCuy0bvuIGhOYEMO4JeId6WYrAwJmZ3mjHqVwO3uQtrYP1Gi
71A+yk4x2hZepwW5fHiTbeCU/kDycqWPsXOI3e+eBIDBHmaaD7uOkIWT/GnSBTvYr4NkF2xVxnmCsQ5eks13QdY6
MX1/gjwLl3nOPl6HBLc+KiHPLlMB rsa-key-20260325
</PRE>

You can use your mouse to highlight the entire string (starting at ssh-rsa and ending with the date) and copy it into your copy and paste buffer (this is actually a single line altogether). But first we want to do the following:

* create a terminal connection to one of the login nodes (putty, or even ThinLinc)
* navigate to the folder "~/.ssh"
* edit or create a file called "authorized_keys"
* paste the key from puttygen into this file (it should be a single line of text)
* save the file

==Using the private key to log in==

The procedure is different for the various pieces of software that can be used to connect to the cluster.

==Configuring PuTTY Connections==

When creating or editing a PuTTY, connect your private key as shown here:

[[File:Putty.png]]

Once you save your connection, the key is stored for all future connections to this machine.

==Configuring WinSCP==

Private/Public Key Authentication

2026-03-25T21:01:32Z

Ley: /* putty */

==Creating a Private/Public Key Pair==

If you have never use public key authentication before, you will have to start by creating a key pair. Once the key pair is created, you need to keep the private key in a safe location. Never upload the private key, and never send it by Email. Whoever has your private key can use it to try logging in to ARROW. So, treat the private key as a secret at all times.

The easiest way to prepare a key pair is the use of "puttygen", part of the "putty" software on Windows. Pressing the Windows Key together with R will open a window where you enter "puttygen". Once you press "Ok", the software opens up:

[[File:Puttygen1.png]]

We can go with the defaults and just click on the "Generate" button. Some randomness depends on you moving the mouse around on the screen. Once enough random data is gathered, the private and public key will be generated.

[[File:Puttygen2.png]]

Once the keys have been generated, you need to store the private key in a easy to find location on your local file system. I recommend creating a folder "Keys" within your "Documents" folder, but any other location is fine as well. The idea is that you may easily forget where the key is stored when you need it a later point in time.

[[File:Puttygen3.png]]

Click on "Save private key", which will create the following dialog box for you:

[[File:Puttygen4.png]]

In an ideal world, assigning a password for your private key would be best, but that also means that you may have to enter that password every time you use the key, which can be a problem. Not assigning a password is one more reason to never risk losing this private key file.

Navigate to the "Keys" folder in the "Documents: folder, and give the key a meaningful name. Something that tells you what it is used for, like "arrow-private". The extension ppk is automatically added when the key is saved.

Regarding the public key: It is not necessary to save the public key. When loading a private key, the public key is automatically displayed again at the top of the "puttygen" window. It looks somewhat like this:

==Uploading the public key to one of the ARROW login nodes==

The "puttygen" window still shows the public key at the top.

<PRE>
ssh-rsa AAAAB3NzaC1yc2EAfAADAQABAAABAQDOHgbwUYAAo+BMpvskvLw6eTqqs8OVUMSbAIobbC2/518PpJ/b
jW0n9NM4jlNJlEpuT79ZSv5RwSW8rP82qtcLdSEisxhXkyRLLjbzRWQSGxlVUI+K6MfZeFRYD+nqEH4Q1nSvxWJM
FigswLuWsygcJnGxv0FBGBP7pUrK5pz6AEv5Blf0MCuy0bvuIGhOYEMO4JeId6WYrAwJmZ3mjHqVwO3uQtrYP1Gi
71A+yk4x2hZepwW5fHiTbeCU/kDycqWPsXOI3e+eBIDBHmaaD7uOkIWT/GnSBTvYr4NkF2xVxnmCsQ5eks13QdY6
MX1/gjwLl3nOPl6HBLc+KiHPLlMB rsa-key-20260325
</PRE>

You can use your mouse to highlight the entire string (starting at ssh-rsa and ending with the date) and copy it into your copy and paste buffer (this is actually a single line altogether). But first we want to do the following:

* create a terminal connection to one of the login nodes (putty, or even ThinLinc)
* navigate to the folder "~/.ssh"
* edit or create a file called "authorized_keys"
* paste the key from puttygen into this file (it should be a single line of text)
* save the file

==Using the private key to log in==

The procedure is different for the various pieces of software that can be used to connect to the cluster.

==Configuring PuTTY Connections==

When creating or editing a PuTTY, connect your private key as shown here:

[[File:Putty.png]]

Once you save your connection, the key is stored for all future connections to this machine.

Private/Public Key Authentication

2026-03-25T20:06:10Z

Ley: /* putty */

File:Putty.png

2026-03-25T20:04:28Z

Ley:

Private/Public Key Authentication

2026-03-25T20:03:13Z

Ley:

Private/Public Key Authentication

Private/Public Key Authentication

2026-03-25T19:22:22Z

Ley: Created page with "==Creating a Private/Public Key Pair=="

==Creating a Private/Public Key Pair==

How to Connect

2026-03-25T19:21:23Z

Ley:

You need an SSH client to connect to Arrow. No other connection protocols are supported. There are 3 general purpose login nodes that you can connect to:

*login1.arrow.tracc.anl.gov
*login2.arrow.tracc.anl.gov
*login3.arrow.tracc.anl.gov

There is also a web-based ThinLinc GUI server available at:

*webaccess4.arrow.tracc.anl.gov

which can be accessed using Chrome, FireFox, or Edge. To use this interface, please contact us for instructions.

When connecting, please pick a random entry from the above list to evenly distribute users over multiple machines. Each login node is a unique server, so if you established an interactive GUI session at some point in the past, you can reconnect to the same login node where you started that GUI session, and you will be able to continue where you left off. This is similar to a remote desktop connection in Windows, and is convenient when connecting from an unreliable network or if you simply prefer to be have a more permanent desktop available. Please not that the login servers have to restarted from time to time, so there is guarantee that a session stays around for weeks or months at a time.

For most remote collaborators, your account starts with "ac.". An example would be "ac.username". These accounts give you access to the ARROW cluster, but to no other resources at Argonne, without exception. If you are an Argonne employee or have an Argonne domain account for other reasons, you will use that account to log in. In this case, don't use the "ANL\" domain prefix as you would on some Windows machines. Just enter the "username" portion.

After entering the password, you will need to confirm your identity using the DUO application. Upon enrollment for a cluster account, you will receive an auto-enrollment Email. Follow the instructions, install the DUO app on your phone, and you are ready to login. As soon as you enter your password in the ssh connection, your phone will prompt you to confirm that you are attempting to log in. After confirming your identity, you will be connected.

Passwords expire on a regular basis (every 6 months or so), and you will need to update your password with Argonne Account Services. You can call 630-252-9999 if you need any help or detailed instructions.

* Access to the TRACC cluster requires the use of an SSH client. Free SSH clients are available for Windows, are included or available for MacOS, and all varieties of Linux or UNIX. SSH clients can be terminal applications to work with command lines (e.g. Putty on Windows), or they can be file transfer utilities (WinSCP, FileZilla, MobaXterm). In any case, cluster connections are all using the SSH protocol (including sftp). Typically you would use a variation of the following command, or provide account and password in your SSH application, such as PuTTy.

ssh username@login1.arrow.tracc.anl.gov

* If you are planning to use a single GUI application on the cluster through a plain SSH connection and you are either connecting from a Mac or Linux desktop machine or you have an X server installed on your Windows machine, you may want to enable X11 forwarding to your client using the "-X" option on the command line. Performance is limited, but the mechanism works with limited bandwidth and resources:

ssh -X username@login1.arrow.tracc.anl.gov

In some cases, it is necessary to add the "-Y" option, or to replace the "-X" option with "-Y" altogether. It depends on the graphical application you are planning to use.

ssh -X -Y username@login1.arrow.tracc.anl.gov

* Alternatively, client software like ThinLinc or X2Go can be used to connect, providing a full graphical user interface and an XFCE desktop. We can provide information on how to download and possibly install the software on your system. We are no longer providing the NoMachine remote desktop software on ARROW.

* [[Private/Public Key Authentication]]

2025-12-09T06:00:39Z

Ley: /* LS-Dyna+ */

Main Page

2025-12-09T05:57:03Z

Ley: /* LS-Dyna+ */

Main Page

2025-12-09T05:54:40Z

Ley: /* LS-Dyna+ */

Main Page

2025-12-09T05:52:52Z

Ley: /* LS-Dyna+ */

Main Page

2025-12-09T05:49:56Z

Ley: /* StarCCM+ */