UMIACS - User contributions [en]

PythonVirtualEnv

2016-08-03T18:41:38Z

Jwebs: /* Using a different python version */

A virtual environment is an isolated working copy of Python, which allows you to work on specific projects without affecting others. It creates an environment that has its own installation directories and that doesn’t share libraries with other virtualenv environments (and optionally doesn’t access the globally-installed libraries either).
 
virtualenv can be found in the following locations:
*'''RHEL5'''
:<code>/usr/local/stow/virtualenv-1.5.1/virtualenv.py</code>
*'''RHEL6'''
:<code>/opt/local/stow/virtualenv-1.9.1/virtualenv.py</code>
*'''RHEL7'''
:<code>/usr/lib/python2.7/site-packages/virtualenv.py</code>
*'''SOURCE''' (most up-to-date)
:<code>https://virtualenv.pypa.io/en/latest/</code>
:<code>https://github.com/pypa/virtualenv</code>

==Basic Usage==
The following steps outline how to create a virtual environment using the system Python.
''Please note the that following examples were done using RHEL5. Please adjust the commands to reflect the OS you are on.''

====Creating the virtual environment (example)====
<pre>
-bash-3.2$ git clone https://github.com/pypa/virtualenv.git
-bash-3.2$ python virtualenv/virtualenv.py env
New python executable in env/bin/python
Installing setuptools.............done.

-bash-3.2$ source env/bin/activate

(env)-bash-3.2$ which python
~/env/bin/python
</pre>

You will notice that once you have created your virtual environment, you will need to use the 'source' command to load it into your environment. In bash and tcsh, the environment can be deactivated by typing <code>deactivate</code>

====Installing Python Modules====
Once you have created your virtual environment and sourced it, you can install additional modules using the 'pip' command.

<pre>
(env)-bash-3.2$ pip install nose
Downloading/unpacking nose
Downloading nose-1.3.3.tar.gz (274Kb): 274Kb downloaded
Running setup.py egg_info for package nose

...output omitted for brevity...

Successfully installed nose
Cleaning up...
(env)-bash-3.2$
</pre>

====Listing installed Python Modules====
<pre>
(env)-bash-3.2$ pip freeze
nose==1.3.3
</pre>
====Uninstalling Python Modules====
'pip' can also be used to remove a module from the environment.
<pre>
(env)-bash-3.2$ pip uninstall nose
Uninstalling nose:
/chimerahomes/sabobbin/env/bin/nosetests
/chimerahomes/sabobbin/env/bin/nosetests-2.4
/chimerahomes/sabobbin/env/lib/python2.4/site-packages/nose
/chimerahomes/sabobbin/env/lib/python2.4/site-packages/nose-1.3.3-py2.4.egg-info
/chimerahomes/sabobbin/env/man/man1/nosetests.1
Proceed (y/n)? y
Successfully uninstalled nose
</pre>

===Switching between virtual environments===
To switch between different environments, simply deactivate your current virtual environment, and source the other.
<pre>
(env)-bash-3.2$ which python
~/env/bin/python

(env)-bash-3.2$ deactivate

-bash-3.2$ source env2.7/bin/activate

(env2.7)-bash-3.2$ which python
~/env2.7/bin/python
</pre>

==Using a different python version==
To create a virtual environment that uses a version of python that is different then the system default, simply create the virtualenv with your target version of Python. This could be a Python build we provide via [[Modules]], or one you've built yourself. Virtualenv will pick up the first python version it finds in your $PATH, or you can direct it to a specific location with the "--python" flag.

<pre>
-bash-3.2$ module load Python

-bash-3.2$ which python
/usr/local/stow/python-2.7.2/bin/python
</pre>
'''Important:''' virtualenv will include any modules listed in your PYTHONPATH when initializing the virtual environment. To ensure a vanilla environment, it might be a good idea to verify your PYTHONPATH is empty.
<pre>
-bash-3.2$ echo $PYTHONPATH
/usr/local/stow/python-commonmodules-2.7.2.0/lib/python2.7/site-packages

-bash-3.2$ PYTHONPATH=''
</pre>
<pre>
-bash-3.2$ /usr/local/stow/virtualenv-1.5.1/virtualenv.py env2.7
New python executable in env2.7/bin/python
Installing setuptools....................done.

-bash-3.2$ source env2.7/bin/activate
(env2.7)-bash-3.2$ which python
~/env2.7/bin/python
</pre>

UbuntuPrinting

2016-03-17T18:08:09Z

Jwebs: no Junos VPN availability in Ubuntu at the moment

==Overview==
:Printing from your personal Ubuntu laptop or desktop is supported. If you are sitting at a supported UMIACS Ubuntu LTS desktop then please see our common UNIX/Linux printing documentation for [[CUPS]]. This documentation assumes the current Ubuntu LTS 12.04.xx release and while older or newer versions of Ubuntu may work, we have not tested them.
===Printer Accessibility===
:In order to print you will '''need to be on the UMIACS internal network,''' either via a wired proxy drop or an [https://wiki.umiacs.umd.edu/umiacs/index.php/SecureShellTunneling SSH tunnel].
 
 
==Connecting to a printer==
In order for printing to function properly, you must complete '''ALL''' of the following steps:
 
 
#Open the 'Printing' dialog box and click 'Add'
#Expand the 'Network Printer' dropdown list, and select 'Find Network Printer'
#In the host field type "print.umiacs.umd.edu" and click find.
#:[[Image:UbuntuPrint01.png|thumb|none|300px|[3] Type 'print.umiacs.umd.edu' into the 'Host:' field and then click Find]]
#Select the print queue you wish to print to, click forward. If you are unsure which queue to use, see the [[PrinterQueueNaming| selecting a print queue]] page.
#:[[Image:UbuntuPrint02.png|thumb|none|300px|[4] Select the queue you wish to print too]]
#Name the printer. '''Take note of the model name listed in the Description. This will be used later!''' Then click 'Apply'
#:[[Image:UbuntuPrint03.png|thumb|none|300px|[5] Take note of the printer description, this will be used in later steps!]]
#In the printing dialog box, right click the newly added printer and select properties.
#In the 'Make and Model' line, click 'change'
#:[[Image:UbuntuPrint04.png|thumb|none|300px|[7] Click 'change' next the 'Make and Model' field.]]
#Ubuntu will now load a list of printers models (This will take a few moments). From that list, select the brand of the printer you are connecting to as noted in step 5.
#:[[Image:UbuntuPrint05.png|thumb|none|300px|[8] Select the brand of the printer as you noted in step 5]]
#Select the specific model of the printer as noted in step 5. Then click forward.
#:[[Image:UbuntuPrint06.png|thumb|none|300px|[9] Select the model of the printer as you noted in step 5]]
#Leave the "try to copy the option settings over from the old PPD' option selected and click forward.
#Select any additional features available for the printer (i.e. duplexing), and then click forward.
#Verify this process by printing a test page. You should get the Default ubuntu test page. If you just get a page with a string of text then printer is not properly configured, and you should verify the settings.

==[[PrinterQueueNaming|How to select a print queue]]==

Printing

2015-07-18T00:24:52Z

Jwebs:

==Printing==
*'''Operating Specific printing guides:'''
:* [[WindowsPrinting|Windows Printing Guide]]
:* [[OSXPrinting|Mac OS X Printing Guide]]
:* [[CUPS|Linux Printing Guide (RHEL and Ubuntu)]]
:* [[UbuntuPrinting|Self supported Ubuntu Printing Guide]]

* Printing from the wireless or Non-UMIACS Networks
** UMIACS account holders: Connect to the UMIACS [[VPN]]. Afterwards, follow the instructions in [[WindowsPrinting]] for Windows or [[OSXPrinting]] for Mac.
** UMIACS guests and self-supported systems may print using the [[Windows7PrintingNonUMIACS | open print server]]

* [[PrinterQueueNaming|Selecting A Print Queue (Color, Banners, etc)]]

* [[UNIXPrinting|Legacy UNIX Printing Guide (Linux and Solaris)]]

* [[Umiacs_Public_Printers | Umiacs Public Printers]]

*[[PrinterTroubleshooting | Printer troubleshooting]]

SecureShellTunneling

2015-05-04T17:09:18Z

Jwebs: /* Example: SOCKS proxy, Browser configuration */

==Port Forwarding==

When you want to just forward a specific port locally to a remote port.

This example will create a local port 9999 that will be forwarded to the remote host webbserver.umiacs.umd.edu and its port 8000 through the host openlab.umiacs.umd.edu.

* ssh -NfL 9999:webserver.umiacs.umd.edu:8000 openlab.umiacs.umd.edu

This example will create a local port 13389 that will be forwarded to a remote host that is running a [[Remote Desktop |RDP]] client like Windows through the host openlab.umiacs.umd.edu

* ssh -L 13389:my-desktop.pc.umiacs.umd.edu:3389 openlab.umiacs.umd.edu

==SOCKS Proxy==

[[SSH]] can also tunnel all traffic coming into a certain port through a SOCKS v5 proxy. Many browsers and some operating systems can be setup to then connect to this proxy to allow them again to look like they are coming from the host name you specify in your [[SSH]] command.

* ssh -ND 7777 openlab.umiacs.umd.edu

Please note: when you configure proxy settings for a browser (or your whole operating system) all the traffic for that browser (or the OS) will be sent through the proxy. This can have performance implications.

==Port Forwarding with PuTTY==

Windows users can achieve the same types of tunnels using PuTTY or a similar SSH client. In PuTTY, the port forwarding configuration dialogue can be found under "Connection>SSH>Tunnels".

[[Image:PuTTYWin7Tunnel.png]]

This example will create a local port '''8889''' that is attached to the remote host '''clipsm301.umiacs.umd.edu''' on its port '''8000'''.

==Socks Proxy with PuTTY==

Windows users can tunnel traffic coming into a certain port through a SOCKS v5 proxy by using PuTTY or a similar SSH client. Many browsers and some operating systems can be setup to connect to this proxy to allow them to look like they are coming from the host name you specify.

In PuTTY under "Sessions" set the Host Name:
[[Image:Putty1.png]]

Then under "Connection>SSH>Tunnels" enter a port number and set the type of forwarding to "Dynamic" and press add:

[[Image:Putty2.png]]

Click Open and log into the host.
As long as this PuTTY window is open and you are logged in, you can use the SOCKS proxy.

Please note that when you configure proxy settings for a browser or your whole operating system, all the traffic for that browser or your OS will be sent through the proxy. This can have performance implications.

== Example: SOCKS proxy, Browser configuration ==
[[Image:FF_Proxy_1.png|thumb|]] [[Image:FF_Proxy_2.png|thumb|]]
There are too many variations here to cover them all, but they all follow the same general pattern and the following example should be generally applicable. We'll use Firefox for this example. Screenshots are from FF 37.0.2

* Under <code> Preferences > Advanced > Network > Connection > Settings... </code>
* choose <code>Manually proxy configuration:</code>,
* enter <code>127.0.0.1</code> for the proxy
* enter the port you chose earlier for dynamic forwarding (7777 in the example above.)
* Check <code>Use this proxy server for all protocols</code>, and then click OK.

'''NOTE:''' this will continue to send all browser traffic through your SSH tunnel until the configuration is reverted. The SSH connection must be established for traffic to pass through to the destination network. Firefox has a very useful plugin called "FoxyProxy" that allows conditional proxies to be set up, if you're interested in adding some intelligence/complexity to your proxy configuration.

SecureShellTunneling

2015-05-04T17:06:25Z

Jwebs: Added Browser Config example

==Port Forwarding==

When you want to just forward a specific port locally to a remote port.

This example will create a local port 9999 that will be forwarded to the remote host webbserver.umiacs.umd.edu and its port 8000 through the host openlab.umiacs.umd.edu.

* ssh -NfL 9999:webserver.umiacs.umd.edu:8000 openlab.umiacs.umd.edu

This example will create a local port 13389 that will be forwarded to a remote host that is running a [[Remote Desktop |RDP]] client like Windows through the host openlab.umiacs.umd.edu

* ssh -L 13389:my-desktop.pc.umiacs.umd.edu:3389 openlab.umiacs.umd.edu

==SOCKS Proxy==

[[SSH]] can also tunnel all traffic coming into a certain port through a SOCKS v5 proxy. Many browsers and some operating systems can be setup to then connect to this proxy to allow them again to look like they are coming from the host name you specify in your [[SSH]] command.

* ssh -ND 7777 openlab.umiacs.umd.edu

Please note: when you configure proxy settings for a browser (or your whole operating system) all the traffic for that browser (or the OS) will be sent through the proxy. This can have performance implications.

==Port Forwarding with PuTTY==

Windows users can achieve the same types of tunnels using PuTTY or a similar SSH client. In PuTTY, the port forwarding configuration dialogue can be found under "Connection>SSH>Tunnels".

[[Image:PuTTYWin7Tunnel.png]]

This example will create a local port '''8889''' that is attached to the remote host '''clipsm301.umiacs.umd.edu''' on its port '''8000'''.

==Socks Proxy with PuTTY==

Windows users can tunnel traffic coming into a certain port through a SOCKS v5 proxy by using PuTTY or a similar SSH client. Many browsers and some operating systems can be setup to connect to this proxy to allow them to look like they are coming from the host name you specify.

In PuTTY under "Sessions" set the Host Name:
[[Image:Putty1.png]]

Then under "Connection>SSH>Tunnels" enter a port number and set the type of forwarding to "Dynamic" and press add:

[[Image:Putty2.png]]

Click Open and log into the host.
As long as this PuTTY window is open and you are logged in, you can use the SOCKS proxy.

Please note that when you configure proxy settings for a browser or your whole operating system, all the traffic for that browser or your OS will be sent through the proxy. This can have performance implications.

== Example: SOCKS proxy, Browser configuration ==
[[Image:FF_Proxy_1.png|thumb|]] [[Image:FF_Proxy_2.png|thumb|]]
There are too many variations here to cover them all, but they all follow the same general pattern and the following example should be generally applicable. We'll use Firefox for this example. Screenshots are from FF 37.0.2

* Under <code> Preferences > Advanced > Network > Connection > Settings... </code>
* choose <code>Manually proxy configuration:</code>,
* enter <code>127.0.0.1</code> for the proxy
* enter the port you chose earlier for dynamic forwarding (7777 in the example above.)
* Check <code>Use this proxy server for all protocols</code>, and then click OK.

Bear in mind that this will continue to send all browser traffic through your SSH tunnel until the configuration is reverted. The SSH connection must be established for traffic to pass through to the destination network. Firefox has a very useful plugin called "FoxyProxy" that allows conditional proxies to be set up, if you're interested in adding some intelligence/complexity to your proxy configuration.

File:FF Proxy 2.png

2015-05-04T17:00:42Z

Jwebs: FF 37.0.2 Advanced Preferences

FF 37.0.2 Advanced Preferences

File:FF Proxy 1.png

2015-05-04T17:00:03Z

Jwebs: FF 37.0.2 Advanced Preferences

FF 37.0.2 Advanced Preferences

PythonVirtualEnv

2015-05-02T23:17:51Z

Jwebs: some minor updates & broken link fix. This page needs an overhaul.

A virtual environment is an isolated working copy of Python which allows you to to work on specific projects, without affecting others. It creates an environment that has its own installation directories, that doesn’t share libraries with other virtualenv environments (and optionally doesn’t access the globally installed libraries either).
 
virtualenv can be found in the following locations:
*'''RHEL5'''
:<code>usr/local/stow/virtualenv-1.5.1/virtualenv.py</code>
*'''RHEL6'''
:<code>/opt/local/stow/virtualenv-1.9.1/virtualenv.py</code>
*'''RHEL7'''
:<code>/usr/lib/python2.7/site-packages/virtualenv.py</code>
*'''SOURCE''' (most up-to-date)
:<code>https://virtualenv.pypa.io/en/latest/</code>
:<code>https://github.com/pypa/virtualenv</code>

==Basic Usage==
The following steps outline how to create a virtual environment using the system Python.
''Please note the that following examples were done using RHEL5. Please adjust the commands to reflect the OS you are on.''

====Creating the virtual environment (example)====
<pre>

# Get a current version of UMIACS-provided python
-bash-3.2$ module load Python

-bash-3.2$ git clone https://github.com/pypa/virtualenv.git
-bash-3.2$ python virtualenv/virtualenv.py env
New python executable in env/bin/python
Installing setuptools.............done.

-bash-3.2$ source env/bin/activate

(env)-bash-3.2$ which python
~/env/bin/python
</pre>

You will notice that once you have created your virtual environment, you will need to use the 'source' command to load it into your environment. In bash and tcsh, the environment can be deactivated by typing <code>deactivate</code>

====Installing Python Modules====
Once you have created your virtual environment and sourced it, you can install additional modules using the 'pip' command.

<pre>
(env)-bash-3.2$ pip install nose
Downloading/unpacking nose
Downloading nose-1.3.3.tar.gz (274Kb): 274Kb downloaded
Running setup.py egg_info for package nose

...output omitted for brevity...

Successfully installed nose
Cleaning up...
(env)-bash-3.2$
</pre>

====Listing installed Python Modules====
<pre>
(env)-bash-3.2$ pip freeze
nose==1.3.3
</pre>
====Uninstalling Python Modules====
'pip' can also be used to remove a module from the environment.
<pre>
(env)-bash-3.2$ pip uninstall nose
Uninstalling nose:
/chimerahomes/sabobbin/env/bin/nosetests
/chimerahomes/sabobbin/env/bin/nosetests-2.4
/chimerahomes/sabobbin/env/lib/python2.4/site-packages/nose
/chimerahomes/sabobbin/env/lib/python2.4/site-packages/nose-1.3.3-py2.4.egg-info
/chimerahomes/sabobbin/env/man/man1/nosetests.1
Proceed (y/n)? y
Successfully uninstalled nose
</pre>

===Switching between virtual environments===
To switch between different environments, simply deactivate your current virtual environment, and source the other.
<pre>
(env)-bash-3.2$ which python
~/env/bin/python

(env)-bash-3.2$ deactivate

-bash-3.2$ source env2.7/bin/activate

(env2.7)-bash-3.2$ which python
~/env2.7/bin/python
</pre>

==Using a different python version==
To create a virtual environment that uses a version of python that is different then the system default, simply create the virtualenv with your target version of Python.
<pre>
-bash-3.2$ module load Python

-bash-3.2$ which python
/usr/local/stow/python-2.7.2/bin/python
</pre>
'''Important:''' virtualenv will include any modules listed in your PYTHONPATH when initializing the virtual environment. To ensure a vanilla environment, it might be a good idea to verify your PYTHONPATH is empty.
<pre>
-bash-3.2$ echo $PYTHONPATH
/usr/local/stow/python-commonmodules-2.7.2.0/lib/python2.7/site-packages

-bash-3.2$ PYTHONPATH=''
</pre>
<pre>
-bash-3.2$ /usr/local/stow/virtualenv-1.5.1/virtualenv.py env2.7
New python executable in env2.7/bin/python
Installing setuptools....................done.

-bash-3.2$ source env2.7/bin/activate
(env2.7)-bash-3.2$ which python
~/env2.7/bin/python
</pre>

UsrLocal

2015-02-28T02:01:11Z

Jwebs:

'''Note:''' Please see [[Modules]], which is now our preferred method of providing locally-built software to the Institute, as well as its various labs and centers.

<hr>

<tt>/usr/local</tt> is managed via a [[Stow]] system.

If you are looking for a specific piece of software you can list the directory <tt>/usr/local/stow</tt>. Some software is linked in with the <tt>stow</tt> command directly into <tt>bin,lib,man,sbin</tt> directories in <tt>/usr/local</tt>.

Starting with [[RHEL6]] the software will be moving from <tt>/usr/local</tt> to <tt>/opt/local</tt> to work around some issues with the root user and problems with NFS.

CrowdStrike

2015-01-30T23:15:57Z

Jwebs:

== Free malware/virus removal tools ==
For non-UMIACS supported systems, there are several virus and malware protection and removal tools available. This page lists and describes some of them.
<ol>
<li> F-Secure
* [http://www.f-secure.com/en/web/labs_global/removal-tools/-/carousel/view/142 Bootable Scan]
If your computer no longer starts due to malware corrupting the operating system, or you suspect the security software has been compromised,this bootable cd can securely boot up the computer and check the programs installed.The Rescue CD can also be used for more advanced repair and data recovery operations.
* [http://www.f-secure.com/en/web/home_global/online-scanner Online Scan]</li>
Similar to the bootable scan, the online scanner helps to get rid of viruses and spyware that may cause problems on your PC.
<li> [https://www.malwarebytes.org/mwb-download/ Malwarebytes]</li>
This free version is limited, but can also perform malware and virus scans
<li> [http://www.superantispyware.com/superantispyware.html SUPERAntiSpyware]</li>
This free version is also limited but performs multiple different malware scans such installed or internet spyware/adware
<li> [http://www.kaspersky.com/antivirus-removal-tool?form=1 Kaspersky virus removal tool]</li>
This provides a virus scan with updated virus definitions
</ol>

== Other "offline" (bootable) Scanners ==
Offline/bootable scanners work without loading your operating system, and can provide an alternate means for detecting and mitigating threats that may use various tactics to hide from your favorite installed AV suite.
* [http://support.kaspersky.com/viruses/rescuedisk#downloads Kaspersky Rescue Disk]
* [http://www.bitdefender.com/support/how-to-create-a-bitdefender-rescue-cd-627.html BitDefender Rescue CD]
* [https://www.f-secure.com/en/web/labs_global/rescue-cd F-Secure Rescue CD]

OBJ

2014-11-04T19:59:37Z

Jwebs: /* UMIACS Object Store */ Added a link to OBJbox WebUI

= UMIACS Object Store =
A object store is a simple web based storage solution focused on reliability, scalability and security. It is best suited for public content storage/distribution, archiving data or secure data sharing between users. Our Object Storage can be used through the [https://obj.umiacs.umd.edu/obj web interface], the command line [[UMobj]] utilities, third-party graphical [[S3Clients | clients]], and even programmatically using many popular programming languages. We support a subset of the Amazon Simple Storage Services [http://docs.aws.amazon.com/AmazonS3/latest/API/Welcome.html (S3) API], built around a technology called [http://ceph.com/ Ceph].

= Getting Started =
UMIACS users are initially allocated 50GB of storage and faculty 500GB.
To get started you just need to log in to create your account and you will be redirected to the initial help page. You can find the link from our https://intranet.umiacs.umd.edu site as "OBJbox Object Store".

Phishing

2014-11-04T08:29:07Z

Jwebs:

Phishing attacks may be hard to distinguish from legitimate administrative messages, especially those in which the supposed UMIACS staff advise or require users to take administrative actions related to their account (e.g. storage quota, email account, or general account usage).

Below are some helpful tips and practices that will make it easier to distinguish between legitimate UMIACS staff messages and phishing attempts.

==Legitimate Mail from Staff==

The [https://www.intranet.umiacs.umd.edu UMIACS intranet site] will always have a posted announcement of any administrative actions we wish our users to take collectively. We suggest to always type this address into your browser or have a bookmark for this site. This URL will also always redirect to a SSL-secured site. Please check that your browser is reporting a secure connection when visiting the site. This will always be the case for any URL in the *.umiacs.umd.edu domain and is currently valid until March 15th, 2017. UMIACS staff will communicate any changes or updates to the certificate validating this via an announcement.

When we do send out requests for advisory and mandatory actions for a user they will be signed with a staff member's GPG key. We provide a tool called Verify Staff GPG Messages from the UMIACS intranet site (also linked below). This allows you to paste the text of the message and confirm that the sender is legitimate. Please note that other communications that are initiated by users through our Jira ticket system or in response to these tickets will not be signed.
* [https://intranet.umiacs.umd.edu/staff/gpg/verify Verify Staff GPG Messages]

==Some Telltale Signs of Phishing==

The above steps should ensure that you are properly able to identify legitimate messages sent by staff. Below are some additional generic signs that should help identify phishing attempts.

* Bogus to and from addresses (not within the UMIACS or UMD domains)
* Message not directly referencing you by name (e.g. "Hello user" or "Hello researcher")
* Sender of message demanding that action be taken immediately or consequences will occur (without an appropriate GPG key included)
* Poor grammar and spelling in the message
* Hyperlinks pointing to different locations than they claim to or shady attachments being included with the message
**'''WARNING: Do NOT click on any links or open any attachments in a message you suspect to be a phishing attempt, as these may lead to the execution of malicious programs on your machine. Instead, hover over links to check where they really point to.'''

If you ever have questions about the legitimacy of a message please open a ticket with staff by sending mail to [mailto:staff@umiacs.umd.edu staff] or call our [[HelpDesk | Help Desk]] and we can verify whether or not it was sent out by staff.

==If You Have Fallen Victim==

If you believe you've fallen victim to a phishing attack or otherwise believe your account may have been compromised, please open a ticket via sending mail to [mailto:staff@umiacs.umd.edu staff] or contact the [[HelpDesk | Help Desk]] immediately. The sooner we know about any potential issues the sooner we can take preventive measures to make sure as little harm is done as possible. This typically will involve a password change as well as possibly locking out access to your account for some period of time while we ensure your account is secure.

OBJ

2014-11-04T07:27:35Z

Jwebs:

= UMIACS Object Store =
A object store is a simple web based storage solution focused on reliability, scalability and security. It is best suited for public content storage/distribution, archiving data or secure data sharing between users. Our Object Storage can be used through the web interface, the command line [[UMobj]] utilities, third-party graphical [[S3Clients | clients]], and even programmatically using many popular programming languages. We support a subset of the Amazon Simple Storage Services [http://docs.aws.amazon.com/AmazonS3/latest/API/Welcome.html (S3) API], built around a technology called [http://ceph.com/ Ceph].

= Getting Started =
UMIACS users are initially allocated 50GB of storage and faculty 500GB.
To get started you just need to log in to create your account and you will be redirected to the initial help page. You can find the link from our https://intranet.umiacs.umd.edu site as "OBJbox Object Store".

OBJ

2014-11-04T07:27:19Z

Jwebs: added link to S3Clients

= UMIACS Object Store =
A object store is a simple web based storage solution focused on reliability, scalability and security. It is best suited for public content storage/distribution, archiving data or secure data sharing between users. Our Object Storage can be used through the web interface, the command line [[UMobj]] utilities, third-party graphical [[S3Clients clients]], and even programmatically using many popular programming languages. We support a subset of the Amazon Simple Storage Services [http://docs.aws.amazon.com/AmazonS3/latest/API/Welcome.html (S3) API], built around a technology called [http://ceph.com/ Ceph].

= Getting Started =
UMIACS users are initially allocated 50GB of storage and faculty 500GB.
To get started you just need to log in to create your account and you will be redirected to the initial help page. You can find the link from our https://intranet.umiacs.umd.edu site as "OBJbox Object Store".

OBJ

2014-11-04T07:17:51Z

Jwebs: init

= UMIACS Object Store =
A object store is a simple web based storage solution focused on reliability, scalability and security. It is best suited for public content storage/distribution, archiving data or secure data sharing between users. Our Object Storage can be used through the web interface, the command line [[UMobj]] utilities, third-party graphical clients, and even programmatically using many popular programming languages. We support a subset of the Amazon Simple Storage Services [http://docs.aws.amazon.com/AmazonS3/latest/API/Welcome.html (S3) API], built around a technology called [http://ceph.com/ Ceph].

= Getting Started =
UMIACS users are initially allocated 50GB of storage and faculty 500GB.
To get started you just need to log in to create your account and you will be redirected to the initial help page. You can find the link from our https://intranet.umiacs.umd.edu site as "OBJbox Object Store".

Jira

2013-08-18T16:45:37Z

Jwebs:

JIRA is a request and bug tracker that UMIACS uses to provide our [[HelpDesk]] functionality to our users. It can be accessed [https://intranet.umiacs.umd.edu/jira here. ]

It is a web based ticketing system that allows both users and staff to maintain greater control over their tickets and makes communication and resolution of issues a seamless process.

== Using JIRA ==

JIRA automatically generates an account when it receives an email; '''by default, you can log in to JIRA with your UMIACS email address (not username!)''' and UMIACS [[Kerberos]] password. When you email JIRA, a ticket is created, and the email address your mail was sent from is added as a participant to the ticket -- this means that if you create a ticket using a non-UMIACS email address, you'll have to login to JIRA using that email address to see the ticket.

[[Image:Jira_login.png]]

* Off site users use their email address and can request a password be emailed to them via this [https://intranet.umiacs.umd.edu/jira/secure/ForgotLoginDetails!default.jspa link]. '''(For external users only!)'''

Jira

2013-08-18T16:45:05Z

Jwebs: non-umiacs email wasn't emphasized enough (probably still isnt...)

JIRA is a request and bug tracker that UMIACS uses to provide our [[HelpDesk]] functionality to our users. It can be accessed [https://intranet.umiacs.umd.edu/jira here. ]

It is a web based ticketing system that allows both users and staff to maintain greater control over their tickets and makes communication and resolution of issues a seamless process.

== Using JIRA ==

JIRA automatically generates an account when it receives an email; '''by default, you can log in to JIRA with your UMIACS email address (not username!)''' and UMIACS [[Kerberos]] password. When you email JIRA, a ticket is created, and the email address your mail was sent from is added as a participant to the ticket -- this means that if you create a ticket using a non-UMIACS email address, you'll have to login to JIRA using that email address* to see the ticket.

[[Image:Jira_login.png]]

* Off site users use their email address and can request a password be emailed to them via this [https://intranet.umiacs.umd.edu/jira/secure/ForgotLoginDetails!default.jspa link]. '''(For external users only!)'''

OptLocal

2013-08-05T17:38:40Z

Jwebs: We use GNU Environment Modules now...

'''Note:''' Please see [[Modules]], which is now our preferred method of providing locally-built software to the Institute, as well as its various labs and centers.

<hr>

<tt>/opt/local</tt> is managed via a [[Stow]] system.

If you are looking for a specific piece of software you can list the directory <tt>/opt/local/stow</tt>. Some software is linked in with the <tt>stow</tt> command directly into <tt>bin,lib,man,sbin</tt> directories in <tt>/opt/local</tt>.

This only pertains to [[RHEL6]] and above. The software previously was found in <tt>/usr/local</tt>.

Main Page

2013-08-02T17:54:09Z

Jwebs: Basic early-close message (for full-staff tech talk)

===Announcements===

== Help Desk Early Closing (Tuesday, August 6th, 2013) ==
The UMIACS Help Desk will be closing at 4PM on Tuesday, August 6th, 2013. Our normal schedule will resume on Wednesday, August 7th.

==Java==
Due to the frequency and severity of recent Java vulnerabilities, it is strongly advised that '''Java be disabled''' in all browsers on your workstations. If you do require Java, it is recommended to maintain a second, '''separate browser''', solely for the instances which require Java. For instructions on disabling Java on your workstation, please see the following: [[JavaDisableBrowser|How to disable Java]]

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

If you would like to open a support ticket, please contact the UMIACS [[HelpDesk]]

__NOTOC__

Snapshots

2013-07-03T18:10:38Z

Jwebs: Added a more functional explanation of why snapshots are important

Snapshots are a implementation of [http://en.wikipedia.org/wiki/Copy-on-write| copy-on-write] that allows for a file system to quickly take a point-in-time copy of the file system and provide access to the data through a .snapshot directory. Snapshots provide a fast, user-accessible way to recover data that has been accidentally deleted or corrupted within a recent time window -- rather than having to retrieve the data from comparatively slow tape backups. They also help to span the time gap between full backups.

We provide [[Snapshots]] on our [[ONStor]], [[SnapshotsNexenta | Nexenta]] and [[Snapshots:FluidFS | FluidFS]] filers to certain file systems.

Please see [[SnapshotFileSystems]] for a list of our file systems that have snapshots in the department.

==Snapshot Policy==

Our core file systems in the department are on a 4 hour snapshot cycle. Snapshots are taken at,

{| style="color:green; background-color:#ffffcc;" cellpadding="5" cellspacing="0"
| 12am
| 4am
| 8am
| 12pm
| 4pm
| 8pm
|}

We retain up to 8 hourly snapshots, 2 daily snapshots and 1 weekly snapshot.

The [[OpenLAB]] filesystems on which snapshots are available are listed on the [[SnapshotFileSystems]] page.

==Snapshot Restoring==

If you have deleted a file by mistake and you need to get it back, you can use the snapshots directory to recopy the file. This directory can typically be found in your home directory; it will be prepended by a ., so you will need to use the command "ls -a" to find it. It will be one of three:

* .snapshot for the [[ONStor]] (will be removed soon!) / [[Snapshots:NetApp | NetApp]] filers
* .snapshots for the [[Snapshots:FluidFS | FluidFS]] filer
* .zfs/snapshots for the [[SnapshotsNexenta | Nexenta]] / [[Snapshots:ZFS | ZFS]] filers

The inside of one of these will look something like:

[[File:Screenshot-.snapshot_-_bash.png]]

For an example of file restoration, please see [[Snapshots:Example | this page]].

[[Category:Snapshots]]
__NOTOC__

FilesystemDataStorage

2013-01-06T05:51:28Z

Jwebs: Added a section explicitly noting network-attached scratch space

UMIACS recommends that any and all important data be stored on a redundant, backed-up file server. However, there are a number of cases where this is not feasible.

==Windows Local Storage==
Windows hosts at UMIACS store user directories on their local drives. Supported, UMIACS-managed hosts are automatically backed up using the Institute's backup system. Laptops and non-standard hosts are not automatically backed up and be manually backed up by their users.

==UNIX Remote Storage==
We provide storage to each of our users in our UNIX offerings through the [[OpenLAB]] [[NFShomes]].

This home directory,

/nfshomes/username

is backed up nightly into our [[TSM]] backup system. If you wish to have files restored pleased follow these [[TSMRestore|instructions]]. We also now provide [[Snapshots]] on this file system.

Users are given a 2 gigabyte [[Quota]].

==UNIX Local Storage==
UNIX machines use redundant, backed-up network file shares for user directories. Research data storage is also stored on redundant, backed-up network file shares and is generally available under /fs/

All UNIX machines also have local storage available for transitory use. These directories may be used to store temporary, local '''''COPIES''''' of data that is permanently stored elsewhere or as a staging point for output.

These directories may not, '''''under any circumstances''''', be used as permanent storage for unique, important data. UMIACS staff cannot recover damaged or deleted data from these directories and will not be responsible for data loss if they are misused.

Please note that '''/tmp''' in particular is at risk for data loss or corruption as that directory is regularly used by system processes and services for temporary storage.

These directories include:

- /tmp
- /scratch0, /scratch1, /scratch*
- any directory named in whole or in part "tmp", "temp", or "scratch".

==Locally Attached Storage==
Locally attached storage like USB flash drives and USB hard drives are very popular. However, these devices are significantly more vulnerable to data loss or theft than internal or networked data storage. In general, UMIACS discourages the use of locally attached network storage when any other option is available. Please note that these devices are prone to high rates of failure and additional steps should be taken to ensure that the data is backed up and that critical or confidential data is not lost or stolen.

==Network Scratch Storage==
Some labs have network-attached storage dedicated for scratch/temporary storage. These shares are named in the same manner as local scratch or temporary storage (i.e. /fs/lab-scratch or /lab/scratch0 ) and are subject to the same policies as local scratch/tmp (discussed above.)

GettingStarted

2012-12-22T07:46:20Z

Jwebs: /* Questions? */

== [[UMIACS Account]] Introduction ==

UMIACS maintains several different systems and facilities. The basic [[UMIACS Account]] includes access to facilities including:

* [[EMail | E-mail]] (Which is automatically [[BarracudaSpamFirewall | SPAM-Filtered]])
* Several login machines ([[OpenLAB]])
* Basic home directory space
* [[WebSpace|Web]] and [[FileTransferProtocol | FTP]] space
* The [[OpenLAB]] HPC cluster
* [[VPN]], Printing ...

Your UMIACS account actually consists of two system accounts, a Unix Account and Windows (also called your PC) Account. You will use either of these two accounts to access different institute resources and, when you join or are affiliated with different labs, these accounts will be granted access to more lab specific resources.

The goal of the [[OpenLAB]] is to provide a basic computing environment for communications, authoring, file sharing, and general administrative computing. Use of facilities are subject to the [[OpenLAB]]'s Acceptable Use Policy.

== Getting An Account ==

If you do not already have an account, you will need to fill out the account request form located at https://intranet.umiacs.umd.edu/requests/accounts/new/ Please note that for the PI field you will be entering your PI/Professor/Sponsor's account name here at UMIACS. Also indicate any labs you are a member of in the notes field to speed up access to your lab's resources.

Once the form is submitted, it will return to you your initial password for your accounts, please keep it. If you forget your password, you can always come to the UMIACS Helpdesk in 3142 AVW with a photo ID to reset it. Accounts can take anywhere from a few hours to a day for installation, depending on how quickly your PI approves your account.

== Logging into your Account ==

Once your account has been installed, you can use [[SSH]] to login to openlab.umiacs.umd.edu. You can also login to other [[OpenLAB | OpenLab hosts]] or any machines located in the [[OpenLAB]] workstation room 4462 AVW. You will also have login access to most department windows machines as well.

== Account Maintenance ==

There are a few web applications for managing your account:

* [https://intranet.umiacs.umd.edu/chinfo Directory Profile] Change your mail delivery/forward options, change your shells, and setting of office numbers
* [https://intranet.umiacs.umd.edu/cgi-bin/changepass UMIACS Change Password] - Change either your [[Kerberos|UMIACS KRB5 Password (UNIX)]] or your Windows [[ActiveDirectory]] Password.

== Where's my data? ==

Your unix home directory is accessible from most machines from your [[NFShomes]]. You may have different home directories in different locations while using specific labs' machines. Your local data processing is different depending on the operating system of your desktop, please see:

* [[UNIXDataPolicies | Unix/Linux Local Data Policies]]
* [[WindowsDataPolicies | Windows Local Data Policies]]

Your can find out where your web space and FTP space are from [[NASUsers]]. and your lab may have data stored in a [[Subversion]] repository as well. If you need to access your data remotely, we recommend using [[SFTP]]. Many of our labs have specific network attached storage in addition to the default allocation a user is given.

== Questions? ==

Explore the rest of the wiki - if you have any problems or questions, you can contact the technical staff at

[mailto:staff@umiacs.umd.edu staff@umiacs.umd.edu]

Or at the [[HelpDesk|UMIACS Helpdesk]] in A.V. Williams room 3142

GettingStarted

2012-12-22T07:43:11Z

Jwebs: /* UMIACS Account Introduction */ moved a comma

HelpDesk

2012-12-05T19:16:54Z

Jwebs:

If you need additional assistance, please contact the UMIACS Technical Staff.

To start a trouble ticket, log into [[Jira]] at https://intranet.umiacs.umd.edu/jira

UMIACS Technical Staff can also be reached by sending email to [mailto:staff@umiacs.umd.edu staff@umiacs.umd.edu].

If you have a problem with your email or a problem that would be better addressed by speaking to directly to a staffer, you can call or visit our Help Desk,

* Monday - Friday
** 9:00am - 5:00pm

The Help Desk is located in Room [[AVW3142|3142]] of the A.V. Williams Building, and can be reached by phone at 301-405-1775.

UMIACS Account

2012-12-05T16:53:40Z

Jwebs: Added Forgotten Passwords header

== Types of Accounts ==
A UMIACS Account is a collection of distinct account credentials, associated with a unique user, that provide access to various UMIACS systems and related resources.

When a UMIACS Account is first created, three sets of credentials (Windows, UNIX, and Jira) are configured based on the username and password requested via the [https://intranet.umiacs.umd.edu/requests/accounts/new/ UMIACS Account Request] (new users: see [[GettingStarted]].) With the exception of Jira, which requires a full email address, the username is identical for all credentials tied to a UMIACS account.

==== [[Windows]] ====
:Your Windows (aka "PC") account authenticates against our [[ActiveDirectory]] domain and is set when you first create your UMIACS account.
:It controls access for the following resources:
::*Windows computers
::*[[exchange]] e-mail
::*[[VPN]] Authentication

==== [[UNIX]] ====
:Your UNIX (aka "[[Kerberos]]") account authenticates against our Kerberos realm and is set when you first create your UMIACS account.
:It controls access for the following resources:
::*UNIX/Linux computers
::*[[UNIXEmail|IMAP]] e-mail
::*[[ApplicationResource|AR]]-controlled resources (wikis, [[SourceCodeManagement|repositories]], webapps)

==== [[Jira]] ====
:Your Jira username is your full email address. By default, the [[Jira]] account associated with your @umiacs email address authenticates against the kerberos realm. However it is possible to set a separate password for this account. If you change your password through the Jira web interface it will create a '''new''', '''separate''' password, and no longer authenticate against the kerberos realm. Changing your Jira password DOES NOT change any other UMIACS passwords.

:Please note that Jira creates a new account for each new email address it sees (including non-UMIACS addresses like @gmail or @umd.edu addresses.) This occasionally causes some confusion for new users. Please see the [[Jira]] page for further details.

== Changing your password ==
==== Approved Methods ====
There are currently two ways to change your UMIACS passwords:
*Via the web interface tool on the UMIACS Intranet at:
:https://intranet.umiacs.umd.edu/cgi-bin/changepass
*Stop by the [[HelpDesk|UMIACS Helpdesk]], in room 3142 AVW
::If you plan on stopping by the UMIACS Helpdesk, please make sure to bring photo ID
==== Password Requirements ====
#Must be atleast 8 characters in length
#Must have alteast 3 of the following character classes: lower-case letters, upper-case letters, numbers, punctuation, special characters
#Cannot be the same as any of your previous 5 passwords
#Cannot contain a string that is part of your username
==== Off-site or out-of-state users ====
UMIACS Staff requires positive identification before we'll honor a request to change a password. In the event that you are unable to change your password via the methods above, send an email to staff@umiacs.umd.edu detailing your situation. Typically, we'll ask you to get in touch with your PI/advisor, as they should be able to identify you. They will work with staff to reset your password on your behalf, and then communicate it to you in a secure manner.
==== Forgotten Passwords ====
If you have forgotten your Windows or Unix password(s), you will need to stop by the UMIACS Help Desk or follow the Off-site instructions above.

Main Page

2012-11-21T18:45:02Z

Jwebs: TG closed notification

===Closed for the Thanksgiving Holiday===
The UMIACS helpdesk will be closed on Thursday, November 22nd and Friday, November 23rd, in observance of the Thanksgiving holiday and will be open again on Monday, November 26th.

===New Version of Roundcube Webmail Deployed===
UMIACS users using IMAP have a new version of [[Webmail]] available to them. The look-and-feel has been improved from the previous version, but all of your settings have been carried over. New features include a preview pane and the ability to group mail filters together.

===EMET Deployed on all Windows hosts===
We have recently deployed Microsoft's [[Enhanced Mitigation Experience Toolkit]] to all of our supported Windows hosts to help prevent successful exploitation of vulnerabilities in both Microsoft and third party softwares. You should notice a new taskbar icon in the bottom right corner of your screen with a picture of a lock to indicate that EMET is actively working to keep your computer secure.

<endFeed />

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

__NOTOC__

GettingStarted

2012-11-20T20:44:49Z

Jwebs: Removed "OpenLAB Account" wording as this is usually an internal reference.

== [[UMIACS Account]] Introduction ==

UMIACS maintains several different systems and facilities. The basic [[UMIACS Account]] includes access to facilities including:

* [[EMail | E-mail]] (Which is automatically [[BarracudaSpamFirewall | SPAM-Filtered]])
* Several login machines ([[OpenLAB]])
* Basic home directory space
* [[WebSpace|Web]] and [[FileTransferProtocol | FTP]] space
* The [[OpenLAB]] HPC cluster
* [[VPN]], Printing ...

Your UMIACS account actually consists of two system accounts, a Unix Account and Windows (also called your PC) Account. You will use either of these two accounts to access different institute resources, and when you join or are affiliated with different labs, these accounts will be granted access to more lab specific resources.

The goal of the [[OpenLAB]] is to provide a basic computing environment for communications, authoring, file sharing, and general administrative computing. Use of facilities are subject to the [[OpenLAB]]'s Acceptable Use Policy.

== Getting An Account ==

If you do not already have an account, you will need to fill out the account request form located at https://intranet.umiacs.umd.edu/requests/accounts/new/ Please note that for the PI field you will be entering your PI/Professor/Sponsor's account name here at UMIACS. Also indicate any labs you are a member of in the notes field to speed up access to your lab's resources.

Once the form is submitted, it will return to you your initial password for your accounts, please keep it. If you forget your password, you can always come to the UMIACS Helpdesk in 3142 AVW with a photo ID to reset it. Accounts can take anywhere from a few hours to a day for installation, depending on how quickly your PI approves your account.

== Logging into your Account ==

Once your account has been installed, you can use [[SSH]] to login to openlab.umiacs.umd.edu. You can also login to other [[OpenLAB | OpenLab hosts]] or any machines located in the [[OpenLAB]] workstation room 4462 AVW. You will also have login access to most department windows machines as well.

== Account Maintenance ==

There are a few web applications for managing your account:

* [https://intranet.umiacs.umd.edu/chinfo Directory Profile] Change your mail delivery/forward options, change your shells, and setting of office numbers
* [https://intranet.umiacs.umd.edu/cgi-bin/changepass UMIACS Change Password] - Change either your [[Kerberos|UMIACS KRB5 Password (UNIX)]] or your Windows [[ActiveDirectory]] Password.

== Where's my data? ==

Your unix home directory is accessible from most machines from your [[NFShomes]]. You may have different home directories in different locations while using specific labs' machines. Your local data processing is different depending on the operating system of your desktop, please see:

* [[UNIXDataPolicies | Unix/Linux Local Data Policies]]
* [[WindowsDataPolicies | Windows Local Data Policies]]

Your can find out where your web space and FTP space are from [[NASUsers]]. and your lab may have data stored in a [[Subversion]] repository as well. If you need to access your data remotely, we recommend using [[SFTP]]. Many of our labs have specific network attached storage in addition to the default allocation a user is given.

== Questions? ==

Explore the rest of the wiki - if you have any problems or questions, you can contact the technical staff at

[mailto:staff@umiacs.umd.edu staff@umiacs.umd.edu]

Or at the [[HelpDesk|UMIACS Helpdesk]] A.V. Williams room 3142

GettingStarted

2012-11-20T19:49:59Z

Jwebs: /* UMIACS Account Introduction */

== [[UMIACS Account]] Introduction ==

UMIACS maintains several different systems and facilities. The basic [[UMIACS Account]] is called your [[OpenLAB]] Account, which includes access to facilities including:

* [[EMail | E-mail]] (Which is automatically [[BarracudaSpamFirewall | SPAM-Filtered]])
* [[OpenLAB | Several login machines]]
* Basic home directory space
* [[WebSpace|Web]] and [[FileTransferProtocol | FTP]] space
* The [[OpenLAB]] HPC cluster
* [[VPN]], Printing ...

Your [[OpenLAB]] account actually consists of two accounts, a Unix Account and Windows (also called your PC) Account. You will use either of these two accounts to access different institute resources, and when you join or are affiliated with different labs, these accounts will be granted access to more lab specific resources.

The goal of the [[OpenLAB]] is to provide a basic computing environment for communications, authoring, file sharing, and general administrative computing. Use of facilities are subject to the [[OpenLAB]]'s Acceptable Use Policy.

== Getting An Account ==

If you do not already have an account, you will need to fill out the account request form located at https://intranet.umiacs.umd.edu/requests/accounts/new/ Please note that for the PI field you will be entering your PI/Professor/Sponsor's account name here at UMIACS. Also indicate any labs you are a member of in the notes field to speed up access to your lab's resources.

Once the form is submitted, it will return to you your initial password for your accounts, please keep it. If you forget your password, you can always come to the UMIACS Helpdesk in 3142 AVW with a photo ID to reset it. Accounts can take anywhere from a few hours to a day for installation, depending on how quickly your PI approves your account.

== Logging into your Account ==

Once your account has been installed, you can use [[SSH]] to login to openlab.umiacs.umd.edu. You can also login to other [[OpenLAB | OpenLab hosts]] or any machines located in the [[OpenLAB]] workstation room 4462 AVW. You will also have login access to most department windows machines as well.

== Account Maintenance ==

There are a few web applications for managing your account:

* [https://intranet.umiacs.umd.edu/chinfo Directory Profile] Change your mail delivery/forward options, change your shells, and setting of office numbers
* [https://intranet.umiacs.umd.edu/cgi-bin/changepass UMIACS Change Password] - Change either your [[Kerberos|UMIACS KRB5 Password (UNIX)]] or your Windows [[ActiveDirectory]] Password.

== Where's my data? ==

Your unix home directory is accessible from most machines from your [[NFShomes]]. You may have different home directories in different locations while using specific labs' machines. Your local data processing is different depending on the operating system of your desktop, please see:

* [[UNIXDataPolicies | Unix/Linux Local Data Policies]]
* [[WindowsDataPolicies | Windows Local Data Policies]]

Your can find out where your web space and FTP space are from [[NASUsers]]. and your lab may have data stored in a [[Subversion]] repository as well. If you need to access your data remotely, we recommend using [[SFTP]]. Many of our labs have specific network attached storage in addition to the default allocation a user is given.

== Questions? ==

Explore the rest of the wiki - if you have any problems or questions, you can contact the technical staff at

[mailto:staff@umiacs.umd.edu staff@umiacs.umd.edu]

Or at the [[HelpDesk|UMIACS Helpdesk]] A.V. Williams room 3142

Jira

2012-11-20T19:45:19Z

Jwebs:

JIRA is a request and bug tracker that UMIACS uses to provide our [[HelpDesk]] functionality to our users. It can be accessed [https://intranet.umiacs.umd.edu/jira here. ]

It is a web based ticketing system that allows both users and staff to maintain greater control over their tickets and makes communication and resolution of issues a seamless process.

== Using JIRA ==

JIRA automatically generates an account when it receives an email; '''by default, you can log in to JIRA with your UMIACS email address (not username!)''' and UMIACS [[Kerberos]] password.

[[Image:Jira_login.png]]

When you email JIRA, a ticket is created, and the email address your mail was sent from is added as a participant to the ticket -- this means that if you create a ticket using a non-UMIACS email address, you'll have to login to JIRA using that email address to see the ticket.

* Off site users use their email address and can request a password be emailed to them via this [https://intranet.umiacs.umd.edu/jira/secure/ForgotLoginDetails!default.jspa link]. '''(For external users only!)'''

UMIACS Account

2012-11-20T19:42:05Z

Jwebs: /* Types of Accounts */

== Types of Accounts ==
A UMIACS Account, sometimes referred to as an OpenLab Account, is a collection of account credentials that provide access to various UMIACS systems and related resources.

When a UMIACS Account is first created, three sets of credentials are configured. All three are initially set to the password chosen in the [https://intranet.umiacs.umd.edu/requests/accounts/new/ UMIACS Account Request] (new users: see [[GettingStarted]].)

==== Windows ====
:Your Windows (aka "PC") account authenticates against our Windows domain and is set when you first create your UMIACS account.
:It control access for the following resources:
::*Windows computers
::*[[exchange]] e-mail
::*[[VPN]] Authentication

==== [[Kerberos]] ====
:Your UNIX (aka "Kerberos") account authenticates against our Kerberos Server and is set when you first create your UMIACS account.
:It controls access for the following resources:
::*UNIX/Linux computers
::*[[UNIXEmail|IMAP]] e-mail
::*[[ApplicationResource|AR]]-controlled resources (wikis, [[SourceCodeManagement|repositories]], webapps)

==== [[Jira]] ====
:Your Jira username is your full email address. By default, the [[Jira]] account associated with your @umiacs email address authenticates against the kerberos server. However it is possible to set a separate password for this account. If you change your password through the Jira web interface it will create a '''new''', '''separate''' password, and no longer authenticate against the kerberos server. Changing your Jira password DOES NOT change any other UMIACS passwords.

:Please note that Jira creates a new account for each new email address it sees (including non-UMIACS addresses like @gmail or @umd.edu addresses.) This occasionally causes some confusion for new users. Please see the [[Jira]] page for further details.

== Changing your password ==
==== Approved Methods ====
There are currently two ways to change your UMIACS passwords:
*Via the web interface tool on the UMIACS Intranet at:
:https://intranet.umiacs.umd.edu/cgi-bin/changepass
*Stop by the [[HelpDesk|UMIACS Helpdesk]], in room 3142 AVW
::If you plan on stopping by the UMIACS Helpdesk, please make sure to bring photo ID
==== Password Requirements ====
#Must be atleast 8 characters in length
#Must have alteast 3 of the following character classes: lower-case letters, upper-case letters, numbers, punctuation, special characters
#Cannot be the same as any of your previous 5 passwords
#Cannot contain a string that is part of your username
==== Off-site or out-of-state users ====
UMIACS Staff requires positive identification before we'll honor a request to change a password. In the event that you are unable to change your password via the methods above, send an email to staff@umiacs.umd.edu detailing your situation. Typically, we'll ask you to get in touch with your PI/advisor, as they should be able to identify you. They will work with staff to reset your password on your behalf, and then communicate it to you in a secure manner.

UMIACS Account

2012-11-20T19:32:46Z

Jwebs: /* Types of Accounts */

== Types of Accounts ==
When a UMIACS Account is first created, three sets of credentials are configured -- all of which are initially set to the password chosen in the [https://intranet.umiacs.umd.edu/requests/accounts/new/ UMIACS Account Request] (new users: see [[GettingStarted]].)

==== Windows ====
:Your Windows (aka "PC") account authenticates against our Windows domain and is set when you first create your UMIACS account.
:It control access for the following resources:
::*Windows computers
::*[[exchange]] e-mail
::*[[VPN]] Authentication

==== [[Kerberos]] ====
:Your UNIX (aka "Kerberos") account authenticates against our Kerberos Server and is set when you first create your UMIACS account.
:It controls access for the following resources:
::*UNIX/Linux computers
::*[[UNIXEmail|IMAP]] e-mail
::*[[ApplicationResource|AR]]-controlled resources (wikis, [[SourceCodeManagement|repositories]], webapps)

==== [[Jira]] ====
:Your Jira username is your full email address. By default, the [[Jira]] account associated with your @umiacs email address authenticates against the kerberos server. However it is possible to set a separate password for this account. If you change your password through the Jira web interface it will create a '''new''', '''separate''' password, and no longer authenticate against the kerberos server. Changing your Jira password DOES NOT change any other UMIACS passwords.

:Please note that Jira creates a new account for each new email address it sees (such as an @gmail or @cs.umd.edu address.) This occasionally causes some confusion for new users. Please see the [[Jira]] page for further details.

== Changing your password ==
==== Approved Methods ====
There are currently two ways to change your UMIACS passwords:
*Via the web interface tool on the UMIACS Intranet at:
:https://intranet.umiacs.umd.edu/cgi-bin/changepass
*Stop by the [[HelpDesk|UMIACS Helpdesk]], in room 3142 AVW
::If you plan on stopping by the UMIACS Helpdesk, please make sure to bring photo ID
==== Password Requirements ====
#Must be atleast 8 characters in length
#Must have alteast 3 of the following character classes: lower-case letters, upper-case letters, numbers, punctuation, special characters
#Cannot be the same as any of your previous 5 passwords
#Cannot contain a string that is part of your username
==== Off-site or out-of-state users ====
UMIACS Staff requires positive identification before we'll honor a request to change a password. In the event that you are unable to change your password via the methods above, send an email to staff@umiacs.umd.edu detailing your situation. Typically, we'll ask you to get in touch with your PI/advisor, as they should be able to identify you. They will work with staff to reset your password on your behalf, and then communicate it to you in a secure manner.

GettingStarted

2012-11-20T19:20:44Z

Jwebs: /* UMIACS Account Introduction */

== UMIACS Account Introduction ==

UMIACS maintains several different systems and facilities. The basic [[UMIACS Account]] is called your [[OpenLAB]] Account, which includes access to facilities including:

* [[EMail | E-mail]] (Which is automatically [[BarracudaSpamFirewall | SPAM-Filtered]])
* [[OpenLAB | Several login machines]]
* Basic home directory space
* [[WebSpace|Web]] and [[FileTransferProtocol | FTP]] space
* The [[OpenLAB]] HPC cluster
* [[VPN]], Printing ...

Your [[OpenLAB]] account actually consists of two accounts, a Unix Account and Windows (also called your PC) Account. You will use either of these two accounts to access different institute resources, and when you join or are affiliated with different labs, these accounts will be granted access to more lab specific resources.

The goal of the [[OpenLAB]] is to provide a basic computing environment for communications, authoring, file sharing, and general administrative computing. Use of facilities are subject to the [[OpenLAB]]'s Acceptable Use Policy.

== Getting An Account ==

If you do not already have an account, you will need to fill out the account request form located at https://intranet.umiacs.umd.edu/requests/accounts/new/ Please note that for the PI field you will be entering your PI/Professor/Sponsor's account name here at UMIACS. Also indicate any labs you are a member of in the notes field to speed up access to your lab's resources.

Once the form is submitted, it will return to you your initial password for your accounts, please keep it. If you forget your password, you can always come to the UMIACS Helpdesk in 3142 AVW with a photo ID to reset it. Accounts can take anywhere from a few hours to a day for installation, depending on how quickly your PI approves your account.

== Logging into your Account ==

Once your account has been installed, you can use [[SSH]] to login to openlab.umiacs.umd.edu. You can also login to other [[OpenLAB | OpenLab hosts]] or any machines located in the [[OpenLAB]] workstation room 4462 AVW. You will also have login access to most department windows machines as well.

== Account Maintenance ==

There are a few web applications for managing your account:

* [https://intranet.umiacs.umd.edu/chinfo Directory Profile] Change your mail delivery/forward options, change your shells, and setting of office numbers
* [https://intranet.umiacs.umd.edu/cgi-bin/changepass UMIACS Change Password] - Change either your [[Kerberos|UMIACS KRB5 Password (UNIX)]] or your Windows [[ActiveDirectory]] Password.

== Where's my data? ==

Your unix home directory is accessible from most machines from your [[NFShomes]]. You may have different home directories in different locations while using specific labs' machines. Your local data processing is different depending on the operating system of your desktop, please see:

* [[UNIXDataPolicies | Unix/Linux Local Data Policies]]
* [[WindowsDataPolicies | Windows Local Data Policies]]

Your can find out where your web space and FTP space are from [[NASUsers]]. and your lab may have data stored in a [[Subversion]] repository as well. If you need to access your data remotely, we recommend using [[SFTP]]. Many of our labs have specific network attached storage in addition to the default allocation a user is given.

== Questions? ==

Explore the rest of the wiki - if you have any problems or questions, you can contact the technical staff at

[mailto:staff@umiacs.umd.edu staff@umiacs.umd.edu]

Or at the [[HelpDesk|UMIACS Helpdesk]] A.V. Williams room 3142

UMIACS Account

2012-11-20T19:15:30Z

Jwebs: /* Types of Accounts */

== Types of Accounts ==
When a UMIACS Account is first created, three sets of credentials are set up -- all of which are initially set to the password chosen in the [https://intranet.umiacs.umd.edu/requests/accounts/new/ UMIACS Account Request] (new users: see [[GettingStarted]].)

==== Windows ====
:This password authenticates against our Windows domain and is set when you first create your UMIACS account.
:It control access for the following resources:
::*Windows computers
::*[[exchange]] e-mail
::*[[VPN]] Authentication

==== [[Kerberos]] ====
:This password authenticates against our Kerberos Server and is set when you first create your UMIACS account.
:It controls access for the following resources:
::*UNIX/Linux computers
::*[[UNIXEmail|IMAP]] e-mail
::*[[ApplicationResource|AR]]-controlled resources (wikis, [[SourceCodeManagement|repositories]], webapps)

==== [[Jira]] ====
:By default [[Jira]] authenticates against the kerberos server, however it is possible to set Jira to it's own separate password. If you change your password through the Jira web interface it will create a '''new''', '''separate''' password, and no longer authenticate against the kerberos server. Changing your Jira password DOES NOT change any other UMIACS password.

== Changing your password ==
==== Approved Methods ====
There are currently two ways to change your UMIACS passwords:
*Via the web interface tool on the UMIACS Intranet at:
:https://intranet.umiacs.umd.edu/cgi-bin/changepass
*Stop by the [[HelpDesk|UMIACS Helpdesk]], in room 3142 AVW
::If you plan on stopping by the UMIACS Helpdesk, please make sure to bring photo ID
==== Password Requirements ====
#Must be atleast 8 characters in length
#Must have alteast 3 of the following character classes: lower-case letters, upper-case letters, numbers, punctuation, special characters
#Cannot be the same as any of your previous 5 passwords
#Cannot contain a string that is part of your username
==== Off-site or out-of-state users ====
UMIACS Staff requires positive identification before we'll honor a request to change a password. In the event that you are unable to change your password via the methods above, send an email to staff@umiacs.umd.edu detailing your situation. Typically, we'll ask you to get in touch with your PI/advisor, as they should be able to identify you. They will work with staff to reset your password on your behalf, and then communicate it to you in a secure manner.

UMIACS Account

2012-11-20T19:13:56Z

Jwebs: /* Types of Accounts */

== Types of Accounts ==
When a UMIACS Account is first created, three sets of credentials are set up -- all of which are initially set to the password chosen in the [https://intranet.umiacs.umd.edu/requests/accounts/new/ UMIACS Account Request].

==== Windows ====
:This password authenticates against our Windows domain and is set when you first create your UMIACS account.
:It control access for the following resources:
::*Windows computers
::*[[exchange]] e-mail
::*[[VPN]] Authentication

==== [[Kerberos]] ====
:This password authenticates against our Kerberos Server and is set when you first create your UMIACS account.
:It controls access for the following resources:
::*UNIX/Linux computers
::*[[UNIXEmail|IMAP]] e-mail
::*[[ApplicationResource|AR]]-controlled resources (wikis, [[SourceCodeManagement|repositories]], webapps)

==== [[Jira]] ====
:By default [[Jira]] authenticates against the kerberos server, however it is possible to set Jira to it's own separate password. If you change your password through the Jira web interface it will create a '''new''', '''separate''' password, and no longer authenticate against the kerberos server. Changing your Jira password DOES NOT change any other UMIACS password.

== Changing your password ==
==== Approved Methods ====
There are currently two ways to change your UMIACS passwords:
*Via the web interface tool on the UMIACS Intranet at:
:https://intranet.umiacs.umd.edu/cgi-bin/changepass
*Stop by the [[HelpDesk|UMIACS Helpdesk]], in room 3142 AVW
::If you plan on stopping by the UMIACS Helpdesk, please make sure to bring photo ID
==== Password Requirements ====
#Must be atleast 8 characters in length
#Must have alteast 3 of the following character classes: lower-case letters, upper-case letters, numbers, punctuation, special characters
#Cannot be the same as any of your previous 5 passwords
#Cannot contain a string that is part of your username
==== Off-site or out-of-state users ====
UMIACS Staff requires positive identification before we'll honor a request to change a password. In the event that you are unable to change your password via the methods above, send an email to staff@umiacs.umd.edu detailing your situation. Typically, we'll ask you to get in touch with your PI/advisor, as they should be able to identify you. They will work with staff to reset your password on your behalf, and then communicate it to you in a secure manner.

UMIACS Account

2012-11-20T18:59:02Z

Jwebs: /* Changing your password */

UMIACS Account

2012-11-20T18:57:12Z

Jwebs: Removing Acnt sec/comm pending staff revise

UMIACS Account

2012-11-20T18:54:14Z

Jwebs: /* Changing your password */

== Types of Accounts ==
When your UMIACS account is first created there are two password that are initially set.

==== Windows ====
:This password authenticates against our Windows domain and is set when you first create your UMIACS account.
:It control access for the following resources:
::*Windows computers
::*[[exchange]] e-mail
::*[[VPN]] Authentication

==== [[Kerberos]] ====
:This password authenticates against our Kerberos Server and is set when you first create your UMIACS account.
:It controls access for the following resources:
::*UNIX/Linux computers
::*[[UNIXEmail|IMAP]] e-mail
::*[[ApplicationResource|AR]]-controlled resources (wikis, [[SourceCodeManagement|repositories]], webapps)

==== [[Jira]] ====
:By default [[Jira]] authenticates against the kerberos server, however it is possible to set Jira to it's own separate password. If you change your password through the Jira web interface it will create a '''new''', '''separate''' password, and no longer authenticate against the kerberos server. Changing your Jira password DOES NOT change any other UMIACS password.

== Changing your password ==
There are currently two ways to change your UMIACS passwords:
*Via the web interface tool on the UMIACS Intranet at:
:https://intranet.umiacs.umd.edu/cgi-bin/changepass
*Stop by the [[HelpDesk|UMIACS Helpdesk]], in room 3142 AVW
::If you plan on stopping by the UMIACS Helpdesk, please make sure to bring photo ID
==== Password Requirements ====
#Must be atleast 8 characters in length
#Must have alteast 3 of the following character classes: lower-case letters, upper-case letters, numbers, punctuation, special characters
#Cannot be the same as any of your previous 5 passwords
#Cannot contain a string that is part of your username
==== Off-site or out-of-state users ====
UMIACS Staff requires positive identification before we'll honor a request to change a password. In the event that you are unable to change your password via the methods above, send an email to staff@umiacs.umd.edu detailing your situation. Typically, we'll ask you to get in touch with your PI/advisor, as they should be able to identify you. They will work with staff to reset your password on your behalf, and then communicate it to you in a secure manner.

== Account Security and Communications from Staff ==
Keeping your account secure is a high priority for UMIACS Staff, and we need your help. In today's digital environment, it is often challenging to distinguish phishing attempts and scams from legitimate email. Please note that:
#UMIACS Staff will never ask you for your password and you should never share your username and password with anyone.
#You should '''NEVER''' transmit ANY password via email or other insecure medium.
#If you are ever uncertain about the legitimacy of an email from staff, please do not hesitate to contact the [[HelpDesk]] for verification.

'''In the event of a compromised account''' or some other situation where staff might need to contact you via email and instruct you to change your password, the request will not deviate from the instructions provided above -- namely, we will ask you to change your password via the UMIACS Intranet, in person, or via a trusted and authoritative proxy (your PI.)

UMIACS Account

2012-11-20T18:53:33Z

Jwebs: Some basic tweaks, plus the addition of sections on out-of-state password changes and basic account/comm security.

== Types of Accounts ==
When your UMIACS account is first created there are two password that are initially set.

==== Windows ====
:This password authenticates against our Windows domain and is set when you first create your UMIACS account.
:It control access for the following resources:
::*Windows computers
::*[[exchange]] e-mail
::*[[VPN]] Authentication

==== [[Kerberos]] ====
:This password authenticates against our Kerberos Server and is set when you first create your UMIACS account.
:It controls access for the following resources:
::*UNIX/Linux computers
::*[[UNIXEmail|IMAP]] e-mail
::*[[ApplicationResource|AR]]-controlled resources (wikis, [[SourceCodeManagement|repositories]], webapps)

==== [[Jira]] ====
:By default [[Jira]] authenticates against the kerberos server, however it is possible to set Jira to it's own separate password. If you change your password through the Jira web interface it will create a '''new''', '''separate''' password, and no longer authenticate against the kerberos server. Changing your Jira password DOES NOT change any other UMIACS password.

== Changing your password ==
There are currently two ways to change your UMIACS passwords:
*Via the web interface tool on the UMIACS Intranet at:
:https://intranet.umiacs.umd.edu/cgi-bin/changepass
*Stop by the [[HelpDesk|UMIACS Helpdesk]], in room 3142 AVW
::If you plan on stopping by the UMIACS Helpdesk, please make sure to bring photo ID
==== Password Requirements ====
#Must be atleast 8 characters in length
#Must have alteast 3 of the following character classes: lower-case letters, upper-case letters, numbers, punctuation, special characters
#Cannot be the same as any of your previous 5 passwords
#Cannot contain a string that is part of your username
==== Off-site or out-of-state users ====
UMIACS Staff requires positive identification before we'll honor a request to change a password. In the event that you are unable to change your password via the methods above, send an email to staff@umiacs.umd.edu detailing your situation. Typically, we'll ask you to get in touch with your PI/advisor, as they should be able to visually and aurally identify you. They will work with staff to reset your password on your behalf, and then communicate it to you in a secure manner.

== Account Security and Communications from Staff ==
Keeping your account secure is a high priority for UMIACS Staff, and we need your help. In today's digital environment, it is often challenging to distinguish phishing attempts and scams from legitimate email. Please note that:
#UMIACS Staff will never ask you for your password and you should never share your username and password with anyone.
#You should '''NEVER''' transmit ANY password via email or other insecure medium.
#If you are ever uncertain about the legitimacy of an email from staff, please do not hesitate to contact the [[HelpDesk]] for verification.

'''In the event of a compromised account''' or some other situation where staff might need to contact you via email and instruct you to change your password, the request will not deviate from the instructions provided above -- namely, we will ask you to change your password via the UMIACS Intranet, in person, or via a trusted and authoritative proxy (your PI.)

UMIACS Account

2012-11-20T18:06:01Z

Jwebs: /* Jira */ link edits

UMIACS Account

2012-11-20T17:51:27Z

Jwebs: /* Kerberos */

UMIACS Account

2012-11-20T17:50:46Z

Jwebs: /* Windows */ link additions

SecureShellTunneling

2012-07-31T17:18:28Z

Jwebs: /* Socks Proxy */ Wording of the performance aside was mangled

Main Page

2012-07-03T17:25:29Z

Jwebs: Closed for Independence Day

===UMIACS Help Desk Closed on July 4th, 2012===
The UMIACS Help Desk (and the University) will be closed on July 4th, 2012 in observance of Independence Day. The Help Desk will reopen on July 5th at 9AM. Have a great 4th!

===EMET Deployed on all Windows hosts===
We have recently deployed Microsoft's [[Enhanced Mitigation Experience Toolkit]] to all of our supported Windows hosts to help prevent successful exploitation of vulnerabilities in both Microsoft and third party softwares. You should notice a new taskbar icon in the bottom right corner of your screen with a picture of a lock to indicate that EMET is actively working to keep your computer secure.

===Matlab R2012A now available===
Matlab R2012A (release 7.14) is now available. Please see [[Matlab]] for information on availability.

<endFeed />

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

Programming

2012-03-12T18:43:46Z

Jwebs: Added a page about Python modules and environments

* C/C++
** [[CCompilers|C/C++ Compilers]]
** [[CDebuggers|C/C++ Debuggers]]
** [[COtherTools|C/C++ Other Tools]]
* Java
** [[JavaVersions|Java Versions]]
** [[JavaDevelEnvironment|Java Development Environment]]
* Perl
** [[PerlVersions|Perl 5 Versions]]
** [[PerlDevelEnvironment|Perl Development Environment]]
** [[PerlModules|Perl Missing Modules]]
* Python
** [[PythonVersions | Python Versions]]
** [[PythonModDev | Python Modules and Development Environment]]
* VB/VC/.NET
** [[MSVisualDevelopment|Development Environment]]
* Others
** [[ACL|Alegro Common Lisp]]

SecureShell

2012-02-20T17:27:52Z

Jwebs: /* Passwordless SSH with SSH Keys */ clarification. this section contains info on both passwordless and passphrase ssh keys, users were confused by flow.

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

==Connecting to an SSH Server==
Under Linux and 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.

All UMIACS Windows hosts are installed with SSH Secure Shell Client. Alternatively, users can install these software on their personal machines:

* [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 Linux and Mac OS X, the following command from a terminal will connect a client computer to the UMIACS [[OpenLAB]] using X11 Forwarding.
# ssh '''-Y''' 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].

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, shown below. 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.

==SSH Keys (and Passwordless SSH)==

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 [http://en.wikipedia.org/wiki/Key_pair 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!''' <pre> # ssh-keygen -N ""</pre>
#: Alternatively, 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.<pre> # ssh-keygen</pre>
#This will produce two files, '''id_rsa''' and '''id_rsa.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_rsa ~/.ssh
# chmod 600 ~/.ssh/id_rsa
# touch ~/.ssh/authorized_keys2
# chmod 600 ~/.ssh/authorized_keys2
# cat id_rsa.pub >> ~/.ssh/authorized_keys2
# rm id_rsa.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_rsa''') 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]

SecureShellTunneling

2011-10-21T08:38:59Z

Jwebs: Added a little something for Windows users

SecureShell

2011-10-21T08:28:46Z

Jwebs: /* X11 Forwarding */ removed reference to RHEL versions here too

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

==Connecting to an SSH Server==
Under Linux and 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 Linux and Mac OS X, the following command from a terminal will connect a client computer to the UMIACS [[OpenLAB]] using X11 Forwarding.
# ssh '''-Y''' 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

2011-10-21T08:27:19Z

Jwebs: /* Connecting to an SSH Server */ removed reference to specific versions of RHEL since adding 6 would have made an unnecessary list longer

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

==Connecting to an SSH Server==
Under Linux and 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 '''-Y''' 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]

LabFacilities

2011-08-30T19:56:39Z

Jwebs: updated clip link

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

Main Page

2011-07-07T16:16:39Z

Jwebs: Removed Holiday Announcement (holiday has passed)

__NOTOC__
==Anouncements==
<startFeed />

===New UNIX Print System===
We are pleased to announce the immediately available [[CUPS]] print system for our UNIX (rhel/ubuntu) users. Please contact staff@umiacs.umd.edu with any issues.

<endFeed />

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