UMIACS - User contributions [en]

SSH/Keys

2020-10-30T18:08:08Z

Meganst:

SSH can utilize public key encryption to authenticate and authorize users. This can be considered more secure especially if you secure your private key with a pass-phrase. The keys themselves are not susceptible to brute force attacks like normal passwords over SSH are.

==Overview==
;Prerequisites
#If using batch clusters (e.g. [[SLURM]]) please read [[SSH/Keys#Batch clusters | Batch clusters]] prior to creating a new key.
#Determine your OS (and if Windows, what you will be using to create the key)
#*Windows
#**Git Bash: follow instructions for Linux/MacOSX/Bash and Git Bash (for Windows)
#**PuTTY: follow instructions for Windows (and PuTTY subsections)
#**TTSSH2: follow instructions for Windows (and TTSSH2 subsections)
#**[[BashForWindows10 | Windows Subsystem for Linux (WSL)]]: follow instructions for 'Linux/MacOSX/Bash and Git Bash (for Windows)'
#*Linux: follow instructions for 'Linux/MacOSX/Bash and Git Bash (for Windows)'
#*MacOSX: follow instructions for 'Linux/MacOSX/Bash and Git Bash (for Windows)'
;Steps
#[[SSH/Keys#Create and store the key pair | Create and store the key pair]]
#[[SSH/Keys#Copy the public key | Copy the public key]]
#If Windows, [[SSH/Keys#Adding Keys to SSH Clients (Windows Only) | Adding Keys to SSH Clients (Windows Only)]]
;Additional Considerations
#The [[SSH/Keys#SSH Agents | SSH Agents]] section is not a required component of creating and using an SSH key, but can be very useful if you choose to create a password to protect your SSH key, but find yourself needing to enter that password many times in a session. [[SSH/Keys#SSH Agents | SSH Agents]] allow you to temporarily use your SSH key without a password for a set period of time. Please see the [[SSH/Keys#SSH Agents | SSH Agents]] section for more information.

==Create and store the key pair==

The first step is to generate a key which will create two files filled with long strings of characters. A public key file that you may distribute to any machine you want to use it on and a private key that needs to be kept secure. '''Allowing anyone to read this private key will compromise the security of the key and could allow someone to access any resources secured by this key without your consent.''' There are a number of different key types but <code>rsa</code> is the most compatible.

===Windows===
;Git Bash
:See [[SSH/Keys#Linux.2FMacOSX.2FBash_and_Git_Bash_.28for_Windows.29 | Linux/MacOSX/Bash and Git Bash (for Windows)]]
;PuTTY
# Click on the start menu and search for PuTTYgen. Open the application
# Verify that you are attempting to create an "SSH2 RSA" key by clicking on the appropriate box
# Click generate and follow the instructions for generating your keys
# Add passphrase if wanted and save both the public and private keys
;TTSSH2
# Open the application
# Cancel the first box
# Go to setup on the menu bar and go to SSH KeyGenerator
# Click generate and follow the instructions for generating your key
# Add passphrase if wanted and save both the public and private keys

===Linux/MacOSX/Bash and Git Bash (for Windows)===
;Create a new key with a password
You can run the command <code>ssh-keygen -t rsa</code> to generate the new public and private key. It will prompt you for a file to create the private key and then for the public key append <code>.pub</code> extension and store it in the same directory. Pressing enter at the passphrase step twice will create a key without a pass-phrase.

Note: If you change the file in which to save the key, please ensure that it still starts with 'id', such as 'id_umiacs_rsa'.

Example: <pre>
-bash-4.2$ ssh-keygen -t rsa
Generating public/private rsa key pair.
Enter file in which to save the key (/home/derek/.ssh/id_rsa):
Created directory '/home/derek/.ssh'.
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /home/derek/.ssh/id_rsa.
Your public key has been saved in /home/derek/.ssh/id_rsa.pub.
The key fingerprint is:
32:bf:db:74:1b:7e:d7:c6:4b:b5:6f:a8:82:55:3f:bf derek@localhost.localdomain
The key's randomart image is:
+--[ RSA 2048]----+
| |
| |
| |
| . |
| o S . . .|
| + . o o|
| .o. o B.|
| .+.o o+ O|
| o...+o E+|
+-----------------+
</pre>

;Create a new key without a password
You can simplify the existing example above by telling it you do not want a pass-phrase and can run the command <code>ssh-keygen -t rsa -N ""</code>.

Note: If you change the file in which to save the key, please ensure that it still starts with 'id', such as 'id_umiacs_rsa'.

Example: <pre>
-bash-4.2$ ssh-keygen -t rsa -N ""
Generating public/private rsa key pair.
Enter file in which to save the key (/home/derek/.ssh/id_rsa):
Created directory '/home/derek/.ssh'.
Your identification has been saved in /home/derek/.ssh/id_rsa.
Your public key has been saved in /home/derek/.ssh/id_rsa.pub.
The key fingerprint is:
ff:7a:99:28:fc:63:d6:10:44:4c:2e:68:76:44:76:7a derek@localhost.localdomain
The key's randomart image is:
+--[ RSA 2048]----+
| .+++ |
| + +o |
| + +.E |
| o . o. |
| S . |
| .. |
| . .+ o |
| o =.= |
| =o+. |
+-----------------+
</pre>

;Modify permissions
Modify the permissions of your <tt>.ssh</tt> directory as well as the private key file that you just created with <tt>chmod</tt>.

<pre>
chmod 700 ~/.ssh
chmod 600 ~/.ssh/id_rsa
</pre>

If you named your file something other than id_rsa, change <tt>id_rsa</tt> to the name of the file.

==Copy the public key==
Once you have a generated a key pair you will want to add it to one or more computers to allow you to access them.

===Windows===
For Windows hosts you can use [http://winscp.net/eng/download.php WinSCP] to copy the public key file onto a remote host. The root file system for the Bash Subsystem for Windows is located under C:\Users\username>\AppData\Local\lxss\

===Linux/MacOSX/Bash and Git Bash (for Windows)===
This can be done with the <code>ssh-copy-id</code> command and it will prompt you the first time for your current password ('''NOT your pass-phrase'''). You can replace localhost with any other hostname you want to copy the key to. You can also specify a alternate user or identity file if you need to, please <code>man ssh-copy-id</code> for more information within your terminal. This command will ensure that not only it copies your key but secures the file so that no one can tamper and add additional authorized keys to the file on the remote host.

Example: <pre>
-bash-4.2$ ssh-copy-id localhost
/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed
/bin/ssh-copy-id: INFO: 1 key(s) remain to be installed -- if you are prompted now it is to install the new keys
derek@localhost's password:

Number of key(s) added: 1

Now try logging into the machine, with: "ssh 'localhost'"
and check to make sure that only the key(s) you wanted were added.
</pre>

==Adding Keys to SSH Clients (Windows Only)==
;PuTTY
# Open PuTTY and enter the Fully Qualified Domain Name for the host you wish to connect to.
# Go to the Connections tab on the side panel and click on the data subsection.
# Under data enter your default user into the first box. (Auto-login Username)
# Go to the SSH section of the side panel and then go to the Auth Section.
# Under Auth click on the browse and navigate to the saved private key.
# Go back to session on the side panel and save your settings by typing in a name in saved sessions pressing the save button.
;TTSSH2
# Open the application.
# Cancel the first box.
# Go to setup on the menu bar and go to SSH Authentication.
# Enter your username, Click on the option labeled "Use RSA ... key to log in", then use the private key button located next to this line to navigate to your private key file, and click Ok.

==Batch clusters==
Our [[SLURM]] clusters process jobs in batch and require the ability to SSH without entering a password. When creating a key for use with [[SLURM]], follow the above instructions for creating keys without passwords.

After creating this key pair please make sure you follow the [[SSH/Keys#Copy_the_public_key | copy the public key]] instructions above to <code>localhost</code>. This will ensure that your key will be usable on all the cluster nodes since they have a shared home directory.

==SSH Agents==
While it is very useful to protect your SSH key pair with a pass-phrase it can very time consuming to re-type the pass-phrase over and over. SSH provides a agent that runs in the background and allow you add a key(s) to it with a time limit that they will be unlocked for.

<pre>
ssh-agent bash
ssh-add -t $TIME
</pre>

The time specified by <code>-t</code> is specified in seconds.

Example:
(The following would start a bash shell with passwordless SSH active for 30 minutes.)
<pre>
ssh-agent bash
ssh-add -t 1800
</pre>

You will be prompted for your passphrase and, when entered correctly, you will be able to SSH without entering a password. You can check what keys are load when you are running inside a ssh-agent by using the command <code>ssh-add -l</code>.

Example: <pre>
bash-4.2$ ssh-add -l
2048 ee:83:10:c8:2f:2c:17:5e:ef:80:42:7e:ff:75:9e:53 /home/derek/.ssh/id_rsa (RSA)
</pre>

SecureShell

2020-10-30T18:06:57Z

Meganst: Pointing SSH Keys section to SSH/Keys page

Secure Shell (or [http://en.wikipedia.org/wiki/Secure_Shell SSH]) is a network protocol allowing two computers to exchange data securely over an insecure network. By default, use of SSH brings the user to a terminal, but the protocol can be used for other types of data transfer such as [[SFTP]] and [[SCP]].

==Connecting to an SSH Server==
Under Linux and macOS the following command from a terminal will connect a client computer to the UMIACS [[OpenLAB]].
# ssh bkirz@openlab.umiacs.umd.edu
This will give you access to a terminal on any one of the [[OpenLAB]] servers. Note that by default you will not have access to applications that require X11 to run.

All UMIACS Windows hosts are installed with either the SSH Secure Shell Client or [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY].

==X11 Forwarding==
By default, SSH only gives the user shell access to a host. Enabling X11 Forwarding allows users to run applications with Graphical User Interfaces.

Under Linux and macOS, the following command from a terminal will connect a client computer to the UMIACS [[OpenLAB]] using X11 Forwarding. Please note that under macOS, [http://xquartz.macosforge.org/landing/ xQuartz] is required on the client machine to forward X sessions from the remote session.
# ssh '''-Y''' bkirz@openlab.umiacs.umd.edu

Under Windows, you will need to forward X through [http://sourceforge.net/projects/vcxsrv/ VcXsrv] or [http://www.straightrunning.com/XmingNotes/ Xming].

First, enable X forwarding on PuTTY. The option is under Connection > SSH > X11, shown below.

[[Image:Putty-x-forwarding.png]]

Next, configure your SSH session and click open to start a SSH session.

After this has been done, every time you want to use X forwarding, you need to make sure VcXsrv or Xming has been started (it will appear in your task tray) through the start menu programs.
Now, you will be able to use Xwindow programs from your ssh client.

==SSH Tunneling==

You can tunnel one or more ports through an SSH connection such that your packets will look like they are coming from the host you are tunneling to. This is helpful for services that you would be normally blocked by a firewall.

Please see the [[SecureShellTunneling]] page for more information.

==SSH Keys (and Passwordless SSH)==
SSH can utilize public key encryption to authenticate and authorize users. This can be considered more secure especially if you secure your private key with a pass-phrase. The keys themselves are not susceptible to brute force attacks like normal passwords over SSH are.

Please see the [[SSH/Keys]] page for more information.

==Verify remote host SSH fingerprint==
The SSH protocol relies on host keys to verify the identify of a given host. Each host as a unique key for the various different protocols supported.

When connecting to a remove host for the first time, or when the remote host's local host key configuration has changed, you may see the following prompt:
<pre>
$ ssh sabobbin@openlab
The authenticity of host 'openlab (128.8.132.247)' can't be established.
RSA key fingerprint is 25:83:aa:df:f5:ad:5f:08:c9:8a:a3:5d:97:8b:48:1f.
Are you sure you want to continue connecting (yes/no)?
</pre>
It is considered best practice to verify the key fingerprint with the actual key of the host. UMIACS maintains a reference of SSH key fingerprints available at the following link:
https://gitlab.umiacs.umd.edu/staff/ssh-fingerprints/blob/master/fingerprints

It is important to note that each key type has a different fingerprint. Depending on your local configuration, your client may prefer a specific type of key. The following commands can be used to determine the fingerprint of a given key type on a remote host:

<pre>
$ ssh-keyscan -t rsa openlab.umiacs.umd.edu > key
# openlab.umiacs.umd.edu:22 SSH-2.0-OpenSSH_8.0
$ ssh-keygen -l -E md5 -f key
2048 MD5:25:83:aa:df:f5:ad:5f:08:c9:8a:a3:5d:97:8b:48:1f openlab.umiacs.umd.edu (RSA)
</pre>

If you have any questions, or notice a discrepancy, please submit a request to staff@umiacs.umd.edu.

===Windows / PuTTY Verification===
If you use PuTTY to connect to remote hosts, the prompt will be similar to the following:

[[File:Putty ssh host key prompt.png]]

If the host key reported by PuTTY matches the [https://gitlab.umiacs.umd.edu/staff/ssh-fingerprints/blob/master/fingerprints Documented entry for that host], it is safe to click 'yes'. If they do not match, please report the issue to [mailto:staff@umiacs.umd.edu staff@umiacs.umd.edu].

===Other Platforms===
* [https://winscp.net/eng/docs/faq_hostkey WinSCP]

==Long Running Processes==
If you are dealing with a long running process that is inhibiting your ability to work regularly, you may want to run your processes inside a screen on the host that you're connecting to. This way, if the connection is dropped for any reason the screen session will automatically detach on the host and will continue running so that you can reattach it at a later time when you've connected again. Please see our documentation on [[Screen | GNU Screen]] for more information.

==Further Information==
[http://www.openssh.org/ OpenSSH]

[http://www.openssh.com/windows.html Windows Clients]

SSH/Keys

2020-10-23T20:42:32Z

Meganst: DOCS-908

SSH can utilize public key encryption to authenticate and authorize users. This can be considered more secure especially if you secure your private key with a pass-phrase. The keys themselves are not susceptible to brute force attacks like normal passwords over SSH are.

==Overview==
;Prerequisites
#If using batch clusters (e.g. [[SLURM]]) please read [[SSH/Keys#Batch clusters | Batch clusters]] prior to creating a new key.
#Determine your OS (and if Windows, what you will be using to create the key)
#*Windows
#**Git bash: follow instructions for Linux/MacOSX/Bash and Git Bash (for Windows)
#**PuTTY: follow instructions for Windows (and PuTTY subsections)
#**TTSSH2: follow instructions for Windows (and TTSSH2 subsections)
#**[[BashForWindows10 | Windows Subsystem for Linux (WSL)]]: follow instructions for 'Linux/MacOSX/Bash and Git Bash (for Windows)'
#*Linux: follow instructions for 'Linux/MacOSX/Bash and Git Bash (for Windows)'
#*MacOSX: follow instructions for 'Linux/MacOSX/Bash and Git Bash (for Windows)'
;Steps
#[[SSH/Keys#Create and store the key pair | Create and store the key pair]]
#[[SSH/Keys#Copy the public key | Copy the public key]]
#If Windows, [[SSH/Keys#Adding Keys to SSH Clients (Windows Only) | Adding Keys to SSH Clients (Windows Only)]]
;Additional Considerations
#The [[SSH/Keys#SSH Agents | SSH Agents]] section is not a required component of creating and using an SSH key, but can be very useful if you choose to create a password to protect your SSH key, but find yourself needing to enter that password many times in a session. [[SSH/Keys#SSH Agents | SSH Agents]] allow you to temporarily use your SSH key without a password for a set period of time. Please see the [[SSH/Keys#SSH Agents | SSH Agents]] section for more information.

==Create and store the key pair==

The first step is to generate a key which will create two files filled with long strings of characters. A public key file that you may distribute to any machine you want to use it on and a private key that needs to be kept secure. '''Allowing anyone to read this private key will compromise the security of the key and could allow someone to access any resources secured by this key without your consent.''' There are a number of different key types but <code>rsa</code> is the most compatible.

===Windows===
;Git Bash
:See [[SSH/Keys#Linux.2FMacOSX.2FBash_and_Git_Bash_.28for_Windows.29 | Linux/MacOSX/Bash and Git Bash (for Windows)]]
;PuTTY
# Click on the start menu and search for PuTTYgen. Open the application
# Verify that you are attempting to create an "SSH2 RSA" key by clicking on the appropriate box
# Click generate and follow the instructions for generating your keys
# Add passphrase if wanted and save both the public and private keys
;TTSSH2
# Open the application
# Cancel the first box
# Go to setup on the menu bar and go to SSH KeyGenerator
# Click generate and follow the instructions for generating your key
# Add passphrase if wanted and save both the public and private keys

===Linux/MacOSX/Bash and Git Bash (for Windows)===
;Create a new key with a password
You can run the command <code>ssh-keygen -t rsa</code> to generate the new public and private key. It will prompt you for a file to create the private key and then for the public key append <code>.pub</code> extension and store it in the same directory. Pressing enter at the passphrase step twice will create a key without a pass-phrase.

Note: If you change the file in which to save the key, please ensure that it still starts with 'id', such as 'id_umiacs_rsa'.

Example: <pre>
-bash-4.2$ ssh-keygen -t rsa
Generating public/private rsa key pair.
Enter file in which to save the key (/home/derek/.ssh/id_rsa):
Created directory '/home/derek/.ssh'.
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /home/derek/.ssh/id_rsa.
Your public key has been saved in /home/derek/.ssh/id_rsa.pub.
The key fingerprint is:
32:bf:db:74:1b:7e:d7:c6:4b:b5:6f:a8:82:55:3f:bf derek@localhost.localdomain
The key's randomart image is:
+--[ RSA 2048]----+
| |
| |
| |
| . |
| o S . . .|
| + . o o|
| .o. o B.|
| .+.o o+ O|
| o...+o E+|
+-----------------+
</pre>

;Create a new key without a password
You can simplify the existing example above by telling it you do not want a pass-phrase and can run the command <code>ssh-keygen -t rsa -N ""</code>.

Note: If you change the file in which to save the key, please ensure that it still starts with 'id', such as 'id_umiacs_rsa'.

Example: <pre>
-bash-4.2$ ssh-keygen -t rsa -N ""
Generating public/private rsa key pair.
Enter file in which to save the key (/home/derek/.ssh/id_rsa):
Created directory '/home/derek/.ssh'.
Your identification has been saved in /home/derek/.ssh/id_rsa.
Your public key has been saved in /home/derek/.ssh/id_rsa.pub.
The key fingerprint is:
ff:7a:99:28:fc:63:d6:10:44:4c:2e:68:76:44:76:7a derek@localhost.localdomain
The key's randomart image is:
+--[ RSA 2048]----+
| .+++ |
| + +o |
| + +.E |
| o . o. |
| S . |
| .. |
| . .+ o |
| o =.= |
| =o+. |
+-----------------+
</pre>

;Modify permissions
Modify the permissions of your <tt>.ssh</tt> directory as well as the private key file that you just created with <tt>chmod</tt>.

<pre>
chmod 700 ~/.ssh
chmod 600 ~/.ssh/id_rsa
</pre>

If you named your file something other than id_rsa, change <tt>id_rsa</tt> to the name of the file.

==Copy the public key==
Once you have a generated a key pair you will want to add it to one or more computers to allow you to access them.

===Windows===
For Windows hosts you can use [http://winscp.net/eng/download.php WinSCP] to copy the public key file onto a remote host. The root file system for the bash subsystem for windows is located under C:\Users\<username>\appdata\local\lxss\

===Linux/MacOSX/Bash and Git Bash (for Windows)===
This can be done with the <code>ssh-copy-id</code> command and it will prompt you the first time for your current password ('''NOT your pass-phrase'''). You can replace localhost with any other hostname you want to copy the key to. You can also specify a alternate user or identity file if you need to, please <code>man ssh-copy-id</code> for more information within your terminal. This command will ensure that not only it copies your key but secures the file so that no one can tamper and add additional authorized keys to the file on the remote host.

Example: <pre>
-bash-4.2$ ssh-copy-id localhost
/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed
/bin/ssh-copy-id: INFO: 1 key(s) remain to be installed -- if you are prompted now it is to install the new keys
derek@localhost's password:

Number of key(s) added: 1

Now try logging into the machine, with: "ssh 'localhost'"
and check to make sure that only the key(s) you wanted were added.
</pre>

==Adding Keys to SSH Clients (Windows Only)==
;PuTTY
# Open Putty and enter the Fully Qualified Domain name for the host you wish to connect to
# Go to the Connections tab on the side panel and click on the data subsection
# Under data enter your default user into the first box (Auto-login Username)
# Go to the SSH section of the side panel and then go to the Auth Section
# Under Auth click on the browse and navigate to the saved private key
# Go back to session on the side panel and save your settings by typing in a name in saved sessions pressing the save button
;TTSSH2
# Open the application
# Cancel the first box
# Go to setup on the menu bar and go to SSH Authentication
# Enter your username, Click on the option labeled "Use RSA ... key to log in", then use the private key button located next to this line to navigate to your private key file, and click Ok

==Batch clusters==
Our [[SLURM]] clusters process jobs in batch and require the ability to ssh without entering a password. When creating a key for use with [[SLURM]], follow the above instructions for creating keys without passwords.

After creating this key pair please make sure you follow the [[SSH/Keys#Copy_the_public_key | copy the public key]] instructions above to <code>localhost</code>. This will ensure that your key will be usable on all the cluster nodes since they have a shared home directory.

==SSH Agents==

While it is very useful to protect your SSH key pair with a pass-phrase it can very time consuming to re-type the pass-phrase over and over. SSH provides a agent that runs in the background and allow you add a key(s) to it with a time limit that they will be unlocked for.

<pre>
ssh-agent [SHELL]
ssh-add -t [TIME]
</pre>

You will need to specify a shell in this case <code>bash</code> but could be any shell as appropriate (<code>tcsh</code>, <code>sh</code>, etc). The time specified by <code>-t</code> is specified in seconds.

Example:
(The following would start a bash shell with passwordless SSH active for 30 minutes.)
<pre>
ssh-agent bash
ssh-add -t 1800
</pre>

You will be prompted for your passphrase and, when entered correctly, you will be able to ssh without entering a password. You can check what keys are load when you are running inside a ssh-agent by using the command <code>ssh-add -l</code>.

Example: <pre>
bash-4.2$ ssh-add -l
2048 ee:83:10:c8:2f:2c:17:5e:ef:80:42:7e:ff:75:9e:53 /home/derek/.ssh/id_rsa (RSA)
</pre>

SSH/Keys

2020-10-23T20:22:51Z

Meganst:

SSH can utilize public key encryption to authenticate and authorize users. This can be considered more secure especially if you secure your private key with a pass-phrase. The keys themselves are not susceptible to brute force attacks like normal passwords over SSH are.

==Overview==
;Prerequisites
#If using batch clusters (e.g. [[SLURM]]) please read [[SSH/Keys#Batch clusters | Batch clusters]] prior to creating a new key.
#Determine your OS (and if Windows, what you will be using to create the key)
#*Windows
#**Git bash: follow instructions for Linux/MacOSX/Bash and Git Bash (for Windows)
#**PuTTY: follow instructions for Windows (and PuTTY subsections)
#**TTSSH2: follow instructions for Windows (and TTSSH2 subsections)
#**[[BashForWindows10 | Windows Subsystem for Linux (WSL)]]: follow instructions for 'Linux/MacOSX/Bash and Git Bash (for Windows)'
#*Linux: follow instructions for 'Linux/MacOSX/Bash and Git Bash (for Windows)'
#*MacOSX: follow instructions for 'Linux/MacOSX/Bash and Git Bash (for Windows)'
;Steps
#[[SSH/Keys#Create and store the key pair | Create and store the key pair]]
#[[SSH/Keys#Copy the public key | Copy the public key]]
#If Windows, [[SSH/Keys#Adding Keys to SSH Clients (Windows Only) | Adding Keys to SSH Clients (Windows Only)]]
;Additional Considerations
#The [[SSH/Keys#SSH Agents | SSH Agents]] section is not a required component of creating and using an SSH key, but can be very useful if you choose to create a password to protect your SSH key, but find yourself needing to enter that password many times in a session. [[SSH/Keys#SSH Agents | SSH Agents]] allow you to temporarily use your SSH key without a password for a set period of time. Please see the [[SSH/Keys#SSH Agents | SSH Agents]] section for more information.

==Create and store the key pair==

The first step is to generate a key which will create two files filled with long strings of characters. A public key file that you may distribute to any machine you want to use it on and a private key that needs to be kept secure. '''Allowing anyone to read this private key will compromise the security of the key and could allow someone to access any resources secured by this key without your consent.''' There are a number of different key types but <code>rsa</code> is the most compatible.

===Windows===
;Git Bash
:See [[SSH/Keys#Linux.2FMacOSX.2FBash_and_Git_Bash_.28for_Windows.29 | Linux/MacOSX/Bash and Git Bash (for Windows)]]
;PuTTY
# Click on the start menu and search for PuTTYgen. Open the application
# Verify that you are attempting to create an "SSH2 RSA" key by clicking on the appropriate box
# Click generate and follow the instructions for generating your keys
# Add passphrase if wanted and save both the public and private keys
;TTSSH2
# Open the application
# Cancel the first box
# Go to setup on the menu bar and go to SSH KeyGenerator
# Click generate and follow the instructions for generating your key
# Add passphrase if wanted and save both the public and private keys

===Linux/MacOSX/Bash and Git Bash (for Windows)===
You can run the command <code>ssh-keygen -t rsa</code> to generate the new public and private key. It will prompt you for a file to create the private key and then for the public key append <code>.pub</code> extension and store it in the same directory. Pressing enter at the passphrase step twice will create a key without a pass-phrase.

Example: <pre>
-bash-4.2$ ssh-keygen -t rsa
Generating public/private rsa key pair.
Enter file in which to save the key (/home/derek/.ssh/id_rsa):
Created directory '/home/derek/.ssh'.
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /home/derek/.ssh/id_rsa.
Your public key has been saved in /home/derek/.ssh/id_rsa.pub.
The key fingerprint is:
32:bf:db:74:1b:7e:d7:c6:4b:b5:6f:a8:82:55:3f:bf derek@localhost.localdomain
The key's randomart image is:
+--[ RSA 2048]----+
| |
| |
| |
| . |
| o S . . .|
| + . o o|
| .o. o B.|
| .+.o o+ O|
| o...+o E+|
+-----------------+
</pre>

;Passwordless Keys
You can simplify the existing example above by telling it you do not want a pass-phrase and can run the command <code>ssh-keygen -t rsa -N ""</code>.

Example: <pre>
-bash-4.2$ ssh-keygen -t rsa -N ""
Generating public/private rsa key pair.
Enter file in which to save the key (/home/derek/.ssh/id_rsa):
Created directory '/home/derek/.ssh'.
Your identification has been saved in /home/derek/.ssh/id_rsa.
Your public key has been saved in /home/derek/.ssh/id_rsa.pub.
The key fingerprint is:
ff:7a:99:28:fc:63:d6:10:44:4c:2e:68:76:44:76:7a derek@localhost.localdomain
The key's randomart image is:
+--[ RSA 2048]----+
| .+++ |
| + +o |
| + +.E |
| o . o. |
| S . |
| .. |
| . .+ o |
| o =.= |
| =o+. |
+-----------------+
</pre>

==Copy the public key==
Once you have a generated a key pair you will want to add it to one or more computers to allow you to access them.

===Windows===
For Windows hosts you can use [http://winscp.net/eng/download.php WinSCP] to copy the public key file onto a remote host. The root file system for the bash subsystem for windows is located under C:\Users\<username>\appdata\local\lxss\

===Linux/MacOSX/Bash and Git Bash (for Windows)===
This can be done with the <code>ssh-copy-id</code> command and it will prompt you the first time for your current password ('''NOT your pass-phrase'''). You can replace localhost with any other hostname you want to copy the key to. You can also specify a alternate user or identity file if you need to, please <code>man ssh-copy-id</code> for more information within your terminal. This command will ensure that not only it copies your key but secures the file so that no one can tamper and add additional authorized keys to the file on the remote host.

Example: <pre>
-bash-4.2$ ssh-copy-id localhost
/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed
/bin/ssh-copy-id: INFO: 1 key(s) remain to be installed -- if you are prompted now it is to install the new keys
derek@localhost's password:

Number of key(s) added: 1

Now try logging into the machine, with: "ssh 'localhost'"
and check to make sure that only the key(s) you wanted were added.
</pre>

==Adding Keys to SSH Clients (Windows Only)==
;PuTTY
# Open Putty and enter the Fully Qualified Domain name for the host you wish to connect to
# Go to the Connections tab on the side panel and click on the data subsection
# Under data enter your default user into the first box (Auto-login Username)
# Go to the SSH section of the side panel and then go to the Auth Section
# Under Auth click on the browse and navigate to the saved private key
# Go back to session on the side panel and save your settings by typing in a name in saved sessions pressing the save button
;TTSSH2
# Open the application
# Cancel the first box
# Go to setup on the menu bar and go to SSH Authentication
# Enter your username, Click on the option labeled "Use RSA ... key to log in", then use the private key button located next to this line to navigate to your private key file, and click Ok

==Batch clusters==
Our [[SLURM]] clusters process jobs in batch and require the ability to ssh without entering a password. When creating a key for use with [[SLURM]], follow the above instructions for creating keys without passwords.

After creating this key pair please make sure you follow the [[SSH/Keys#Copy_the_public_key | copy the public key]] instructions above to <code>localhost</code>. This will ensure that your key will be usable on all the cluster nodes since they have a shared home directory.

==SSH Agents==

While it is very useful to protect your SSH key pair with a pass-phrase it can very time consuming to re-type the pass-phrase over and over. SSH provides a agent that runs in the background and allow you add a key(s) to it with a time limit that they will be unlocked for.

<pre>
ssh-agent [SHELL]
ssh-add -t [TIME]
</pre>

You will need to specify a shell in this case <code>bash</code> but could be any shell as appropriate (<code>tcsh</code>, <code>sh</code>, etc). The time specified by <code>-t</code> is specified in seconds.

Example:
(The following would start a bash shell with passwordless SSH active for 30 minutes.)
<pre>
ssh-agent bash
ssh-add -t 1800
</pre>

You will be prompted for your passphrase and, when entered correctly, you will be able to ssh without entering a password. You can check what keys are load when you are running inside a ssh-agent by using the command <code>ssh-add -l</code>.

Example: <pre>
bash-4.2$ ssh-add -l
2048 ee:83:10:c8:2f:2c:17:5e:ef:80:42:7e:ff:75:9e:53 /home/derek/.ssh/id_rsa (RSA)
</pre>

SSH/Keys

2020-10-23T20:21:58Z

Meganst: DOCS-908

SSH can utilize public key encryption to authenticate and authorize users. This can be considered more secure especially if you secure your private key with a pass-phrase. The keys themselves are not susceptible to brute force attacks like normal passwords over SSH are.

==Overview==
;Prerequisites
#If using batch clusters (e.g. [[SLURM]]) please read [[##Batch clusters | Batch clusters]] prior to creating a new key.
#Determine your OS (and if Windows, what you will be using to create the key)
#*Windows
#**Git bash: follow instructions for Linux/MacOSX/Bash and Git Bash (for Windows)
#**PuTTY: follow instructions for Windows (and PuTTY subsections)
#**TTSSH2: follow instructions for Windows (and TTSSH2 subsections)
#**[[BashForWindows10 | Windows Subsystem for Linux (WSL)]]: follow instructions for 'Linux/MacOSX/Bash and Git Bash (for Windows)'
#*Linux: follow instructions for 'Linux/MacOSX/Bash and Git Bash (for Windows)'
#*MacOSX: follow instructions for 'Linux/MacOSX/Bash and Git Bash (for Windows)'
;Steps
#[[SSH/Keys#Create and store the key pair | Create and store the key pair]]
#[[SSH/Keys#Copy the public key | Copy the public key]]
#If Windows, [[SSH/Keys#Adding Keys to SSH Clients (Windows Only) | Adding Keys to SSH Clients (Windows Only)]]
;Additional Considerations
#The [[SSH/Keys#SSH Agents | SSH Agents]] section is not a required component of creating and using an SSH key, but can be very useful if you choose to create a password to protect your SSH key, but find yourself needing to enter that password many times in a session. [[SSH/Keys#SSH Agents | SSH Agents]] allow you to temporarily use your SSH key without a password for a set period of time. Please see the [[SSH/Keys#SSH Agents | SSH Agents]] section for more information.

==Create and store the key pair==

The first step is to generate a key which will create two files filled with long strings of characters. A public key file that you may distribute to any machine you want to use it on and a private key that needs to be kept secure. '''Allowing anyone to read this private key will compromise the security of the key and could allow someone to access any resources secured by this key without your consent.''' There are a number of different key types but <code>rsa</code> is the most compatible.

===Windows===
;Git Bash
:See [[SSH/Keys#Linux.2FMacOSX.2FBash_and_Git_Bash_.28for_Windows.29 | Linux/MacOSX/Bash and Git Bash (for Windows)]]
;PuTTY
# Click on the start menu and search for PuTTYgen. Open the application
# Verify that you are attempting to create an "SSH2 RSA" key by clicking on the appropriate box
# Click generate and follow the instructions for generating your keys
# Add passphrase if wanted and save both the public and private keys
;TTSSH2
# Open the application
# Cancel the first box
# Go to setup on the menu bar and go to SSH KeyGenerator
# Click generate and follow the instructions for generating your key
# Add passphrase if wanted and save both the public and private keys

===Linux/MacOSX/Bash and Git Bash (for Windows)===
You can run the command <code>ssh-keygen -t rsa</code> to generate the new public and private key. It will prompt you for a file to create the private key and then for the public key append <code>.pub</code> extension and store it in the same directory. Pressing enter at the passphrase step twice will create a key without a pass-phrase.

Example: <pre>
-bash-4.2$ ssh-keygen -t rsa
Generating public/private rsa key pair.
Enter file in which to save the key (/home/derek/.ssh/id_rsa):
Created directory '/home/derek/.ssh'.
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /home/derek/.ssh/id_rsa.
Your public key has been saved in /home/derek/.ssh/id_rsa.pub.
The key fingerprint is:
32:bf:db:74:1b:7e:d7:c6:4b:b5:6f:a8:82:55:3f:bf derek@localhost.localdomain
The key's randomart image is:
+--[ RSA 2048]----+
| |
| |
| |
| . |
| o S . . .|
| + . o o|
| .o. o B.|
| .+.o o+ O|
| o...+o E+|
+-----------------+
</pre>

;Passwordless Keys
You can simplify the existing example above by telling it you do not want a pass-phrase and can run the command <code>ssh-keygen -t rsa -N ""</code>.

Example: <pre>
-bash-4.2$ ssh-keygen -t rsa -N ""
Generating public/private rsa key pair.
Enter file in which to save the key (/home/derek/.ssh/id_rsa):
Created directory '/home/derek/.ssh'.
Your identification has been saved in /home/derek/.ssh/id_rsa.
Your public key has been saved in /home/derek/.ssh/id_rsa.pub.
The key fingerprint is:
ff:7a:99:28:fc:63:d6:10:44:4c:2e:68:76:44:76:7a derek@localhost.localdomain
The key's randomart image is:
+--[ RSA 2048]----+
| .+++ |
| + +o |
| + +.E |
| o . o. |
| S . |
| .. |
| . .+ o |
| o =.= |
| =o+. |
+-----------------+
</pre>

==Copy the public key==
Once you have a generated a key pair you will want to add it to one or more computers to allow you to access them.

===Windows===
For Windows hosts you can use [http://winscp.net/eng/download.php WinSCP] to copy the public key file onto a remote host. The root file system for the bash subsystem for windows is located under C:\Users\<username>\appdata\local\lxss\

===Linux/MacOSX/Bash and Git Bash (for Windows)===
This can be done with the <code>ssh-copy-id</code> command and it will prompt you the first time for your current password ('''NOT your pass-phrase'''). You can replace localhost with any other hostname you want to copy the key to. You can also specify a alternate user or identity file if you need to, please <code>man ssh-copy-id</code> for more information within your terminal. This command will ensure that not only it copies your key but secures the file so that no one can tamper and add additional authorized keys to the file on the remote host.

Example: <pre>
-bash-4.2$ ssh-copy-id localhost
/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed
/bin/ssh-copy-id: INFO: 1 key(s) remain to be installed -- if you are prompted now it is to install the new keys
derek@localhost's password:

Number of key(s) added: 1

Now try logging into the machine, with: "ssh 'localhost'"
and check to make sure that only the key(s) you wanted were added.
</pre>

==Adding Keys to SSH Clients (Windows Only)==
;PuTTY
# Open Putty and enter the Fully Qualified Domain name for the host you wish to connect to
# Go to the Connections tab on the side panel and click on the data subsection
# Under data enter your default user into the first box (Auto-login Username)
# Go to the SSH section of the side panel and then go to the Auth Section
# Under Auth click on the browse and navigate to the saved private key
# Go back to session on the side panel and save your settings by typing in a name in saved sessions pressing the save button
;TTSSH2
# Open the application
# Cancel the first box
# Go to setup on the menu bar and go to SSH Authentication
# Enter your username, Click on the option labeled "Use RSA ... key to log in", then use the private key button located next to this line to navigate to your private key file, and click Ok

==Batch clusters==
Our [[SLURM]] clusters process jobs in batch and require the ability to ssh without entering a password. When creating a key for use with [[SLURM]], follow the above instructions for creating keys without passwords.

After creating this key pair please make sure you follow the [[SSH/Keys#Copy_the_public_key | copy the public key]] instructions above to <code>localhost</code>. This will ensure that your key will be usable on all the cluster nodes since they have a shared home directory.

==SSH Agents==

While it is very useful to protect your SSH key pair with a pass-phrase it can very time consuming to re-type the pass-phrase over and over. SSH provides a agent that runs in the background and allow you add a key(s) to it with a time limit that they will be unlocked for.

<pre>
ssh-agent [SHELL]
ssh-add -t [TIME]
</pre>

You will need to specify a shell in this case <code>bash</code> but could be any shell as appropriate (<code>tcsh</code>, <code>sh</code>, etc). The time specified by <code>-t</code> is specified in seconds.

Example:
(The following would start a bash shell with passwordless SSH active for 30 minutes.)
<pre>
ssh-agent bash
ssh-add -t 1800
</pre>

You will be prompted for your passphrase and, when entered correctly, you will be able to ssh without entering a password. You can check what keys are load when you are running inside a ssh-agent by using the command <code>ssh-add -l</code>.

Example: <pre>
bash-4.2$ ssh-add -l
2048 ee:83:10:c8:2f:2c:17:5e:ef:80:42:7e:ff:75:9e:53 /home/derek/.ssh/id_rsa (RSA)
</pre>

Quota

2019-08-08T21:41:06Z

Meganst: Per DOCS-839, added nfshomes to the list of fluidfs mounted home directories. Moved 'Tree Quotas' to the bottom and updated phrasing accordingly.

==RPC Quotas==
File systems that support RPC quotad quotas are reported to the user by the '''<tt>quota</tt>''' command. Home directories that are mounted from our Dell FluidFS NAS will support these kinds of quotas (/cliphomes, /cfarhomes, /cbcbhomes, /nfshomes).

To find out what your current quota is, first run '''<tt>df .</tt>''' to find out what file system you are currently mounted from (in this example it is <tt>fluidfs:/rama_cfarhomes/derek</tt>). '''Please note that the Use% here is for the entire file system and not your user-specific home directory.'''
<pre>
# df .
Filesystem 1K-blocks Used Available Use% Mounted on
fluidfs:/rama_cfarhomes/derek
1073741824 759351008 314390816 71% /cfarhomes/derek
</pre>

Then run '''<tt>quota</tt>''' and that line will list your quota information for that file system. If you see errors such as "Error while getting quota from ..." you may safely ignore these as some of our file systems such as Gluster do not report quotas correctly.

<pre>
$ quota
Disk quotas for user derek (uid 2174):
Filesystem blocks quota limit grace files quota limit grace
fluidfs:/rama_cfarhomes/derek
337560 0 10240000 0 0 0
</pre>

If you have hit your RPC quota and haven't realized it, you may see some strange issues. For example, you will not be able to write-out files (although 'touch' and file concatenation will succeed). Some applications such as vi will throw "FSync" errors. Similarly, commands such as wget will appear to succeed but your files will be zero-length.

==Tree Quotas==
An alternate style of quota management is done through tree quotas that show up in how much space is available in the file system by using the '''<tt>df</tt>''' command to inspect either the current path (no arguments given) or a given path.

For example to show my /nfshomes/derektest home directory quota i can just use '''<tt>df ~</tt>'''
<pre>
$ df ~
Filesystem 1K-blocks Used Available Use% Mounted on
umiacsfs02:/nfshomes/derektest
1024000 49984 974016 5% /nfshomes/derektest
</pre>

PrinterQueueNaming

2019-04-10T15:51:20Z

Meganst: /* Printer Queues */

==Printer Queues==

UMIACS uses a centralized print server to manage all of the printers in the Institute. See [[Printing]] for more details specific to your OS. We have developed a naming scheme for our printer queues based on the colors the printer can produce, the type of queue, the building number, and the room number.

The naming scheme is as follows:

* All color printers begin with a "c". Black & white is the default so nothing extra is needed.
* Then is either "ps" for a postscript queue or "pcl" for a PCL queue. Postscript and PCL are types of printer drivers. If you are unsure what this means, use "ps" for postscript.
* Then add the building number. E.g. add "432" for IRB.
* Add a dash ("-").
* Then add the room number. E.g. If the printer is in room 3108, add "3108".

[[Image:Printerqueueformat.JPG|600px|left]]
 

Some examples:

* ps432-3108 is a black & white printer in Iribe 3108.
* cps296-3120h is a color printer in BSB.

PrinterQueueNaming

2019-04-10T15:50:01Z

Meganst:

==Printer Queues==

UMIACS uses a centralized print server to manage all of the printers in the Institute. See [[Printing]] for more details specific to your OS. We have developed a naming scheme for our printer queues based on the colors the printer can produce, the type of queue, the building number, and the room number.

The naming scheme is as follows:

* All color printers begin with a "c". Black & white is the default so nothing extra is needed.
* Then is either "ps" for a postscript queue or "pcl" for a PCL queue. Postscript and PCL are types of printer drivers. If you are unsure what this means, use "ps" for postscript.
* Then add the building number. E.g. add "432" for IRB.
* Add a dash ("-").
* Then add the room number. E.g. If the printer is in room 3108, add "3108".

[[Image:Printerqueueformat.JPG|600px|left]]
 

Some examples:

* cps3142 is a color printer in AV Williams 3142.
* ps432-3108 is a black & white printer in Iribe 3108.
* cps296-3120h is a color printer in BSB.

File:Printerqueueformat.JPG

2019-04-10T15:45:32Z

Meganst: Printer queue format updated for Iribe.

Printer queue format updated for Iribe.

WindowsPrintingUMIACS

2019-03-21T17:36:43Z

Meganst: Fixed a formatting issue in the PIN-Protected job subsection.

==Introduction==

This will guide you through the process of installing and using the printers available within UMIACS.

==Printing Outside of UMIACS / Laptop Printing==

If you are off the UMIACS network, you must first connect to the [[VPN]] on Windows. After you are connected, follow the instructions for adding a printer queue below. Please note that you must be on the VPN whenever you print.

==Pre-Installation Knowledge on Printing at UMIACS==

[[PrinterQueueNaming| Printer Queue Naming]]

==Installation of printer queue==

Please note that this applies to machines on any UMIACS network. This includes all proxy networks, the vast majority of machines in the labs, and machines connected to the UMIACS VPN but not the wireless network alone.

To add printer queues:

Go to start, click and type in “\\printers.ad.umiacs.umd.edu” in the search box.

[[Image:Win7doc1.jpg]] [[Image:Win7doc2.jpg]]

'''You may be prompted with a box for authentication. Make sure to prefix 'UMIACS\' to your username. (For example, if your username was 'johndoe' you would enter 'UMIACS\johndoe' in the username box)

[[File:UMIACSprinting.png]]

A list of printer queues will appear. Select your desired printer by double clicking on the queue. Once you have double clicked on the queue a box will immediately pop up to show you the status of the printer driver installation. Once that is complete you can start using the printer.

[[Image:Win7doc3.jpg]]

==Removing a printer queue==

To remove a printer queue, open the start menu and click on control panel. Next, click on "View devices and printers." To remove the queue, right click on the printer and select "remove device." If you wish to add the printer back, follow the instructions above.

[[Image:Win7printremove.jpg]]
==Duplex Printing==

Many printers in UMIACS support duplex (2 sided) printing. To make the duplex printing default, first make sure the appropriate printer queue is installed via the directions above. Afterwards, go to start, then “Devices and Printers.”
Once the printer has been installed proceed by right clicking on the queue then selecting “Printing preferences.”

[[Image:Win7doc4.jpg]]

After a few seconds the following menu will come up. Make sure you are on the “Printing Shortcuts” tab and select the “Eco-Print (Two-sided Printing)” option then click on okay. This modification will allow you to print 2-sided whenever you choose to use this printer.

[[Image:Win7doc5.jpg]]

==Store and Print PIN-Protected Jobs==

'''Create a stored job'''

<ol>
<li> From the software program, select the '''Print''' option.
<li> Select the printer from the list of printers, and then select '''Properties''' or '''Preferences''' (name varies by software program)
<li> Click the '''Job Storage''' tab.
<li> Under '''Job Storage Mode''', select '''Personal Job'''.
 
[[Image:Pinprint_1_mode.jpg|600px|left]]
 
<li> In the drop-down menu under '''Make Job Private/Secure''', select '''PIN to print''', and type in a 4-digit number.
 
[[Image:Pinprint_2_pin.jpg|600px|left]]
 
: Note: You will need to provide the entered PIN (4-digit number) at the printer's control panel.
<li> Click the '''OK''' button to close the Document Properties/Preferences dialog box. In the Print dialog box, click '''Print'''.
</ol>

'''Print a stored job'''

After you have created a stored job using the instructions above, follow these steps to print from the printer's control panel.

<ol>
<li> From the Home screen on the printer control panel, select '''Print'''.
<li> Select '''Print from Job Storage'''.
 
[[Image:Pinprint_3_printfrom.jpg|600px|left]]
 
<li> Select '''Choose''', and then select the name of the folder where the job is stored.
 
[[Image:Pinprint_4_folder.jpg|600px|left]]
 
<li> Select the name of the job, enter your chosen PIN (4-digit number), and click '''Ok'''.
 
[[Image:Pinprint_5_pin.jpg|600px|left]]
 
<li> Select '''Print''' to print the job.
 
[[Image:Pinprint_6_print.jpg|600px|left]]
 
: Note: The print job is deleted from memory after it prints.
</ol>

WindowsPrintingUMIACS

2019-03-21T17:30:06Z

Meganst: Added instructions to create a PIN-projected print job.

==Introduction==

This will guide you through the process of installing and using the printers available within UMIACS.

==Printing Outside of UMIACS / Laptop Printing==

If you are off the UMIACS network, you must first connect to the [[VPN]] on Windows. After you are connected, follow the instructions for adding a printer queue below. Please note that you must be on the VPN whenever you print.

==Pre-Installation Knowledge on Printing at UMIACS==

[[PrinterQueueNaming| Printer Queue Naming]]

==Installation of printer queue==

Please note that this applies to machines on any UMIACS network. This includes all proxy networks, the vast majority of machines in the labs, and machines connected to the UMIACS VPN but not the wireless network alone.

To add printer queues:

Go to start, click and type in “\\printers.ad.umiacs.umd.edu” in the search box.

[[Image:Win7doc1.jpg]] [[Image:Win7doc2.jpg]]

'''You may be prompted with a box for authentication. Make sure to prefix 'UMIACS\' to your username. (For example, if your username was 'johndoe' you would enter 'UMIACS\johndoe' in the username box)

[[File:UMIACSprinting.png]]

A list of printer queues will appear. Select your desired printer by double clicking on the queue. Once you have double clicked on the queue a box will immediately pop up to show you the status of the printer driver installation. Once that is complete you can start using the printer.

[[Image:Win7doc3.jpg]]

==Removing a printer queue==

To remove a printer queue, open the start menu and click on control panel. Next, click on "View devices and printers." To remove the queue, right click on the printer and select "remove device." If you wish to add the printer back, follow the instructions above.

[[Image:Win7printremove.jpg]]
==Duplex Printing==

Many printers in UMIACS support duplex (2 sided) printing. To make the duplex printing default, first make sure the appropriate printer queue is installed via the directions above. Afterwards, go to start, then “Devices and Printers.”
Once the printer has been installed proceed by right clicking on the queue then selecting “Printing preferences.”

[[Image:Win7doc4.jpg]]

After a few seconds the following menu will come up. Make sure you are on the “Printing Shortcuts” tab and select the “Eco-Print (Two-sided Printing)” option then click on okay. This modification will allow you to print 2-sided whenever you choose to use this printer.

[[Image:Win7doc5.jpg]]

==Store and Print PIN-Protected Jobs==

'''Create a stored job'''

<ol>
<li> From the software program, select the '''Print''' option.
<li> Select the printer from the list of printers, and then select '''Properties''' or '''Preferences''' (name varies by software program)
<li> Click the '''Job Storage''' tab.
<li> Under '''Job Storage Mode''', select '''Personal Job'''.
 
[[Image:Pinprint_1_mode.jpg|600px|left]]
 
<li> In the drop-down menu under '''Make Job Private/Secure''', select '''PIN to print''', and type in a 4-digit number.
 
[[Image:Pinprint_2_pin.jpg|600px|left]]
 
: Note: You will need to provide the entered PIN (4-digit number) at the printer's control panel.
<li> Click the '''OK''' button to close the Document Properties/Preferences dialog box. In the Print dialog box, click '''Print'''.
</ol>

'''Print a stored job'''

After you have created a stored job using the instructions above, follow these steps to print from the printer's control panel.

<ol>
<li> From the Home screen on the printer control panel, select '''Print'''.
<li> Select '''Print from Job Storage'''.
 
[[Image:Pinprint_3_printfrom.jpg|600px|left]]
 
<li> Select Choose, and then select the name of the folder where the job is stored.
 
[[Image:Pinprint_4_folder.jpg|600px|left]]
 
<li> Select the name of the job, enter your chosen PIN (4-digit number), and click '''Ok'''.
 
[[Image:Pinprint_5_pin.jpg|600px|left]]
 
<li> Select Print to print the job.
 
[[Image:Pinprint_6_print.jpg|600px|left]]
 
: Note: The print job is deleted from memory after it prints.
</ol>

File:Pinprint 6 print.jpg

2019-03-21T17:27:46Z

Meganst:

File:Pinprint 5 pin.jpg

2019-03-21T17:27:34Z

Meganst:

File:Pinprint 4 folder.jpg

2019-03-21T17:27:21Z

Meganst:

File:Pinprint 3 printfrom.jpg

2019-03-21T16:47:26Z

Meganst:

File:Pinprint 2 pin.jpg

2019-03-21T16:44:32Z

Meganst:

File:Pinprint 1 mode.jpg

2019-03-21T16:28:30Z

Meganst: