UMIACS - User contributions [en]

SecureShell

2010-05-05T15:04:08Z

Xhe: /* Passwordless SSH with SSH Keys */

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 RedHat Linux 3, 4, and 5, and Mac OS X, 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.

On Windows XP or Vista hosts there are no SFTP clients installed by default. Users can install either which will enable SSH and SFTP access.

* [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY]
* [http://ttssh2.sourceforge.jp/ ttssh2]

Alternatively, all users can use the UMIACS Intranet SFTP Web Applet located [https://intranet.umiacs.umd.edu/ssh/ here] without installing any additional software.

==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 RedHat Linux 3, 4, and 5, and Mac OS X, the following command from a terminal will connect a client computer to the UMIACS [[OpenLAB]] using X11 Forwarding.
# ssh '''-X''' bkirz@openlab.umiacs.umd.edu

'''Note:''' Mac users must have X11 installed in their systems for X11 forwarding to work. This can be checked by looking for X11.app in /Applications/Utilities. You can find the installer [http://www.apple.com/support/downloads/x11formacosx.html here].

Windows users can enable X11 forwarding on UMIACS desktops by using cygwin to ssh -X.
If you do not have Cygwin, you will need to forward X through Xming.
First, enable X forwarding on your secure ssh client. The option is under tunneling in the ssh client settings. This only has to be done once.

[[Image:sshXForward.jpg]]

Next, click save in the main ssh appication window to save this setting.

After this has been done, every time you want to use X forwarding, you need to make sure 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.

Note that the UMIACS Intranet SFTP Web Applet does ''not'' allow X11 Forwarding.

==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.

==Passwordless SSH with SSH Keys==

There are some situations where it is important to be able to ssh without entering a password. This is mostly required when working in clusters. This is done using ssh keys. Instead of authenticating with a password, ssh can use a pre-defined set of encryption keys to establish an authorized connection.
To setup passwordless ssh, do the following.

First, you will need to create a ssh key pair. It is possible to use a password that you will need to enter at the beginning of your work session. This is preferable as it is more secure but may cause problems for some clustered work, particularly our TORQUE/MAUI clusters. If you simply hit '''[enter]''', you will never be prompted for a password when ssh'ing which can lead to security problems.

To create a '''''passwordless''''' key, type the following. '''NOTE: This is ''REQUIRED'' for our [[ClusterGuide|TORQUE/MAUI]]-based clusters!'''

# ssh-keygen -N "" -t dsa

To create a '''''passphrase-protected''''' (more-secure) key, type the following. Do not use this option if you plan to use any of our [[ClusterGuide|TORQUE/MAUI]]-based clusters.

# ssh-keygen -t dsa

This will produce two files, '''id_dsa''' and '''id_dsa.pub''', the private and public keys respectively. Once you've created the keys, you will need to put them into place as follows:

# mkdir ~/.ssh
# chmod 700 ~/.ssh
# mv id_dsa ~/.ssh
# chmod 600 ~/.ssh/id_dsa
# touch ~/.ssh/authorized_keys2
# chmod 600 ~/.ssh/authorized_keys2
# cat id_dsa.pub >> ~/.ssh/authorized_keys2
# rm id_dsa.pub

It is '''very''' important that you keep your private key secure! Ensure that it is chmod'd to 600 and that you do not put it anywhere visible to other users!

If you did not select a passphrase when you generated your keys, you can now ssh without a password. If you did select a passphrase, you will need to activate the keys as follows:

# ssh-agent [SHELL]
# ssh-add -t [TIME]

In this case, "[SHELL]" is your preferred shell and "[TIME]" is the amount of time you'd like the key to be active in seconds. So, the following would start a bash shell with passwordless ssh active for 30 minutes:

# ssh-agent bash
# ssh-add -t 1800

You will be prompted for your passphrase and, when entered correctly, you will be able to ssh without entering a password.

To disable this functionality, simply delete your private key file ('''~/.ssh/id_dsa''') and remove the public key from your '''~/.ssh/authorized_keys2''' file.

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

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

SecureShell

2010-05-05T15:00:03Z

Xhe: /* Passwordless SSH with SSH Keys */

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 RedHat Linux 3, 4, and 5, and Mac OS X, 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.

On Windows XP or Vista hosts there are no SFTP clients installed by default. Users can install either which will enable SSH and SFTP access.

* [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY]
* [http://ttssh2.sourceforge.jp/ ttssh2]

Alternatively, all users can use the UMIACS Intranet SFTP Web Applet located [https://intranet.umiacs.umd.edu/ssh/ here] without installing any additional software.

==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 RedHat Linux 3, 4, and 5, and Mac OS X, the following command from a terminal will connect a client computer to the UMIACS [[OpenLAB]] using X11 Forwarding.
# ssh '''-X''' bkirz@openlab.umiacs.umd.edu

'''Note:''' Mac users must have X11 installed in their systems for X11 forwarding to work. This can be checked by looking for X11.app in /Applications/Utilities. You can find the installer [http://www.apple.com/support/downloads/x11formacosx.html here].

Windows users can enable X11 forwarding on UMIACS desktops by using cygwin to ssh -X.
If you do not have Cygwin, you will need to forward X through Xming.
First, enable X forwarding on your secure ssh client. The option is under tunneling in the ssh client settings. This only has to be done once.

[[Image:sshXForward.jpg]]

Next, click save in the main ssh appication window to save this setting.

After this has been done, every time you want to use X forwarding, you need to make sure 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.

Note that the UMIACS Intranet SFTP Web Applet does ''not'' allow X11 Forwarding.

==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.

==Passwordless SSH with SSH Keys==

There are some situations where it is important to be able to ssh without entering a password. This is mostly required when working in clusters. This is done using ssh keys. Instead of authenticating with a password, ssh can use a pre-defined set of encryption keys to establish an authorized connection.
To setup passwordless ssh, do the following.

First, you will need to create a ssh key pair. It is possible to use a password that you will need to enter at the beginning of your work session. This is preferable as it is more secure but may cause problems for some clustered work, particularly our TORQUE/MAUI clusters. If you simply hit '''[enter]''', you will never be prompted for a password when ssh'ing which can lead to security problems.

To create a '''''passwordless''''' key, type the following. '''NOTE: This is ''REQUIRED'' for our [[ClusterGuide|TORQUE/MAUI]]-based clusters!'''

# ssh-keygen -N "" -t dsa

To create a '''''passphrase-protected''''' (more-secure) key, type the following. Do not use this option if you plan to use our any of [[ClusterGuide|TORQUE/MAUI]]-based clusters.

# ssh-keygen -t dsa

This will produce two files, '''id_dsa''' and '''id_dsa.pub''', the private and public keys respectively. Once you've created the keys, you will need to put them into place as follows:

# mkdir ~/.ssh
# chmod 700 ~/.ssh
# mv id_dsa ~/.ssh
# chmod 600 ~/.ssh/id_dsa
# touch ~/.ssh/authorized_keys2
# chmod 600 ~/.ssh/authorized_keys2
# cat id_dsa.pub >> ~/.ssh/authorized_keys2
# rm id_dsa.pub

It is '''very''' important that you keep your private key secure! Ensure that it is chmod'd to 600 and that you do not put it anywhere visible to other users!

If you did not select a passphrase when you generated your keys, you can now ssh without a password. If you did select a passphrase, you will need to activate the keys as follows:

# ssh-agent [SHELL]
# ssh-add -t [TIME]

In this case, "[SHELL]" is your preferred shell and "[TIME]" is the amount of time you'd like the key to be active in seconds. So, the following would start a bash shell with passwordless ssh active for 30 minutes:

# ssh-agent bash
# ssh-add -t 1800

You will be prompted for your passphrase and, when entered correctly, you will be able to ssh without entering a password.

To disable this functionality, simply delete your private key file ('''~/.ssh/id_dsa''') and remove the public key from your '''~/.ssh/authorized_keys2''' file.

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

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

SecureShell

2010-05-04T22:12:54Z

Xhe: /* Passwordless SSH with SSH Keys for TORQUE/MAUI Cluster */

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 RedHat Linux 3, 4, and 5, and Mac OS X, 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.

On Windows XP or Vista hosts there are no SFTP clients installed by default. Users can install either which will enable SSH and SFTP access.

* [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY]
* [http://ttssh2.sourceforge.jp/ ttssh2]

Alternatively, all users can use the UMIACS Intranet SFTP Web Applet located [https://intranet.umiacs.umd.edu/ssh/ here] without installing any additional software.

==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 RedHat Linux 3, 4, and 5, and Mac OS X, the following command from a terminal will connect a client computer to the UMIACS [[OpenLAB]] using X11 Forwarding.
# ssh '''-X''' bkirz@openlab.umiacs.umd.edu

'''Note:''' Mac users must have X11 installed in their systems for X11 forwarding to work. This can be checked by looking for X11.app in /Applications/Utilities. You can find the installer [http://www.apple.com/support/downloads/x11formacosx.html here].

Windows users can enable X11 forwarding on UMIACS desktops by using cygwin to ssh -X.
If you do not have Cygwin, you will need to forward X through Xming.
First, enable X forwarding on your secure ssh client. The option is under tunneling in the ssh client settings. This only has to be done once.

[[Image:sshXForward.jpg]]

Next, click save in the main ssh appication window to save this setting.

After this has been done, every time you want to use X forwarding, you need to make sure 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.

Note that the UMIACS Intranet SFTP Web Applet does ''not'' allow X11 Forwarding.

==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.

==Passwordless SSH with SSH Keys==

There are some situations where it is important to be able to ssh without entering a password. This is mostly required when working in clusters. This is done using ssh keys. Instead of authenticating with a password, ssh can use a pre-defined set of encryption keys to establish an authorized connection.
To setup passwordless ssh, do the following.

First, create an ssh key pair:

# ssh-keygen -t dsa

The command will prompt you for a passphrase. If you use a password, you will need to enter it at the beginning of your work session. This is preferable as it is more secure but may cause problems for some clustered work, such as TORQUE/MAUI cluster. If you simply hit '''[enter]''', you will never be prompted for a password when ssh'ing which can lead to security problems.

This will produce two files, '''id_dsa''' and '''id_dsa.pub''', the private and public keys respectively. Once you've created the keys, you will need to put them into place as follows:

# mkdir ~/.ssh
# chmod 700 ~/.ssh
# mv id_dsa ~/.ssh
# chmod 600 ~/.ssh/id_dsa
# touch ~/.ssh/authorized_keys2
# chmod 600 ~/.ssh/authorized_keys2
# cat id_dsa.pub >> authorized_keys2
# rm id_dsa.pub

It is '''very''' important that you keep your private key secure! Ensure that it is chmod'd to 600 and that you do not put it anywhere visible to other users!

If you did not select a passphrase when you generated your keys, you can now ssh without a password. If you did select a passphrase, you will need to activate the keys as follows:

# ssh-agent [SHELL]
# ssh-add -t [TIME]

In this case, "[SHELL]" is your preferred shell and "[TIME]" is the amount of time you'd like the key to be active in seconds. So, the following would start a bash shell with passwordless ssh active for 30 minutes:

# ssh-agent bash
# ssh-add -t 1800

You will be prompted for your passphrase and, when entered correctly, you will be able to ssh without entering a password.

To disable this functionality, simply delete your private key file ('''~/.ssh/id_dsa''') and remove the public key from your '''~/.ssh/authorized_keys2''' file.

==Passwordless SSH with SSH Keys for TORQUE/MAUI Cluster==

To set up passwordless ssh for TORQUE/MAUI cluster, please follow the steps below.

#cd $HOME
#ssh-keygen -t dsa -N "" -f $HOME/.ssh/id_dsa
#cd .ssh
#touch authorized_keys2
#cat id_dsa.pub >> authorized_keys2
#chmod 640 authorized_keys2

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

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

SecureShell

2010-05-04T22:11:59Z

Xhe: /* Passwordless SSH with SSH Keys */

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 RedHat Linux 3, 4, and 5, and Mac OS X, 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.

On Windows XP or Vista hosts there are no SFTP clients installed by default. Users can install either which will enable SSH and SFTP access.

* [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY]
* [http://ttssh2.sourceforge.jp/ ttssh2]

Alternatively, all users can use the UMIACS Intranet SFTP Web Applet located [https://intranet.umiacs.umd.edu/ssh/ here] without installing any additional software.

==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 RedHat Linux 3, 4, and 5, and Mac OS X, the following command from a terminal will connect a client computer to the UMIACS [[OpenLAB]] using X11 Forwarding.
# ssh '''-X''' bkirz@openlab.umiacs.umd.edu

'''Note:''' Mac users must have X11 installed in their systems for X11 forwarding to work. This can be checked by looking for X11.app in /Applications/Utilities. You can find the installer [http://www.apple.com/support/downloads/x11formacosx.html here].

Windows users can enable X11 forwarding on UMIACS desktops by using cygwin to ssh -X.
If you do not have Cygwin, you will need to forward X through Xming.
First, enable X forwarding on your secure ssh client. The option is under tunneling in the ssh client settings. This only has to be done once.

[[Image:sshXForward.jpg]]

Next, click save in the main ssh appication window to save this setting.

After this has been done, every time you want to use X forwarding, you need to make sure 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.

Note that the UMIACS Intranet SFTP Web Applet does ''not'' allow X11 Forwarding.

==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.

==Passwordless SSH with SSH Keys==

There are some situations where it is important to be able to ssh without entering a password. This is mostly required when working in clusters. This is done using ssh keys. Instead of authenticating with a password, ssh can use a pre-defined set of encryption keys to establish an authorized connection.
To setup passwordless ssh, do the following.

First, create an ssh key pair:

# ssh-keygen -t dsa

The command will prompt you for a passphrase. If you use a password, you will need to enter it at the beginning of your work session. This is preferable as it is more secure but may cause problems for some clustered work, such as TORQUE/MAUI cluster. If you simply hit '''[enter]''', you will never be prompted for a password when ssh'ing which can lead to security problems.

This will produce two files, '''id_dsa''' and '''id_dsa.pub''', the private and public keys respectively. Once you've created the keys, you will need to put them into place as follows:

# mkdir ~/.ssh
# chmod 700 ~/.ssh
# mv id_dsa ~/.ssh
# chmod 600 ~/.ssh/id_dsa
# touch ~/.ssh/authorized_keys2
# chmod 600 ~/.ssh/authorized_keys2
# cat id_dsa.pub >> authorized_keys2
# rm id_dsa.pub

It is '''very''' important that you keep your private key secure! Ensure that it is chmod'd to 600 and that you do not put it anywhere visible to other users!

If you did not select a passphrase when you generated your keys, you can now ssh without a password. If you did select a passphrase, you will need to activate the keys as follows:

# ssh-agent [SHELL]
# ssh-add -t [TIME]

In this case, "[SHELL]" is your preferred shell and "[TIME]" is the amount of time you'd like the key to be active in seconds. So, the following would start a bash shell with passwordless ssh active for 30 minutes:

# ssh-agent bash
# ssh-add -t 1800

You will be prompted for your passphrase and, when entered correctly, you will be able to ssh without entering a password.

To disable this functionality, simply delete your private key file ('''~/.ssh/id_dsa''') and remove the public key from your '''~/.ssh/authorized_keys2''' file.

==Passwordless SSH with SSH Keys for TORQUE/MAUI Cluster==

To set up passwordless ssh for TORQUE/MAUI cluster, do the following.

#cd $HOME
#ssh-keygen -t dsa -N "" -f $HOME/.ssh/id_dsa
#cd .ssh
#touch authorized_keys2
#cat id_dsa.pub >> authorized_keys2
#chmod 640 authorized_keys2

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

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

SecureShell

2010-05-04T22:09:23Z

Xhe: /* Passwordless SSH with SSH Keys for TORQUE/MAUI Cluster */

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 RedHat Linux 3, 4, and 5, and Mac OS X, 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.

On Windows XP or Vista hosts there are no SFTP clients installed by default. Users can install either which will enable SSH and SFTP access.

* [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY]
* [http://ttssh2.sourceforge.jp/ ttssh2]

Alternatively, all users can use the UMIACS Intranet SFTP Web Applet located [https://intranet.umiacs.umd.edu/ssh/ here] without installing any additional software.

==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 RedHat Linux 3, 4, and 5, and Mac OS X, the following command from a terminal will connect a client computer to the UMIACS [[OpenLAB]] using X11 Forwarding.
# ssh '''-X''' bkirz@openlab.umiacs.umd.edu

'''Note:''' Mac users must have X11 installed in their systems for X11 forwarding to work. This can be checked by looking for X11.app in /Applications/Utilities. You can find the installer [http://www.apple.com/support/downloads/x11formacosx.html here].

Windows users can enable X11 forwarding on UMIACS desktops by using cygwin to ssh -X.
If you do not have Cygwin, you will need to forward X through Xming.
First, enable X forwarding on your secure ssh client. The option is under tunneling in the ssh client settings. This only has to be done once.

[[Image:sshXForward.jpg]]

Next, click save in the main ssh appication window to save this setting.

After this has been done, every time you want to use X forwarding, you need to make sure 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.

Note that the UMIACS Intranet SFTP Web Applet does ''not'' allow X11 Forwarding.

==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.

==Passwordless SSH with SSH Keys==

There are some situations where it is important to be able to ssh without entering a password. This is mostly required when working in clusters. This is done using ssh keys. Instead of authenticating with a password, ssh can use a pre-defined set of encryption keys to establish an authorized connection.
To setup passwordless ssh, do the following.

First, create an ssh key pair:

# ssh-keygen -t dsa

The command will prompt you for a passphrase. If you use a password, you will need to enter it at the beginning of your work session. This is preferable as it is more secure but may cause problems for some clustered work, such as TORQUE/PBS cluster. If you simply hit '''[enter]''', you will never be prompted for a password when ssh'ing which can lead to security problems.

This will produce two files, '''id_dsa''' and '''id_dsa.pub''', the private and public keys respectively. Once you've created the keys, you will need to put them into place as follows:

# mkdir ~/.ssh
# chmod 700 ~/.ssh
# mv id_dsa ~/.ssh
# chmod 600 ~/.ssh/id_dsa
# touch ~/.ssh/authorized_keys2
# chmod 600 ~/.ssh/authorized_keys2
# cat id_dsa.pub >> authorized_keys2
# rm id_dsa.pub

It is '''very''' important that you keep your private key secure! Ensure that it is chmod'd to 600 and that you do not put it anywhere visible to other users!

If you did not select a passphrase when you generated your keys, you can now ssh without a password. If you did select a passphrase, you will need to activate the keys as follows:

# ssh-agent [SHELL]
# ssh-add -t [TIME]

In this case, "[SHELL]" is your preferred shell and "[TIME]" is the amount of time you'd like the key to be active in seconds. So, the following would start a bash shell with passwordless ssh active for 30 minutes:

# ssh-agent bash
# ssh-add -t 1800

You will be prompted for your passphrase and, when entered correctly, you will be able to ssh without entering a password.

To disable this functionality, simply delete your private key file ('''~/.ssh/id_dsa''') and remove the public key from your '''~/.ssh/authorized_keys2''' file.

==Passwordless SSH with SSH Keys for TORQUE/MAUI Cluster==

To set up passwordless ssh for TORQUE/MAUI cluster, do the following.

#cd $HOME
#ssh-keygen -t dsa -N "" -f $HOME/.ssh/id_dsa
#cd .ssh
#touch authorized_keys2
#cat id_dsa.pub >> authorized_keys2
#chmod 640 authorized_keys2

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

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

SecureShell

2010-05-04T22:08:56Z

Xhe: /* Passwordless SSH with SSH Keys for TORQUE/MAUI Cluster */

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 RedHat Linux 3, 4, and 5, and Mac OS X, 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.

On Windows XP or Vista hosts there are no SFTP clients installed by default. Users can install either which will enable SSH and SFTP access.

* [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY]
* [http://ttssh2.sourceforge.jp/ ttssh2]

Alternatively, all users can use the UMIACS Intranet SFTP Web Applet located [https://intranet.umiacs.umd.edu/ssh/ here] without installing any additional software.

==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 RedHat Linux 3, 4, and 5, and Mac OS X, the following command from a terminal will connect a client computer to the UMIACS [[OpenLAB]] using X11 Forwarding.
# ssh '''-X''' bkirz@openlab.umiacs.umd.edu

'''Note:''' Mac users must have X11 installed in their systems for X11 forwarding to work. This can be checked by looking for X11.app in /Applications/Utilities. You can find the installer [http://www.apple.com/support/downloads/x11formacosx.html here].

Windows users can enable X11 forwarding on UMIACS desktops by using cygwin to ssh -X.
If you do not have Cygwin, you will need to forward X through Xming.
First, enable X forwarding on your secure ssh client. The option is under tunneling in the ssh client settings. This only has to be done once.

[[Image:sshXForward.jpg]]

Next, click save in the main ssh appication window to save this setting.

After this has been done, every time you want to use X forwarding, you need to make sure 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.

Note that the UMIACS Intranet SFTP Web Applet does ''not'' allow X11 Forwarding.

==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.

==Passwordless SSH with SSH Keys==

There are some situations where it is important to be able to ssh without entering a password. This is mostly required when working in clusters. This is done using ssh keys. Instead of authenticating with a password, ssh can use a pre-defined set of encryption keys to establish an authorized connection.
To setup passwordless ssh, do the following.

First, create an ssh key pair:

# ssh-keygen -t dsa

The command will prompt you for a passphrase. If you use a password, you will need to enter it at the beginning of your work session. This is preferable as it is more secure but may cause problems for some clustered work, such as TORQUE/PBS cluster. If you simply hit '''[enter]''', you will never be prompted for a password when ssh'ing which can lead to security problems.

This will produce two files, '''id_dsa''' and '''id_dsa.pub''', the private and public keys respectively. Once you've created the keys, you will need to put them into place as follows:

# mkdir ~/.ssh
# chmod 700 ~/.ssh
# mv id_dsa ~/.ssh
# chmod 600 ~/.ssh/id_dsa
# touch ~/.ssh/authorized_keys2
# chmod 600 ~/.ssh/authorized_keys2
# cat id_dsa.pub >> authorized_keys2
# rm id_dsa.pub

It is '''very''' important that you keep your private key secure! Ensure that it is chmod'd to 600 and that you do not put it anywhere visible to other users!

If you did not select a passphrase when you generated your keys, you can now ssh without a password. If you did select a passphrase, you will need to activate the keys as follows:

# ssh-agent [SHELL]
# ssh-add -t [TIME]

In this case, "[SHELL]" is your preferred shell and "[TIME]" is the amount of time you'd like the key to be active in seconds. So, the following would start a bash shell with passwordless ssh active for 30 minutes:

# ssh-agent bash
# ssh-add -t 1800

You will be prompted for your passphrase and, when entered correctly, you will be able to ssh without entering a password.

To disable this functionality, simply delete your private key file ('''~/.ssh/id_dsa''') and remove the public key from your '''~/.ssh/authorized_keys2''' file.

==Passwordless SSH with SSH Keys for TORQUE/MAUI Cluster==

To set up passwordless ssh for TORQUE/PBS cluster, do the following.

#cd $HOME
#ssh-keygen -t dsa -N "" -f $HOME/.ssh/id_dsa
#cd .ssh
#touch authorized_keys2
#cat id_dsa.pub >> authorized_keys2
#chmod 640 authorized_keys2

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

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

SecureShell

2010-05-04T22:07:59Z

Xhe: /* Passwordless SSH with SSH Keys for TORQUE/MAUI Cluster */

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 RedHat Linux 3, 4, and 5, and Mac OS X, 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.

On Windows XP or Vista hosts there are no SFTP clients installed by default. Users can install either which will enable SSH and SFTP access.

* [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY]
* [http://ttssh2.sourceforge.jp/ ttssh2]

Alternatively, all users can use the UMIACS Intranet SFTP Web Applet located [https://intranet.umiacs.umd.edu/ssh/ here] without installing any additional software.

==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 RedHat Linux 3, 4, and 5, and Mac OS X, the following command from a terminal will connect a client computer to the UMIACS [[OpenLAB]] using X11 Forwarding.
# ssh '''-X''' bkirz@openlab.umiacs.umd.edu

'''Note:''' Mac users must have X11 installed in their systems for X11 forwarding to work. This can be checked by looking for X11.app in /Applications/Utilities. You can find the installer [http://www.apple.com/support/downloads/x11formacosx.html here].

Windows users can enable X11 forwarding on UMIACS desktops by using cygwin to ssh -X.
If you do not have Cygwin, you will need to forward X through Xming.
First, enable X forwarding on your secure ssh client. The option is under tunneling in the ssh client settings. This only has to be done once.

[[Image:sshXForward.jpg]]

Next, click save in the main ssh appication window to save this setting.

After this has been done, every time you want to use X forwarding, you need to make sure 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.

Note that the UMIACS Intranet SFTP Web Applet does ''not'' allow X11 Forwarding.

==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.

==Passwordless SSH with SSH Keys==

There are some situations where it is important to be able to ssh without entering a password. This is mostly required when working in clusters. This is done using ssh keys. Instead of authenticating with a password, ssh can use a pre-defined set of encryption keys to establish an authorized connection.
To setup passwordless ssh, do the following.

First, create an ssh key pair:

# ssh-keygen -t dsa

The command will prompt you for a passphrase. If you use a password, you will need to enter it at the beginning of your work session. This is preferable as it is more secure but may cause problems for some clustered work, such as TORQUE/PBS cluster. If you simply hit '''[enter]''', you will never be prompted for a password when ssh'ing which can lead to security problems.

This will produce two files, '''id_dsa''' and '''id_dsa.pub''', the private and public keys respectively. Once you've created the keys, you will need to put them into place as follows:

# mkdir ~/.ssh
# chmod 700 ~/.ssh
# mv id_dsa ~/.ssh
# chmod 600 ~/.ssh/id_dsa
# touch ~/.ssh/authorized_keys2
# chmod 600 ~/.ssh/authorized_keys2
# cat id_dsa.pub >> authorized_keys2
# rm id_dsa.pub

It is '''very''' important that you keep your private key secure! Ensure that it is chmod'd to 600 and that you do not put it anywhere visible to other users!

If you did not select a passphrase when you generated your keys, you can now ssh without a password. If you did select a passphrase, you will need to activate the keys as follows:

# ssh-agent [SHELL]
# ssh-add -t [TIME]

In this case, "[SHELL]" is your preferred shell and "[TIME]" is the amount of time you'd like the key to be active in seconds. So, the following would start a bash shell with passwordless ssh active for 30 minutes:

# ssh-agent bash
# ssh-add -t 1800

You will be prompted for your passphrase and, when entered correctly, you will be able to ssh without entering a password.

To disable this functionality, simply delete your private key file ('''~/.ssh/id_dsa''') and remove the public key from your '''~/.ssh/authorized_keys2''' file.

==Passwordless SSH with SSH Keys for TORQUE/MAUI Cluster==

To set up passwordless ssh for TORQUE/PBS cluster, do the following.

cd $HOME
ssh-keygen -t dsa -N "" -f $HOME/.ssh/id_dsa
cd .ssh
touch authorized_keys2
cat id_dsa.pub >> authorized_keys2
chmod 640 authorized_keys2

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

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

SecureShell

2010-05-04T22:07:45Z

Xhe: /* Passwordless SSH with SSH Keys */

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 RedHat Linux 3, 4, and 5, and Mac OS X, 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.

On Windows XP or Vista hosts there are no SFTP clients installed by default. Users can install either which will enable SSH and SFTP access.

* [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY]
* [http://ttssh2.sourceforge.jp/ ttssh2]

Alternatively, all users can use the UMIACS Intranet SFTP Web Applet located [https://intranet.umiacs.umd.edu/ssh/ here] without installing any additional software.

==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 RedHat Linux 3, 4, and 5, and Mac OS X, the following command from a terminal will connect a client computer to the UMIACS [[OpenLAB]] using X11 Forwarding.
# ssh '''-X''' bkirz@openlab.umiacs.umd.edu

'''Note:''' Mac users must have X11 installed in their systems for X11 forwarding to work. This can be checked by looking for X11.app in /Applications/Utilities. You can find the installer [http://www.apple.com/support/downloads/x11formacosx.html here].

Windows users can enable X11 forwarding on UMIACS desktops by using cygwin to ssh -X.
If you do not have Cygwin, you will need to forward X through Xming.
First, enable X forwarding on your secure ssh client. The option is under tunneling in the ssh client settings. This only has to be done once.

[[Image:sshXForward.jpg]]

Next, click save in the main ssh appication window to save this setting.

After this has been done, every time you want to use X forwarding, you need to make sure 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.

Note that the UMIACS Intranet SFTP Web Applet does ''not'' allow X11 Forwarding.

==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.

==Passwordless SSH with SSH Keys==

There are some situations where it is important to be able to ssh without entering a password. This is mostly required when working in clusters. This is done using ssh keys. Instead of authenticating with a password, ssh can use a pre-defined set of encryption keys to establish an authorized connection.
To setup passwordless ssh, do the following.

First, create an ssh key pair:

# ssh-keygen -t dsa

The command will prompt you for a passphrase. If you use a password, you will need to enter it at the beginning of your work session. This is preferable as it is more secure but may cause problems for some clustered work, such as TORQUE/PBS cluster. If you simply hit '''[enter]''', you will never be prompted for a password when ssh'ing which can lead to security problems.

This will produce two files, '''id_dsa''' and '''id_dsa.pub''', the private and public keys respectively. Once you've created the keys, you will need to put them into place as follows:

# mkdir ~/.ssh
# chmod 700 ~/.ssh
# mv id_dsa ~/.ssh
# chmod 600 ~/.ssh/id_dsa
# touch ~/.ssh/authorized_keys2
# chmod 600 ~/.ssh/authorized_keys2
# cat id_dsa.pub >> authorized_keys2
# rm id_dsa.pub

It is '''very''' important that you keep your private key secure! Ensure that it is chmod'd to 600 and that you do not put it anywhere visible to other users!

If you did not select a passphrase when you generated your keys, you can now ssh without a password. If you did select a passphrase, you will need to activate the keys as follows:

# ssh-agent [SHELL]
# ssh-add -t [TIME]

In this case, "[SHELL]" is your preferred shell and "[TIME]" is the amount of time you'd like the key to be active in seconds. So, the following would start a bash shell with passwordless ssh active for 30 minutes:

# ssh-agent bash
# ssh-add -t 1800

You will be prompted for your passphrase and, when entered correctly, you will be able to ssh without entering a password.

To disable this functionality, simply delete your private key file ('''~/.ssh/id_dsa''') and remove the public key from your '''~/.ssh/authorized_keys2''' file.

==Passwordless SSH with SSH Keys for TORQUE/MAUI Cluster==

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

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

SecureShell

2010-05-04T22:07:04Z

Xhe: /* Passwordless SSH with SSH Keys */

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 RedHat Linux 3, 4, and 5, and Mac OS X, 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.

On Windows XP or Vista hosts there are no SFTP clients installed by default. Users can install either which will enable SSH and SFTP access.

* [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY]
* [http://ttssh2.sourceforge.jp/ ttssh2]

Alternatively, all users can use the UMIACS Intranet SFTP Web Applet located [https://intranet.umiacs.umd.edu/ssh/ here] without installing any additional software.

==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 RedHat Linux 3, 4, and 5, and Mac OS X, the following command from a terminal will connect a client computer to the UMIACS [[OpenLAB]] using X11 Forwarding.
# ssh '''-X''' bkirz@openlab.umiacs.umd.edu

'''Note:''' Mac users must have X11 installed in their systems for X11 forwarding to work. This can be checked by looking for X11.app in /Applications/Utilities. You can find the installer [http://www.apple.com/support/downloads/x11formacosx.html here].

Windows users can enable X11 forwarding on UMIACS desktops by using cygwin to ssh -X.
If you do not have Cygwin, you will need to forward X through Xming.
First, enable X forwarding on your secure ssh client. The option is under tunneling in the ssh client settings. This only has to be done once.

[[Image:sshXForward.jpg]]

Next, click save in the main ssh appication window to save this setting.

After this has been done, every time you want to use X forwarding, you need to make sure 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.

Note that the UMIACS Intranet SFTP Web Applet does ''not'' allow X11 Forwarding.

==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.

==Passwordless SSH with SSH Keys==

There are some situations where it is important to be able to ssh without entering a password. This is mostly required when working in clusters. This is done using ssh keys. Instead of authenticating with a password, ssh can use a pre-defined set of encryption keys to establish an authorized connection. To set up passwordless ssh for TORQUE/PBS cluster, do the following.

cd $HOME
ssh-keygen -t dsa -N "" -f $HOME/.ssh/id_dsa
cd .ssh
touch authorized_keys2
cat id_dsa.pub >> authorized_keys2
chmod 640 authorized_keys2

To setup passwordless ssh, do the following.

First, create an ssh key pair:

# ssh-keygen -t dsa

The command will prompt you for a passphrase. If you use a password, you will need to enter it at the beginning of your work session. This is preferable as it is more secure but may cause problems for some clustered work, such as TORQUE/PBS cluster. If you simply hit '''[enter]''', you will never be prompted for a password when ssh'ing which can lead to security problems.

This will produce two files, '''id_dsa''' and '''id_dsa.pub''', the private and public keys respectively. Once you've created the keys, you will need to put them into place as follows:

# mkdir ~/.ssh
# chmod 700 ~/.ssh
# mv id_dsa ~/.ssh
# chmod 600 ~/.ssh/id_dsa
# touch ~/.ssh/authorized_keys2
# chmod 600 ~/.ssh/authorized_keys2
# cat id_dsa.pub >> authorized_keys2
# rm id_dsa.pub

It is '''very''' important that you keep your private key secure! Ensure that it is chmod'd to 600 and that you do not put it anywhere visible to other users!

If you did not select a passphrase when you generated your keys, you can now ssh without a password. If you did select a passphrase, you will need to activate the keys as follows:

# ssh-agent [SHELL]
# ssh-add -t [TIME]

In this case, "[SHELL]" is your preferred shell and "[TIME]" is the amount of time you'd like the key to be active in seconds. So, the following would start a bash shell with passwordless ssh active for 30 minutes:

# ssh-agent bash
# ssh-add -t 1800

You will be prompted for your passphrase and, when entered correctly, you will be able to ssh without entering a password.

To disable this functionality, simply delete your private key file ('''~/.ssh/id_dsa''') and remove the public key from your '''~/.ssh/authorized_keys2''' file.

==Passwordless SSH with SSH Keys for TORQUE/MAUI Cluster==

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

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

SecureShell

2010-05-04T21:39:35Z

Xhe: /* Passwordless SSH with SSH Keys */

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 RedHat Linux 3, 4, and 5, and Mac OS X, 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.

On Windows XP or Vista hosts there are no SFTP clients installed by default. Users can install either which will enable SSH and SFTP access.

* [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY]
* [http://ttssh2.sourceforge.jp/ ttssh2]

Alternatively, all users can use the UMIACS Intranet SFTP Web Applet located [https://intranet.umiacs.umd.edu/ssh/ here] without installing any additional software.

==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 RedHat Linux 3, 4, and 5, and Mac OS X, the following command from a terminal will connect a client computer to the UMIACS [[OpenLAB]] using X11 Forwarding.
# ssh '''-X''' bkirz@openlab.umiacs.umd.edu

'''Note:''' Mac users must have X11 installed in their systems for X11 forwarding to work. This can be checked by looking for X11.app in /Applications/Utilities. You can find the installer [http://www.apple.com/support/downloads/x11formacosx.html here].

Windows users can enable X11 forwarding on UMIACS desktops by using cygwin to ssh -X.
If you do not have Cygwin, you will need to forward X through Xming.
First, enable X forwarding on your secure ssh client. The option is under tunneling in the ssh client settings. This only has to be done once.

[[Image:sshXForward.jpg]]

Next, click save in the main ssh appication window to save this setting.

After this has been done, every time you want to use X forwarding, you need to make sure 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.

Note that the UMIACS Intranet SFTP Web Applet does ''not'' allow X11 Forwarding.

==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.

==Passwordless SSH with SSH Keys==

There are some situations where it is important to be able to ssh without entering a password. This is mostly required when working in clusters. This is done using ssh keys. Instead of authenticating with a password, ssh can use a pre-defined set of encryption keys to establish an authorized connection. To set up passwordless ssh for TORQUE/PBS cluster, do the following.

cd $HOME
ssh-keygen -t dsa -N "" -f $HOME/.ssh/id_dsa
cd .ssh
touch authorized_keys2
cat id_dsa.pub >> authorized_keys2
chmod 640 authorized_keys2

To setup passwordless ssh, do the following.

First, create an ssh key pair:

# ssh-keygen -t dsa

The command will prompt you for a passphrase. If you use a password, you will need to enter it at the beginning of your work session. This is preferable as it is more secure but may cause problems for some clustered work, such as TORQUE/PBS cluster. If you simply hit '''[enter]''', you will never be prompted for a password when ssh'ing which can lead to security problems.

This will produce two files, '''id_dsa''' and '''id_dsa.pub''', the private and public keys respectively. Once you've created the keys, you will need to put them into place as follows:

# mkdir ~/.ssh
# chmod 700 ~/.ssh
# mv id_dsa ~/.ssh
# chmod 600 ~/.ssh/id_dsa
# touch ~/.ssh/authorized_keys2
# chmod 600 ~/.ssh/authorized_keys2
# cat id_dsa.pub >> authorized_keys2
# rm id_dsa.pub

It is '''very''' important that you keep your private key secure! Ensure that it is chmod'd to 600 and that you do not put it anywhere visible to other users!

If you did not select a passphrase when you generated your keys, you can now ssh without a password. If you did select a passphrase, you will need to activate the keys as follows:

# ssh-agent [SHELL]
# ssh-add -t [TIME]

In this case, "[SHELL]" is your preferred shell and "[TIME]" is the amount of time you'd like the key to be active in seconds. So, the following would start a bash shell with passwordless ssh active for 30 minutes:

# ssh-agent bash
# ssh-add -t 1800

You will be prompted for your passphrase and, when entered correctly, you will be able to ssh without entering a password.

To disable this functionality, simply delete your private key file ('''~/.ssh/id_dsa''') and remove the public key from your '''~/.ssh/authorized_keys2''' file.

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

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

SecureShell

2010-05-04T21:36:29Z

Xhe: /* Passwordless SSH with SSH Keys */

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 RedHat Linux 3, 4, and 5, and Mac OS X, 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.

On Windows XP or Vista hosts there are no SFTP clients installed by default. Users can install either which will enable SSH and SFTP access.

* [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY]
* [http://ttssh2.sourceforge.jp/ ttssh2]

Alternatively, all users can use the UMIACS Intranet SFTP Web Applet located [https://intranet.umiacs.umd.edu/ssh/ here] without installing any additional software.

==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 RedHat Linux 3, 4, and 5, and Mac OS X, the following command from a terminal will connect a client computer to the UMIACS [[OpenLAB]] using X11 Forwarding.
# ssh '''-X''' bkirz@openlab.umiacs.umd.edu

'''Note:''' Mac users must have X11 installed in their systems for X11 forwarding to work. This can be checked by looking for X11.app in /Applications/Utilities. You can find the installer [http://www.apple.com/support/downloads/x11formacosx.html here].

Windows users can enable X11 forwarding on UMIACS desktops by using cygwin to ssh -X.
If you do not have Cygwin, you will need to forward X through Xming.
First, enable X forwarding on your secure ssh client. The option is under tunneling in the ssh client settings. This only has to be done once.

[[Image:sshXForward.jpg]]

Next, click save in the main ssh appication window to save this setting.

After this has been done, every time you want to use X forwarding, you need to make sure 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.

Note that the UMIACS Intranet SFTP Web Applet does ''not'' allow X11 Forwarding.

==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.

==Passwordless SSH with SSH Keys==

There are some situations where it is important to be able to ssh without entering a password. This is mostly required when working in clusters. This is done using ssh keys. Instead of authenticating with a password, ssh can use a pre-defined set of encryption keys to establish an authorized connection. To setup passwordless ssh, do the following.

First, create an ssh key pair:

# ssh-keygen -t dsa

The command will prompt you for a passphrase. If you use a password, you will need to enter it at the beginning of your work session. This is preferable as it is more secure but may cause problems for some clustered work, such as TORQUE/PBS cluster. If you simply hit '''[enter]''', you will never be prompted for a password when ssh'ing which can lead to security problems.

This will produce two files, '''id_dsa''' and '''id_dsa.pub''', the private and public keys respectively. Once you've created the keys, you will need to put them into place as follows:

# mkdir ~/.ssh
# chmod 700 ~/.ssh
# mv id_dsa ~/.ssh
# chmod 600 ~/.ssh/id_dsa
# touch ~/.ssh/authorized_keys2
# chmod 600 ~/.ssh/authorized_keys2
# cat id_dsa.pub >> authorized_keys2
# rm id_dsa.pub

It is '''very''' important that you keep your private key secure! Ensure that it is chmod'd to 600 and that you do not put it anywhere visible to other users!

If you did not select a passphrase when you generated your keys, you can now ssh without a password. If you did select a passphrase, you will need to activate the keys as follows:

# ssh-agent [SHELL]
# ssh-add -t [TIME]

In this case, "[SHELL]" is your preferred shell and "[TIME]" is the amount of time you'd like the key to be active in seconds. So, the following would start a bash shell with passwordless ssh active for 30 minutes:

# ssh-agent bash
# ssh-add -t 1800

You will be prompted for your passphrase and, when entered correctly, you will be able to ssh without entering a password.

To disable this functionality, simply delete your private key file ('''~/.ssh/id_dsa''') and remove the public key from your '''~/.ssh/authorized_keys2''' file.

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

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

Main Page

2010-03-12T16:46:09Z

Xhe: /* ONStor Upgrade Mon March 1st 2010 8pm-12am */

Main Page

2010-03-12T16:45:23Z

Xhe: /* UMIACS NFS Problems */

__NOTOC__
==Anouncements==
<startFeed />
===UMIACS Help Desk Closed During Spring Break===
The UMIACS Help Desk will be closed from Monday the 15th to Thursday 18th along with the rest of the University. We will be opening back up on Friday the 19th.

===CLIP File System Downtime, March 8===

Monday 
March 8 
10am 

corpora 
gale2 
trec 
chinese_parsing 
spinn3r 
lm 
galep3eval 
clueweb 
mei 
wwwtides 
www 

==CBCB Opteron Upgrades==
the following hosts will be unavailable due to an OS upgrade from RHEL4->RHEL5.

beech and larch: Tuesday, March 9th at 10am -->Complete

sycamore and hemlock: Friday, March 12th at 10am

and after spring break --

privet and bayberry: Tuesday, March 23rd at 10am

please note that apart from the nodes being down, the /tmp directories will also be deleted.

===ONStor Upgrade Mon March 1st 2010 8pm-12am===
Staff will be upgrading the last of our 2 ONStor clusters which provide NFS and CIFS file service to many of our labs and centers. Because they are clustered and highly available we expect to be able to upgrade the cluster without any downtime. There may be however some short hiccups when we fail servers over they should just show up as delays in file service. The following are the virtual servers that will be affected by this upgrade:

* umiacsfs02 (nfshomes)
* umiacsfs01 (legacyfs file systems)
* umiacsfs00 (/usr/local and /opt file systems)
* umiacs-webftp (ftp and web trees)
* clampfs00
* lccdfs00

If you have any questions please email [mailto:staff@umiacs.umd.edu staff@umiacs.umd.edu]

<endFeed />

'''Please see our [[HelpDesk]] for additional support.'''

==Technical Reference==

Welcome to UMIACS Wiki. This is the main place to find documentation and information about your account and the technical services that UMIACS offers. If this is your first time please start here [[GettingStarted| Getting Started]].

We provide many [[CoreServices|Core Services]] which include [[EMail]], [[Backups]] and [[VPN]].

We have lots of specific [[LabFacilities|Lab Facilities]] that you may be interested in.

Please check here if you are interested in [[OrderingEquipment|Ordering Equipment]].

Main Page

2010-02-02T18:04:20Z

Xhe: /* Openlab Cluster TORQUE/MAUI upgrade */

__NOTOC__
==Anouncements==
<startFeed />
===Openlab Cluster TORQUE/MAUI upgrade===

openlab TORQUE/MAUI system will be down from 12:30 - 2:30pm on Tuesday, 2/2/2010 for the upgrading. We will upgrade TORUQE/MAUI to our latest version.

===CLIP File System Downtime===

Monday 
Feburary 1 
10:00am

enron2 
mono-para 
nsf-cri-ii 
liwc 

<endFeed />

'''Please see our [[HelpDesk]] for additional support.'''

==Technical Reference==

Welcome to UMIACS Wiki. This is the main place to find documentation and information about your account and the technical services that UMIACS offers. If this is your first time please start here [[GettingStarted| Getting Started]].

We provide many [[CoreServices|Core Services]] which include [[EMail]], [[Backups]] and [[VPN]].

We have lots of specific [[LabFacilities|Lab Facilities]] that you may be interested in.

Please check here if you are interested in [[OrderingEquipment|Ordering Equipment]].

Main Page

2010-02-02T18:04:09Z

Xhe: /* Anouncements */

__NOTOC__
==Anouncements==
<startFeed />
===Openlab Cluster TORQUE/MAUI upgrade===

openlab TORQUE/MAUI system will down from 12:30 - 2:30pm on Tuesday, 2/2/2010 for the upgrading. We will upgrade TORUQE/MAUI to our latest version.

===CLIP File System Downtime===

Monday 
Feburary 1 
10:00am

enron2 
mono-para 
nsf-cri-ii 
liwc 

<endFeed />

'''Please see our [[HelpDesk]] for additional support.'''

==Technical Reference==

Welcome to UMIACS Wiki. This is the main place to find documentation and information about your account and the technical services that UMIACS offers. If this is your first time please start here [[GettingStarted| Getting Started]].

We provide many [[CoreServices|Core Services]] which include [[EMail]], [[Backups]] and [[VPN]].

We have lots of specific [[LabFacilities|Lab Facilities]] that you may be interested in.

Please check here if you are interested in [[OrderingEquipment|Ordering Equipment]].

Main Page

2010-01-27T02:57:05Z

Xhe:

__NOTOC__
==Anouncements==
<startFeed />
<endFeed />

'''Please see our [[HelpDesk]] for additional support.'''

==Technical Reference==

Welcome to UMIACS Wiki. This is the main place to find documentation and information about your account and the technical services that UMIACS offers. If this is your first time please start here [[GettingStarted| Getting Started]].

We provide many [[CoreServices|Core Services]] which include [[EMail]], [[Backups]] and [[VPN]].

We have lots of specific [[LabFacilities|Lab Facilities]] that you may be interested in.

Please check here if you are interested in [[OrderingEquipment|Ordering Equipment]].

Main Page

2010-01-27T02:56:52Z

Xhe:

__NOTOC__
==Anouncements==
<startFeed />
<endFeed />

'''Please see our [[HelpDesk]] for additional support.'''

==Technical Reference==

Welcome to UMIACS Wiki. This is the main place to find documentation and information about your account and the technical services that UMIACS offers. If this is your first time please start here [[GettingStarted| Getting Started]].

We provide many more [[CoreServices|Core Services]] which include [[EMail]], [[Backups]] and [[VPN]].

We have lots of specific [[LabFacilities|Lab Facilities]] that you may be interested in.

Please check here if you are interested in [[OrderingEquipment|Ordering Equipment]].

Main Page

2010-01-27T02:56:33Z

Xhe:

HPC

2010-01-26T15:53:04Z

Xhe:

* [[ClusterGuide|Torque/Maui Cluster Guide]]
* [[ CondorGuide | Condor Guide]]

HPC

2010-01-13T17:03:22Z

Xhe:

* [[ClusterGuide|Torque/Maui Cluster Guide]]
* [[ Condor | Condor Guide]]

HPC

2010-01-13T17:02:35Z

Xhe:

* [[ClusterGuide|Torque/Maui Cluster Guide]]
* [[ | Condor Guide]]

Main Page

2010-01-13T15:02:57Z

Xhe: /* Openlab cluster maintenance */

__NOTOC__
==Anouncements==
<startFeed />
===Openlab cluster maintenance===

Openlab cluster is scheduled to have maintenance from 2:00pm - 3:30pm on Wednesday 1/13/2010. During the time, the cluster may not available all the time.

===CLIP File System Downtime===

Tuesday 
January 19 
10:00am

ace2 
trecindex 
malach-ldc 
spinn3r 
weps 
galep3eval 
hsd 
enron-corpus 

===Do not turn off supported computers over break ===
Recently Someone from FM sent a message to the campus community encouraging people to turn off their computers before leaving for the Holiday Break.

However The UMIACS Technical staff would like to request that you not do so
that your computers can continue to get backed up, get updates and receive
the latest virus protections.

If you have any questions or concerns about this, please send mail to the
technical staff (staff@umiacs.umd.edu).

<endFeed />

'''Please see our [[HelpDesk]] for additional support.'''

==Technical Reference==

Welcome to UMIACS Wiki. This is the main place to find documentation and information about your account and the technical services that UMIACS offers. If this is your first time please start here [[GettingStarted| Getting Started]].

We provide many [[CoreServices|Core Services]] which include [[EMail]], [[Backups]] and [[VPN]].

We have lots of specific [[LabFacilities|Lab Facilities]] that you may be interested in.

Please check here if you are interested in [[OrderingEquipment|Ordering Equipment]].

Main Page

2010-01-13T14:59:51Z

Xhe: /* Anouncements */

__NOTOC__
==Anouncements==
<startFeed />
===Openlab cluster maintenance===

Openlab cluster is scheduled to have maintenance from 10:00am - 2:00pm on Wednesday 1/13/2010. During the time, the cluster may not available all the time.

===CLIP File System Downtime===

Tuesday 
January 19 
10:00am

ace2 
trecindex 
malach-ldc 
spinn3r 
weps 
galep3eval 
hsd 
enron-corpus 

===Do not turn off supported computers over break ===
Recently Someone from FM sent a message to the campus community encouraging people to turn off their computers before leaving for the Holiday Break.

However The UMIACS Technical staff would like to request that you not do so
that your computers can continue to get backed up, get updates and receive
the latest virus protections.

If you have any questions or concerns about this, please send mail to the
technical staff (staff@umiacs.umd.edu).

<endFeed />

'''Please see our [[HelpDesk]] for additional support.'''

==Technical Reference==

Welcome to UMIACS Wiki. This is the main place to find documentation and information about your account and the technical services that UMIACS offers. If this is your first time please start here [[GettingStarted| Getting Started]].

We provide many [[CoreServices|Core Services]] which include [[EMail]], [[Backups]] and [[VPN]].

We have lots of specific [[LabFacilities|Lab Facilities]] that you may be interested in.

Please check here if you are interested in [[OrderingEquipment|Ordering Equipment]].

Main Page

2009-11-07T03:00:15Z

Xhe: /* Anouncements */

__NOTOC__
==Anouncements==
<startFeed />
For the next two weeks, we would like to schedule UMIACS condor service down time to migrate UMIACS
condor system to the latest stable version, upgrade condor server to newer Operating system
with the latest condor version. This will be implemented in stages for different clusters and
lab machines.

Here is the planed schedule for the migration:

Monday 11/9, we will migrate condor on openlab machines, openlab cluster.
Tuesday 11/10, migrate condor on rdec cluster
Wednesday 11/11, migrate condor system on lccd cluster,
Friday, 11/13, migrate condor on wren cluster
Monday 11/16, gene cluster
Tuesday, 11/17, lab machines: nara, bio, clip
Wednesday, 11/18, condor server migration. During server migration, we will setup
a backup server for condor pool, so users can still submit jobs to condor pool.

Please note that the scheduled machines will be out of condor pool during the migration.

If the schedule causes any problems, please let us know.
<endFeed />

'''Please see our [[HelpDesk]] for additional support.'''

==Technical Reference==

Welcome to UMIACS Wiki. This is the main place to find documentation and information about your account and the technical services that UMIACS offers. If this is your first time please start here [[GettingStarted| Getting Started]].

We provide many [[CoreServices|Core Services]] which include [[EMail]], [[Backups]] and [[VPN]].

We have lots of specific [[LabFacilities|Lab Facilities]] that you may be interested in.

Please check here if you are interested in [[OrderingEquipment|Ordering Equipment]].

Main Page

2009-11-07T02:41:46Z

Xhe: /* Anouncements */

__NOTOC__
==Anouncements==
<startFeed />
For the next two weeks, we would like to schedule UMIACS condor service down time to migrate UMIACS
condor system to the latest stable version, upgrade condor server to newer Operating system
with the latest condor version. This will be implenmented in stages for different clusters and
lab machines.

Here is the planed schedule for the migration:

Monday 11/9, we will migrate condor on openlab machines, openlab cluster.
Tuesday 11/10, migrate condor on rdec cluster
Wednesday 11/11, migrate condor system on lccd cluster,
Friday, 11/13, migrate condor on wren cluster
Monday 11/16, gene cluster
Tuesday, 11/17, lab machines: nara, bio, clip
Wednesday, 11/18, condor server migration. During server migration, we will setup
a backup server for condor pool, so users can still submit jobs to condor pool.

Please note that the scheduled machines will be out of condor pool during the migration.

If the schedule causes any problems, please let us know.
<endFeed />

'''Please see our [[HelpDesk]] for additional support.'''

==Technical Reference==

Welcome to UMIACS Wiki. This is the main place to find documentation and information about your account and the technical services that UMIACS offers. If this is your first time please start here [[GettingStarted| Getting Started]].

We provide many [[CoreServices|Core Services]] which include [[EMail]], [[Backups]] and [[VPN]].

We have lots of specific [[LabFacilities|Lab Facilities]] that you may be interested in.

Please check here if you are interested in [[OrderingEquipment|Ordering Equipment]].

Main Page

2009-11-07T02:41:22Z

Xhe: /* Anouncements */

__NOTOC__
==Anouncements==
<startFeed />
For the next two weeks, we would like to schedule UMIACS condor service down time to migrate UMIACS
condor system to the latest stable version, upgrade condor server to newer Operating system
with the latest condor version. This will be implenmented in stages for different clusters and
lab machines.

Here is the planed schedule for the migration:

Monday 11/9, we will migrate condor on openlab machines, openlab cluster.
Tuesday 11/10, migrate condor on rdec cluster
Wednesday 11/11, migrate condor system on lccd cluster,
Friday, 11/13, migrate condor on wren cluster
Monday 11/16, gene cluster
Tuesday, 11/17, lab machines: nara, bio, clip
Wednesday, 11/18, condor server migration. During server migration, we will setup a backup server for
condor pool, so users can still submit jobs to condor pool.

Please note that the scheduled machines will be out of condor pool during the migration.

If the schedule causes any problems, please let us know.
<endFeed />

'''Please see our [[HelpDesk]] for additional support.'''

==Technical Reference==

Welcome to UMIACS Wiki. This is the main place to find documentation and information about your account and the technical services that UMIACS offers. If this is your first time please start here [[GettingStarted| Getting Started]].

We provide many [[CoreServices|Core Services]] which include [[EMail]], [[Backups]] and [[VPN]].

We have lots of specific [[LabFacilities|Lab Facilities]] that you may be interested in.

Please check here if you are interested in [[OrderingEquipment|Ordering Equipment]].

Main Page

2009-11-07T02:40:43Z

Xhe: /* Anouncements */

__NOTOC__
==Anouncements==
<startFeed />
For the next two weeks, we would like to schedule UMIACS condor service down time to migrate UMIACS
condor system to the latest stable version, upgrade condor server to newer Operating system
with the latest condor version. This will be implenmented in stages for different clusters and
lab machines.

Here is the planed schedule for the migration:

Monday 11/9, we will migrate condor on openlab machines, openlab cluster.
Tuesday 11/10, migrate condor on rdec cluster
Wednesday 11/11, migrate condor system on lccd cluster,
Friday, 11/13, migrate condor on wren cluster
Monday 11/16, gene cluster
Tuesday, 11/17, lab machines: nara, bio, clip
Wednesday, 11/18, condor server migration. During server migration, we will setup a backup server for condor pool, so users can still submit jobs to condor pool.

Please note that the scheduled machines will be out of condor pool during the migration.

If the schedule causes any problems, please let us know.
<endFeed />

'''Please see our [[HelpDesk]] for additional support.'''

==Technical Reference==

Welcome to UMIACS Wiki. This is the main place to find documentation and information about your account and the technical services that UMIACS offers. If this is your first time please start here [[GettingStarted| Getting Started]].

We provide many [[CoreServices|Core Services]] which include [[EMail]], [[Backups]] and [[VPN]].

We have lots of specific [[LabFacilities|Lab Facilities]] that you may be interested in.

Please check here if you are interested in [[OrderingEquipment|Ordering Equipment]].

LabFacilities

2009-09-11T01:36:46Z

Xhe:

* [[OpenLAB]]
* [[CBCB|Center for Bioinformatics and Computational Biology]] (CBCB) http://www.cbcb.umd.edu
* [[CDIG|Center for Digital International Government]] (CDIG) http://www.umiacs.umd.edu/research/CDIG
* [[CFAR|Center for Automation Research]] (CFAR) http://www.cfar.umd.edu
* [[CHESS|Center for Human Enhanced Secure Systems]] (CHESS) http://chess.umiacs.umd.edu/
* [[CLIP|Computational Linguistics and Information Processing]] (CLIP) http://www.umiacs.umd.edu/research/CLIP
* [[CVL|Computer Vision Laboratory]] (CVL) http://www.cfar.umd.edu/cvl/
* [[DSSL|Distributed Systems Software Laboratory]] (DSSL) http://www.cs.umd.edu/projects/dssl
* [[FCMD|Fraunhofer Center at Maryland]] (FCMD) http://fc-md.umd.edu/
* [[GLCF|Global Land Cover Facility]] (GLCF) http://www.glcf.umiacs.umd.edu
* [[GVIL|Graphics and Visual Informatics Laboratory]] (GVIL) http://www.cs.umd.edu/gvil/
* [[HCIL|Human Computer Interaction Laboratory]] (HCIL) http://www.cs.umd.edu/projects/hcil
* [[KECK|Keck Lab for the Comp. Modeling of Visual Movement]] (KECK) http://www.umiacs.umd.edu/%7Elsd/kecklab.html
* [[LAMP|Language and Media Processing Laboratory]] (LAMP) http://lamp.cfar.umd.edu
* [[LCCD|Laboratory for Computational Cultural Dynamics]] (LCCD) http://www.umiacs.umd.edu/research/LCCD/
* [[LPDC|Laboratory for Parallel and Distributed Computing]] (LPDC) http://www.umiacs.umd.edu/research/LPDC
* [[MIND|Maryland Information and Network Dynamics Lab]] (MIND) http://mindlab.umd.edu/
* [[PIRL|Perceptual Interfaces and Reality Laboratory]] (PIRL) http://pirl.umd.edu/

HPC

2009-09-11T01:29:26Z

Xhe:

* [[ClusterGuide|Torque/Maui Cluster Guide]]

HPC

2009-09-11T01:23:53Z

Xhe:

* [[ClusterGuide]] Torque/Maui Cluster Guide

CoreServices

2009-09-11T01:22:21Z

Xhe:

* [[Kerberos|Authentication (UMIACS KRB5/UNIX)]]

* [[ActiveDirectory|Authentication (Active Directory/Windows)]]

* [[EMail]]

* [[Printing]]

* [[MailingLists|Mailing Lists]]

* [[OSSupport|Operating Systems Support]]

* [[NAS|Network Attached Storage]]

* [[Web|Web Services]]

* [[FileTransferProtocol |File Transfer Protocol]]

* [[Subversion|Revision Control (Subversion)]]

* [[Programming|Programming Languages]]

* [[Backups]]

* [[VPN|Virtual Private Networking]]

* [[WinXPRemoteAssist|Windows XP Remote Assistance]]

* [[LocalDataStorage|Local Data Storage]]

* [[HPC|High Performance Computing]]

MailmanFAQ

2008-10-01T18:46:40Z

Xhe: /* How do I add users to a mailman mailing list? */

===Is there an easy way to discard all messages waiting to be reviewed?===

If you have a list where non members can post but their messages are moderated, you'll have to deal with a lot of spam. After sometime, just a small percentage of them will be good posts.

The admindb page has a checkbox that allows you to discard all held messages that are marked Defer. On heavy lists with lots of spam holds, this makes clearing them much faster.

To make sure that all mail from non-members is automatically deleted, go to the privacy page followed by the sender-filter sub-page. At the bottom of the page, set to "discard" the value for "Action to take for postings from non-members for which no explicit action is defined."

On the same page, at the top, you can do the same thing for postings by members (if your list is moderated such that users can't post)

===How do I turn off HTML messages/attachments?===

On the admin page, go to the Content Filtering section.

Change "Should Mailman filter ..." to Yes.

If you leave the rest at default values, including

Yes for "Should Mailman convert text/html parts to plain text?"

your list will only distribute plain text messages with no attachments.

===How can I post from 2 or more addresses to a "members-only" list?===

If you're subscribed to a members-only list as USER@umiacs.umd.edu and accidentally post as USER@cfar.umd.edu, your message will not go through.

The solution is to actually subscribe both addresses to the list, but to disable delivery from all but one of the addresses. So in the above example, I'd subscribe USER@umiacs.umd.edu and USER@Ccfar.umd.edu, but I would disable delivery to USER@cfar.umd.edu.

You can disable delivery to an address by going to the personal options page for that address and setting "Mail delivery" to "disabled".

The list manager can disable delivery to an address by going to the membership page and clicking "no mail" nect to the address in question.

===How do I change a member's password or send them their password?===

Go to the Membership-management page, click the address in question. The page that appears allows you to set a users password or mail them their existing password by clicking on

"Email my password to me"

Note all the other options you can set for the user here.

Don't forget that members can have their password sent to them anytime they like, by clicking the appropriate button on their personal page. There is no need for you to change their password if they forgettheir password. They just have to go to

http://lists.umiacs.umd.edu/mailman/options/LISTNAME/USERNAME%40DOMAINNAME

EG:

http://lists.umiacs.umd.edu/mailman/options/umiacs/johndoe%40umiacs.umd.edu

===How can I restrict the list so only authorized persons can post?===

Turn on the moderation flag for all your existing users. Go to the membership management page, and use the Additional Member Tasks to turn on the mod flag for all users.

Then go to Privacy Options -> Sender filters and set the default_member_moderation flag to Yes so that new users are automatically set as moderated.

Set the member_moderation_action to Reject and add a nice rejection notice text to the following text box.

Set the generic_nonmember_action to Reject or Discard.

===How can someone subscribe without my doing anything?===

They just need to go to

http://lists/mailman/listinfo/LISTNAME

and fill in the form. They can also subscribe/unsubscribe by email by sending to

LISTNAME-subscribe

or to unsubscribe,

LISTNAME-unsubscribe

In ALL of the above cases, the user will receive email confirming their action. They need to just reply to the mail for this to take affect.

===How do I unsubscribe users without them getting an unsubscribe message?===

By default, they will not get an unsubscribe message. You need only go to the membership page and click the "unsub" button next to each of their names and press "submit" or go to the Mass-removal subpage under Membership-management and add all the addresses into the window and click "submit".

===How do I edit a held message before approving it for the list?===

* Use the "forward this message" feature in the admindb page to forward the message to yourself.

* At the same time, discard the original held message. You may want to do this later, after you're sure the message was properly forwarded to you.

* Edit the message in your mail reader. You should include a notice in the message explaining that the list moderator has edited the message. Please use proper netiquette!

* Resend the message to the list using a Resent-To: header containing the list posting address. Also include an Approved: header containing
the list's admin password.

===How do I add users to a mailman mailing list?===

* Login to the mailman mailing list adminstration's page use your mailman admin password

http://mailman.umiacs.umd.edu/mailman/admin/MAILINGLISTNAME

* Click "Membership Management..." -> Choose "Mass Subscription"

* In the "Mass subscriptions" panel, enter user's address one address per line

* click "Submit Your Changes" button.

* You can verify it by choose "Membership List" under "Membership Management...", find the user's address.

* After completion, click "Logout"

MailmanFAQ

2008-10-01T18:46:08Z

Xhe: /* How do I add users to a mailman mailing list? */

MailmanFAQ

2008-10-01T18:43:51Z

Xhe:

MailmanFAQ

2008-10-01T18:43:14Z

Xhe: /* How do I add users to a mailman mailing list? */

===Is there an easy way to discard all messages waiting to be reviewed?===

If you have a list where non members can post but their messages are moderated, you'll have to deal with a lot of spam. After sometime, just a small percentage of them will be good posts.

The admindb page has a checkbox that allows you to discard all held messages that are marked Defer. On heavy lists with lots of spam holds, this makes clearing them much faster.

To make sure that all mail from non-members is automatically deleted, go to the privacy page followed by the sender-filter sub-page. At the bottom of the page, set to "discard" the value for "Action to take for postings from non-members for which no explicit action is defined."

On the same page, at the top, you can do the same thing for postings by members (if your list is moderated such that users can't post)

===How do I turn off HTML messages/attachments?===

On the admin page, go to the Content Filtering section.

Change "Should Mailman filter ..." to Yes.

If you leave the rest at default values, including

Yes for "Should Mailman convert text/html parts to plain text?"

your list will only distribute plain text messages with no attachments.

===How can I post from 2 or more addresses to a "members-only" list?===

If you're subscribed to a members-only list as USER@umiacs.umd.edu and accidentally post as USER@cfar.umd.edu, your message will not go through.

The solution is to actually subscribe both addresses to the list, but to disable delivery from all but one of the addresses. So in the above example, I'd subscribe USER@umiacs.umd.edu and USER@Ccfar.umd.edu, but I would disable delivery to USER@cfar.umd.edu.

You can disable delivery to an address by going to the personal options page for that address and setting "Mail delivery" to "disabled".

The list manager can disable delivery to an address by going to the membership page and clicking "no mail" nect to the address in question.

===How do I change a member's password or send them their password?===

Go to the Membership-management page, click the address in question. The page that appears allows you to set a users password or mail them their existing password by clicking on

"Email my password to me"

Note all the other options you can set for the user here.

Don't forget that members can have their password sent to them anytime they like, by clicking the appropriate button on their personal page. There is no need for you to change their password if they forgettheir password. They just have to go to

http://lists.umiacs.umd.edu/mailman/options/LISTNAME/USERNAME%40DOMAINNAME

EG:

http://lists.umiacs.umd.edu/mailman/options/umiacs/johndoe%40umiacs.umd.edu

===How can I restrict the list so only authorized persons can post?===

Turn on the moderation flag for all your existing users. Go to the membership management page, and use the Additional Member Tasks to turn on the mod flag for all users.

Then go to Privacy Options -> Sender filters and set the default_member_moderation flag to Yes so that new users are automatically set as moderated.

Set the member_moderation_action to Reject and add a nice rejection notice text to the following text box.

Set the generic_nonmember_action to Reject or Discard.

===How can someone subscribe without my doing anything?===

They just need to go to

http://lists/mailman/listinfo/LISTNAME

and fill in the form. They can also subscribe/unsubscribe by email by sending to

LISTNAME-subscribe

or to unsubscribe,

LISTNAME-unsubscribe

In ALL of the above cases, the user will receive email confirming their action. They need to just reply to the mail for this to take affect.

===How do I unsubscribe users without them getting an unsubscribe message?===

By default, they will not get an unsubscribe message. You need only go to the membership page and click the "unsub" button next to each of their names and press "submit" or go to the Mass-removal subpage under Membership-management and add all the addresses into the window and click "submit".

===How do I edit a held message before approving it for the list?===

* Use the "forward this message" feature in the admindb page to forward the message to yourself.

* At the same time, discard the original held message. You may want to do this later, after you're sure the message was properly forwarded to you.

* Edit the message in your mail reader. You should include a notice in the message explaining that the list moderator has edited the message. Please use proper netiquette!

* Resend the message to the list using a Resent-To: header containing the list posting address. Also include an Approved: header containing
the list's admin password.

===How do I add users to a mailman mailing list?===

* Login to the mailman mailing list adminstration's page use your mailman admin password

http://mailman.umiacs.umd.edu/mailman/admin/MAILINGLISTNAME

* Click "Membership Management..." -> Choose "Mass Subscription"

* In the "Mass subscriptions" panel, enter user's address one address per line

* click "Submit Your Changes" button.

== mailinglistname ==

* Click "Membership Management..." -> Choose "Mass Subscription"

* In the "Mass subscriptions" panel, enter user's address one address per line

* click "Submit Your Changes" button.

MailmanFAQ

2008-10-01T18:41:39Z

Xhe: /* How do I add users to a mailman mailing list? */

===Is there an easy way to discard all messages waiting to be reviewed?===

If you have a list where non members can post but their messages are moderated, you'll have to deal with a lot of spam. After sometime, just a small percentage of them will be good posts.

The admindb page has a checkbox that allows you to discard all held messages that are marked Defer. On heavy lists with lots of spam holds, this makes clearing them much faster.

To make sure that all mail from non-members is automatically deleted, go to the privacy page followed by the sender-filter sub-page. At the bottom of the page, set to "discard" the value for "Action to take for postings from non-members for which no explicit action is defined."

On the same page, at the top, you can do the same thing for postings by members (if your list is moderated such that users can't post)

===How do I turn off HTML messages/attachments?===

On the admin page, go to the Content Filtering section.

Change "Should Mailman filter ..." to Yes.

If you leave the rest at default values, including

Yes for "Should Mailman convert text/html parts to plain text?"

your list will only distribute plain text messages with no attachments.

===How can I post from 2 or more addresses to a "members-only" list?===

If you're subscribed to a members-only list as USER@umiacs.umd.edu and accidentally post as USER@cfar.umd.edu, your message will not go through.

The solution is to actually subscribe both addresses to the list, but to disable delivery from all but one of the addresses. So in the above example, I'd subscribe USER@umiacs.umd.edu and USER@Ccfar.umd.edu, but I would disable delivery to USER@cfar.umd.edu.

You can disable delivery to an address by going to the personal options page for that address and setting "Mail delivery" to "disabled".

The list manager can disable delivery to an address by going to the membership page and clicking "no mail" nect to the address in question.

===How do I change a member's password or send them their password?===

Go to the Membership-management page, click the address in question. The page that appears allows you to set a users password or mail them their existing password by clicking on

"Email my password to me"

Note all the other options you can set for the user here.

Don't forget that members can have their password sent to them anytime they like, by clicking the appropriate button on their personal page. There is no need for you to change their password if they forgettheir password. They just have to go to

http://lists.umiacs.umd.edu/mailman/options/LISTNAME/USERNAME%40DOMAINNAME

EG:

http://lists.umiacs.umd.edu/mailman/options/umiacs/johndoe%40umiacs.umd.edu

===How can I restrict the list so only authorized persons can post?===

Turn on the moderation flag for all your existing users. Go to the membership management page, and use the Additional Member Tasks to turn on the mod flag for all users.

Then go to Privacy Options -> Sender filters and set the default_member_moderation flag to Yes so that new users are automatically set as moderated.

Set the member_moderation_action to Reject and add a nice rejection notice text to the following text box.

Set the generic_nonmember_action to Reject or Discard.

===How can someone subscribe without my doing anything?===

They just need to go to

http://lists/mailman/listinfo/LISTNAME

and fill in the form. They can also subscribe/unsubscribe by email by sending to

LISTNAME-subscribe

or to unsubscribe,

LISTNAME-unsubscribe

In ALL of the above cases, the user will receive email confirming their action. They need to just reply to the mail for this to take affect.

===How do I unsubscribe users without them getting an unsubscribe message?===

By default, they will not get an unsubscribe message. You need only go to the membership page and click the "unsub" button next to each of their names and press "submit" or go to the Mass-removal subpage under Membership-management and add all the addresses into the window and click "submit".

===How do I edit a held message before approving it for the list?===

* Use the "forward this message" feature in the admindb page to forward the message to yourself.

* At the same time, discard the original held message. You may want to do this later, after you're sure the message was properly forwarded to you.

* Edit the message in your mail reader. You should include a notice in the message explaining that the list moderator has edited the message. Please use proper netiquette!

* Resend the message to the list using a Resent-To: header containing the list posting address. Also include an Approved: header containing
the list's admin password.

===How do I add users to a mailman mailing list?===

* Login to the mailman mailing list adminstration's page use your mailman admin password

http://mailman.umiacs.umd.edu/mailman/admin/
== mailinglistname ==

* Click "Membership Management..." -> Choose "Mass Subscription"

* In the "Mass subscriptions" panel, enter user's address one address per line

* click "Submit Your Changes" button.

MailmanFAQ

2008-10-01T18:41:13Z

Xhe: /* How do I add users to a mailman mailing list? */

===Is there an easy way to discard all messages waiting to be reviewed?===

If you have a list where non members can post but their messages are moderated, you'll have to deal with a lot of spam. After sometime, just a small percentage of them will be good posts.

The admindb page has a checkbox that allows you to discard all held messages that are marked Defer. On heavy lists with lots of spam holds, this makes clearing them much faster.

To make sure that all mail from non-members is automatically deleted, go to the privacy page followed by the sender-filter sub-page. At the bottom of the page, set to "discard" the value for "Action to take for postings from non-members for which no explicit action is defined."

On the same page, at the top, you can do the same thing for postings by members (if your list is moderated such that users can't post)

===How do I turn off HTML messages/attachments?===

On the admin page, go to the Content Filtering section.

Change "Should Mailman filter ..." to Yes.

If you leave the rest at default values, including

Yes for "Should Mailman convert text/html parts to plain text?"

your list will only distribute plain text messages with no attachments.

===How can I post from 2 or more addresses to a "members-only" list?===

If you're subscribed to a members-only list as USER@umiacs.umd.edu and accidentally post as USER@cfar.umd.edu, your message will not go through.

The solution is to actually subscribe both addresses to the list, but to disable delivery from all but one of the addresses. So in the above example, I'd subscribe USER@umiacs.umd.edu and USER@Ccfar.umd.edu, but I would disable delivery to USER@cfar.umd.edu.

You can disable delivery to an address by going to the personal options page for that address and setting "Mail delivery" to "disabled".

The list manager can disable delivery to an address by going to the membership page and clicking "no mail" nect to the address in question.

===How do I change a member's password or send them their password?===

Go to the Membership-management page, click the address in question. The page that appears allows you to set a users password or mail them their existing password by clicking on

"Email my password to me"

Note all the other options you can set for the user here.

Don't forget that members can have their password sent to them anytime they like, by clicking the appropriate button on their personal page. There is no need for you to change their password if they forgettheir password. They just have to go to

http://lists.umiacs.umd.edu/mailman/options/LISTNAME/USERNAME%40DOMAINNAME

EG:

http://lists.umiacs.umd.edu/mailman/options/umiacs/johndoe%40umiacs.umd.edu

===How can I restrict the list so only authorized persons can post?===

Turn on the moderation flag for all your existing users. Go to the membership management page, and use the Additional Member Tasks to turn on the mod flag for all users.

Then go to Privacy Options -> Sender filters and set the default_member_moderation flag to Yes so that new users are automatically set as moderated.

Set the member_moderation_action to Reject and add a nice rejection notice text to the following text box.

Set the generic_nonmember_action to Reject or Discard.

===How can someone subscribe without my doing anything?===

They just need to go to

http://lists/mailman/listinfo/LISTNAME

and fill in the form. They can also subscribe/unsubscribe by email by sending to

LISTNAME-subscribe

or to unsubscribe,

LISTNAME-unsubscribe

In ALL of the above cases, the user will receive email confirming their action. They need to just reply to the mail for this to take affect.

===How do I unsubscribe users without them getting an unsubscribe message?===

By default, they will not get an unsubscribe message. You need only go to the membership page and click the "unsub" button next to each of their names and press "submit" or go to the Mass-removal subpage under Membership-management and add all the addresses into the window and click "submit".

===How do I edit a held message before approving it for the list?===

* Use the "forward this message" feature in the admindb page to forward the message to yourself.

* At the same time, discard the original held message. You may want to do this later, after you're sure the message was properly forwarded to you.

* Edit the message in your mail reader. You should include a notice in the message explaining that the list moderator has edited the message. Please use proper netiquette!

* Resend the message to the list using a Resent-To: header containing the list posting address. Also include an Approved: header containing
the list's admin password.

===How do I add users to a mailman mailing list?===

* Login to the mailman mailing list adminstration's page use your mailman admin password

http://mailman.umiacs.umd.edu/mailman/admin/'''''mailinglistname'''''

* Click "Membership Management..." -> Choose "Mass Subscription"

* In the "Mass subscriptions" panel, enter user's address one address per line

* click "Submit Your Changes" button.

MailmanFAQ

2008-10-01T18:40:57Z

Xhe: /* How do I add users to a mailman mailing list? */

===Is there an easy way to discard all messages waiting to be reviewed?===

If you have a list where non members can post but their messages are moderated, you'll have to deal with a lot of spam. After sometime, just a small percentage of them will be good posts.

The admindb page has a checkbox that allows you to discard all held messages that are marked Defer. On heavy lists with lots of spam holds, this makes clearing them much faster.

To make sure that all mail from non-members is automatically deleted, go to the privacy page followed by the sender-filter sub-page. At the bottom of the page, set to "discard" the value for "Action to take for postings from non-members for which no explicit action is defined."

On the same page, at the top, you can do the same thing for postings by members (if your list is moderated such that users can't post)

===How do I turn off HTML messages/attachments?===

On the admin page, go to the Content Filtering section.

Change "Should Mailman filter ..." to Yes.

If you leave the rest at default values, including

Yes for "Should Mailman convert text/html parts to plain text?"

your list will only distribute plain text messages with no attachments.

===How can I post from 2 or more addresses to a "members-only" list?===

If you're subscribed to a members-only list as USER@umiacs.umd.edu and accidentally post as USER@cfar.umd.edu, your message will not go through.

The solution is to actually subscribe both addresses to the list, but to disable delivery from all but one of the addresses. So in the above example, I'd subscribe USER@umiacs.umd.edu and USER@Ccfar.umd.edu, but I would disable delivery to USER@cfar.umd.edu.

You can disable delivery to an address by going to the personal options page for that address and setting "Mail delivery" to "disabled".

The list manager can disable delivery to an address by going to the membership page and clicking "no mail" nect to the address in question.

===How do I change a member's password or send them their password?===

Go to the Membership-management page, click the address in question. The page that appears allows you to set a users password or mail them their existing password by clicking on

"Email my password to me"

Note all the other options you can set for the user here.

Don't forget that members can have their password sent to them anytime they like, by clicking the appropriate button on their personal page. There is no need for you to change their password if they forgettheir password. They just have to go to

http://lists.umiacs.umd.edu/mailman/options/LISTNAME/USERNAME%40DOMAINNAME

EG:

http://lists.umiacs.umd.edu/mailman/options/umiacs/johndoe%40umiacs.umd.edu

===How can I restrict the list so only authorized persons can post?===

Turn on the moderation flag for all your existing users. Go to the membership management page, and use the Additional Member Tasks to turn on the mod flag for all users.

Then go to Privacy Options -> Sender filters and set the default_member_moderation flag to Yes so that new users are automatically set as moderated.

Set the member_moderation_action to Reject and add a nice rejection notice text to the following text box.

Set the generic_nonmember_action to Reject or Discard.

===How can someone subscribe without my doing anything?===

They just need to go to

http://lists/mailman/listinfo/LISTNAME

and fill in the form. They can also subscribe/unsubscribe by email by sending to

LISTNAME-subscribe

or to unsubscribe,

LISTNAME-unsubscribe

In ALL of the above cases, the user will receive email confirming their action. They need to just reply to the mail for this to take affect.

===How do I unsubscribe users without them getting an unsubscribe message?===

By default, they will not get an unsubscribe message. You need only go to the membership page and click the "unsub" button next to each of their names and press "submit" or go to the Mass-removal subpage under Membership-management and add all the addresses into the window and click "submit".

===How do I edit a held message before approving it for the list?===

* Use the "forward this message" feature in the admindb page to forward the message to yourself.

* At the same time, discard the original held message. You may want to do this later, after you're sure the message was properly forwarded to you.

* Edit the message in your mail reader. You should include a notice in the message explaining that the list moderator has edited the message. Please use proper netiquette!

* Resend the message to the list using a Resent-To: header containing the list posting address. Also include an Approved: header containing
the list's admin password.

===How do I add users to a mailman mailing list?===

* Login to the mailman mailing list adminstration's page use your mailman admin password

http://mailman.umiacs.umd.edu/mailman/admin/''mailinglistname''

* Click "Membership Management..." -> Choose "Mass Subscription"

* In the "Mass subscriptions" panel, enter user's address one address per line

* click "Submit Your Changes" button.

MailmanFAQ

2008-10-01T18:40:41Z

Xhe: /* How do I add users to a mailman mailing list? */

===Is there an easy way to discard all messages waiting to be reviewed?===

If you have a list where non members can post but their messages are moderated, you'll have to deal with a lot of spam. After sometime, just a small percentage of them will be good posts.

The admindb page has a checkbox that allows you to discard all held messages that are marked Defer. On heavy lists with lots of spam holds, this makes clearing them much faster.

To make sure that all mail from non-members is automatically deleted, go to the privacy page followed by the sender-filter sub-page. At the bottom of the page, set to "discard" the value for "Action to take for postings from non-members for which no explicit action is defined."

On the same page, at the top, you can do the same thing for postings by members (if your list is moderated such that users can't post)

===How do I turn off HTML messages/attachments?===

On the admin page, go to the Content Filtering section.

Change "Should Mailman filter ..." to Yes.

If you leave the rest at default values, including

Yes for "Should Mailman convert text/html parts to plain text?"

your list will only distribute plain text messages with no attachments.

===How can I post from 2 or more addresses to a "members-only" list?===

If you're subscribed to a members-only list as USER@umiacs.umd.edu and accidentally post as USER@cfar.umd.edu, your message will not go through.

The solution is to actually subscribe both addresses to the list, but to disable delivery from all but one of the addresses. So in the above example, I'd subscribe USER@umiacs.umd.edu and USER@Ccfar.umd.edu, but I would disable delivery to USER@cfar.umd.edu.

You can disable delivery to an address by going to the personal options page for that address and setting "Mail delivery" to "disabled".

The list manager can disable delivery to an address by going to the membership page and clicking "no mail" nect to the address in question.

===How do I change a member's password or send them their password?===

Go to the Membership-management page, click the address in question. The page that appears allows you to set a users password or mail them their existing password by clicking on

"Email my password to me"

Note all the other options you can set for the user here.

Don't forget that members can have their password sent to them anytime they like, by clicking the appropriate button on their personal page. There is no need for you to change their password if they forgettheir password. They just have to go to

http://lists.umiacs.umd.edu/mailman/options/LISTNAME/USERNAME%40DOMAINNAME

EG:

http://lists.umiacs.umd.edu/mailman/options/umiacs/johndoe%40umiacs.umd.edu

===How can I restrict the list so only authorized persons can post?===

Turn on the moderation flag for all your existing users. Go to the membership management page, and use the Additional Member Tasks to turn on the mod flag for all users.

Then go to Privacy Options -> Sender filters and set the default_member_moderation flag to Yes so that new users are automatically set as moderated.

Set the member_moderation_action to Reject and add a nice rejection notice text to the following text box.

Set the generic_nonmember_action to Reject or Discard.

===How can someone subscribe without my doing anything?===

They just need to go to

http://lists/mailman/listinfo/LISTNAME

and fill in the form. They can also subscribe/unsubscribe by email by sending to

LISTNAME-subscribe

or to unsubscribe,

LISTNAME-unsubscribe

In ALL of the above cases, the user will receive email confirming their action. They need to just reply to the mail for this to take affect.

===How do I unsubscribe users without them getting an unsubscribe message?===

By default, they will not get an unsubscribe message. You need only go to the membership page and click the "unsub" button next to each of their names and press "submit" or go to the Mass-removal subpage under Membership-management and add all the addresses into the window and click "submit".

===How do I edit a held message before approving it for the list?===

* Use the "forward this message" feature in the admindb page to forward the message to yourself.

* At the same time, discard the original held message. You may want to do this later, after you're sure the message was properly forwarded to you.

* Edit the message in your mail reader. You should include a notice in the message explaining that the list moderator has edited the message. Please use proper netiquette!

* Resend the message to the list using a Resent-To: header containing the list posting address. Also include an Approved: header containing
the list's admin password.

===How do I add users to a mailman mailing list?===

* Login to the mailman mailing list adminstration's page use your mailman admin password

http://mailman.umiacs.umd.edu/mailman/admin/mailinglistname

* Click "Membership Management..." -> Choose "Mass Subscription"

* In the "Mass subscriptions" panel, enter user's address one address per line

* click "Submit Your Changes" button.

MailmanFAQ

2008-10-01T18:40:25Z

Xhe: /* How do I add users to a mailman mailing list? */

===Is there an easy way to discard all messages waiting to be reviewed?===

If you have a list where non members can post but their messages are moderated, you'll have to deal with a lot of spam. After sometime, just a small percentage of them will be good posts.

The admindb page has a checkbox that allows you to discard all held messages that are marked Defer. On heavy lists with lots of spam holds, this makes clearing them much faster.

To make sure that all mail from non-members is automatically deleted, go to the privacy page followed by the sender-filter sub-page. At the bottom of the page, set to "discard" the value for "Action to take for postings from non-members for which no explicit action is defined."

On the same page, at the top, you can do the same thing for postings by members (if your list is moderated such that users can't post)

===How do I turn off HTML messages/attachments?===

On the admin page, go to the Content Filtering section.

Change "Should Mailman filter ..." to Yes.

If you leave the rest at default values, including

Yes for "Should Mailman convert text/html parts to plain text?"

your list will only distribute plain text messages with no attachments.

===How can I post from 2 or more addresses to a "members-only" list?===

If you're subscribed to a members-only list as USER@umiacs.umd.edu and accidentally post as USER@cfar.umd.edu, your message will not go through.

The solution is to actually subscribe both addresses to the list, but to disable delivery from all but one of the addresses. So in the above example, I'd subscribe USER@umiacs.umd.edu and USER@Ccfar.umd.edu, but I would disable delivery to USER@cfar.umd.edu.

You can disable delivery to an address by going to the personal options page for that address and setting "Mail delivery" to "disabled".

The list manager can disable delivery to an address by going to the membership page and clicking "no mail" nect to the address in question.

===How do I change a member's password or send them their password?===

Go to the Membership-management page, click the address in question. The page that appears allows you to set a users password or mail them their existing password by clicking on

"Email my password to me"

Note all the other options you can set for the user here.

Don't forget that members can have their password sent to them anytime they like, by clicking the appropriate button on their personal page. There is no need for you to change their password if they forgettheir password. They just have to go to

http://lists.umiacs.umd.edu/mailman/options/LISTNAME/USERNAME%40DOMAINNAME

EG:

http://lists.umiacs.umd.edu/mailman/options/umiacs/johndoe%40umiacs.umd.edu

===How can I restrict the list so only authorized persons can post?===

Turn on the moderation flag for all your existing users. Go to the membership management page, and use the Additional Member Tasks to turn on the mod flag for all users.

Then go to Privacy Options -> Sender filters and set the default_member_moderation flag to Yes so that new users are automatically set as moderated.

Set the member_moderation_action to Reject and add a nice rejection notice text to the following text box.

Set the generic_nonmember_action to Reject or Discard.

===How can someone subscribe without my doing anything?===

They just need to go to

http://lists/mailman/listinfo/LISTNAME

and fill in the form. They can also subscribe/unsubscribe by email by sending to

LISTNAME-subscribe

or to unsubscribe,

LISTNAME-unsubscribe

In ALL of the above cases, the user will receive email confirming their action. They need to just reply to the mail for this to take affect.

===How do I unsubscribe users without them getting an unsubscribe message?===

By default, they will not get an unsubscribe message. You need only go to the membership page and click the "unsub" button next to each of their names and press "submit" or go to the Mass-removal subpage under Membership-management and add all the addresses into the window and click "submit".

===How do I edit a held message before approving it for the list?===

* Use the "forward this message" feature in the admindb page to forward the message to yourself.

* At the same time, discard the original held message. You may want to do this later, after you're sure the message was properly forwarded to you.

* Edit the message in your mail reader. You should include a notice in the message explaining that the list moderator has edited the message. Please use proper netiquette!

* Resend the message to the list using a Resent-To: header containing the list posting address. Also include an Approved: header containing
the list's admin password.

===How do I add users to a mailman mailing list?===

* Login to the mailman mailing list adminstration's page use your mailman admin password

http://mailman.umiacs.umd.edu/mailman/admin/''mailinglistname''

* Click "Membership Management..." -> Choose "Mass Subscription"

* In the "Mass subscriptions" panel, enter user's address one address per line

* click "Submit Your Changes" button.

MailmanFAQ

2008-10-01T18:39:43Z

Xhe: /* How do I add users to a mailman mailing list? */

===Is there an easy way to discard all messages waiting to be reviewed?===

If you have a list where non members can post but their messages are moderated, you'll have to deal with a lot of spam. After sometime, just a small percentage of them will be good posts.

The admindb page has a checkbox that allows you to discard all held messages that are marked Defer. On heavy lists with lots of spam holds, this makes clearing them much faster.

To make sure that all mail from non-members is automatically deleted, go to the privacy page followed by the sender-filter sub-page. At the bottom of the page, set to "discard" the value for "Action to take for postings from non-members for which no explicit action is defined."

On the same page, at the top, you can do the same thing for postings by members (if your list is moderated such that users can't post)

===How do I turn off HTML messages/attachments?===

On the admin page, go to the Content Filtering section.

Change "Should Mailman filter ..." to Yes.

If you leave the rest at default values, including

Yes for "Should Mailman convert text/html parts to plain text?"

your list will only distribute plain text messages with no attachments.

===How can I post from 2 or more addresses to a "members-only" list?===

If you're subscribed to a members-only list as USER@umiacs.umd.edu and accidentally post as USER@cfar.umd.edu, your message will not go through.

The solution is to actually subscribe both addresses to the list, but to disable delivery from all but one of the addresses. So in the above example, I'd subscribe USER@umiacs.umd.edu and USER@Ccfar.umd.edu, but I would disable delivery to USER@cfar.umd.edu.

You can disable delivery to an address by going to the personal options page for that address and setting "Mail delivery" to "disabled".

The list manager can disable delivery to an address by going to the membership page and clicking "no mail" nect to the address in question.

===How do I change a member's password or send them their password?===

Go to the Membership-management page, click the address in question. The page that appears allows you to set a users password or mail them their existing password by clicking on

"Email my password to me"

Note all the other options you can set for the user here.

Don't forget that members can have their password sent to them anytime they like, by clicking the appropriate button on their personal page. There is no need for you to change their password if they forgettheir password. They just have to go to

http://lists.umiacs.umd.edu/mailman/options/LISTNAME/USERNAME%40DOMAINNAME

EG:

http://lists.umiacs.umd.edu/mailman/options/umiacs/johndoe%40umiacs.umd.edu

===How can I restrict the list so only authorized persons can post?===

Turn on the moderation flag for all your existing users. Go to the membership management page, and use the Additional Member Tasks to turn on the mod flag for all users.

Then go to Privacy Options -> Sender filters and set the default_member_moderation flag to Yes so that new users are automatically set as moderated.

Set the member_moderation_action to Reject and add a nice rejection notice text to the following text box.

Set the generic_nonmember_action to Reject or Discard.

===How can someone subscribe without my doing anything?===

They just need to go to

http://lists/mailman/listinfo/LISTNAME

and fill in the form. They can also subscribe/unsubscribe by email by sending to

LISTNAME-subscribe

or to unsubscribe,

LISTNAME-unsubscribe

In ALL of the above cases, the user will receive email confirming their action. They need to just reply to the mail for this to take affect.

===How do I unsubscribe users without them getting an unsubscribe message?===

By default, they will not get an unsubscribe message. You need only go to the membership page and click the "unsub" button next to each of their names and press "submit" or go to the Mass-removal subpage under Membership-management and add all the addresses into the window and click "submit".

===How do I edit a held message before approving it for the list?===

* Use the "forward this message" feature in the admindb page to forward the message to yourself.

* At the same time, discard the original held message. You may want to do this later, after you're sure the message was properly forwarded to you.

* Edit the message in your mail reader. You should include a notice in the message explaining that the list moderator has edited the message. Please use proper netiquette!

* Resend the message to the list using a Resent-To: header containing the list posting address. Also include an Approved: header containing
the list's admin password.

===How do I add users to a mailman mailing list?===

* Login to the mailman mailing list adminstration's page use your mailman admin password

http://mailman.umiacs.umd.edu/mailman/admin/<it>mailinglistname</it>

* Click "Membership Management..." -> Choose "Mass Subscription"

* In the "Mass subscriptions" panel, enter user's address one address per line

* click "Submit Your Changes" button.

MailmanFAQ

2008-10-01T18:37:24Z

Xhe: /* How do I add users to a mailman mailing list? */

===Is there an easy way to discard all messages waiting to be reviewed?===

If you have a list where non members can post but their messages are moderated, you'll have to deal with a lot of spam. After sometime, just a small percentage of them will be good posts.

The admindb page has a checkbox that allows you to discard all held messages that are marked Defer. On heavy lists with lots of spam holds, this makes clearing them much faster.

To make sure that all mail from non-members is automatically deleted, go to the privacy page followed by the sender-filter sub-page. At the bottom of the page, set to "discard" the value for "Action to take for postings from non-members for which no explicit action is defined."

On the same page, at the top, you can do the same thing for postings by members (if your list is moderated such that users can't post)

===How do I turn off HTML messages/attachments?===

On the admin page, go to the Content Filtering section.

Change "Should Mailman filter ..." to Yes.

If you leave the rest at default values, including

Yes for "Should Mailman convert text/html parts to plain text?"

your list will only distribute plain text messages with no attachments.

===How can I post from 2 or more addresses to a "members-only" list?===

If you're subscribed to a members-only list as USER@umiacs.umd.edu and accidentally post as USER@cfar.umd.edu, your message will not go through.

The solution is to actually subscribe both addresses to the list, but to disable delivery from all but one of the addresses. So in the above example, I'd subscribe USER@umiacs.umd.edu and USER@Ccfar.umd.edu, but I would disable delivery to USER@cfar.umd.edu.

You can disable delivery to an address by going to the personal options page for that address and setting "Mail delivery" to "disabled".

The list manager can disable delivery to an address by going to the membership page and clicking "no mail" nect to the address in question.

===How do I change a member's password or send them their password?===

Go to the Membership-management page, click the address in question. The page that appears allows you to set a users password or mail them their existing password by clicking on

"Email my password to me"

Note all the other options you can set for the user here.

Don't forget that members can have their password sent to them anytime they like, by clicking the appropriate button on their personal page. There is no need for you to change their password if they forgettheir password. They just have to go to

http://lists.umiacs.umd.edu/mailman/options/LISTNAME/USERNAME%40DOMAINNAME

EG:

http://lists.umiacs.umd.edu/mailman/options/umiacs/johndoe%40umiacs.umd.edu

===How can I restrict the list so only authorized persons can post?===

Turn on the moderation flag for all your existing users. Go to the membership management page, and use the Additional Member Tasks to turn on the mod flag for all users.

Then go to Privacy Options -> Sender filters and set the default_member_moderation flag to Yes so that new users are automatically set as moderated.

Set the member_moderation_action to Reject and add a nice rejection notice text to the following text box.

Set the generic_nonmember_action to Reject or Discard.

===How can someone subscribe without my doing anything?===

They just need to go to

http://lists/mailman/listinfo/LISTNAME

and fill in the form. They can also subscribe/unsubscribe by email by sending to

LISTNAME-subscribe

or to unsubscribe,

LISTNAME-unsubscribe

In ALL of the above cases, the user will receive email confirming their action. They need to just reply to the mail for this to take affect.

===How do I unsubscribe users without them getting an unsubscribe message?===

By default, they will not get an unsubscribe message. You need only go to the membership page and click the "unsub" button next to each of their names and press "submit" or go to the Mass-removal subpage under Membership-management and add all the addresses into the window and click "submit".

===How do I edit a held message before approving it for the list?===

* Use the "forward this message" feature in the admindb page to forward the message to yourself.

* At the same time, discard the original held message. You may want to do this later, after you're sure the message was properly forwarded to you.

* Edit the message in your mail reader. You should include a notice in the message explaining that the list moderator has edited the message. Please use proper netiquette!

* Resend the message to the list using a Resent-To: header containing the list posting address. Also include an Approved: header containing
the list's admin password.

===How do I add users to a mailman mailing list?===

* Login to the mailman mailing list adminstration's page use your mailman admin password

http://mailman.umiacs.umd.edu/mailman/admin/mailinglistname

* Click "Membership Management..." -> Choose "Mass Subscription"

* In the "Mass subscriptions" panel, enter user's address pne address per line

* click "Submit Your Changes" button.

MailmanFAQ

2008-10-01T18:22:19Z

Xhe: /* How do I add users to a mailman mailing list? */

MailmanFAQ

2008-10-01T18:20:22Z

Xhe:

MailmanFAQ

2008-10-01T18:18:12Z

Xhe: