Offsite Services

Off-site Services

Off-site Calendar Access

Access to the JLab Calendar application is provided for off-site access via our web based calendar client. Please see the Jlab Calendar web pages for details concerning the use and configuration of this system.

Off-site Email Access

JLab email accounts can be accessed from off-site by using our supported web based email client. Additional off-site email informationand options can be found by reviewing the contents of the JLab Remote Email Access web page.

Off-site File transfers:

As of February 25, 2003, the lab does not allow any file transfer method that utilizes clear-text password authentication with the exception of anonymous FTP. To facilitate off-site file transfers, the computer center provides several securely authenticated services via the ftp.jlab.org system. Full details for these services can be found on the Off-Site File Transfer Facilities webpage and are listed briefly below:

BBFTP - for arbitrary disk files on the /work or /cache file systems, use either bbftp that is secure and does parallel transfers to maximize throughput,
SCP - for copying individual files via ssh protocol
SafeTP - a secure replacement for traditional ftp services
SFTP - a secure replacement which tunnels ftp over ssh.
SRM - a grid-enabled Storage Resource Manager, providing transparent access, that is secure and attempts to fully utilize available network bandwidth.

When required, anonymous ftp service is available for read-only access.

Off-site Login sessions:

Logins from off-site are only available using ssh and only through dedicated login servers - login1.jlab.org, login2.jlab.org (or via generic name jlab.org). In addition all remote logins to these machines must be validated with a password; we do not allow RSA/DSA keys since they can be setup to use a blank or null passphrase. From these machines you may login to any other machine on site. No other systems are permitted to provide direct login access to the outside. You may set up ssh to connect internally in a single command as shown in the examples below, but you will be asked for your password at each step. You can however, set up your internal ssh configuration to have a blank passphrase.

Examples:

ssh -t login1.jlab.org ssh jlabs1

ssh -t jlab.org ssh jlabh1

ssh -f -t login2.jlab.org linxone xterm -name linxone

Refer to http://cc.jlab.org/docs/services/unix/login_server.html for more details on the login systems.

Details regarding offsite Windows PC X application access can be found on the Accessing X Applications from Offsite Windows PC's webpage.

Windows login

Instructions for remotely accessing Windows-based machines can be found here.

Remote CVS:

This service is provided on cvs.jlab.org and makes use of ssh. The following is all that is needed for a remote CVS client:

setenv CVS_RSH ssh

setenv CVSROOT username@cvs.jlab.org:/group/xxx/CVS

Then proceed as normal (e.g. cvs checkout mystuff etc) - you may be prompted for a password, which is your usual jlab login password. In the above example replace "username" with your user id, and replace "/group/xxx/CVS" with the full pathname of your CVS repository.

Anonymous CVS Access:

The Computer Center is pleased to provide anonymous access to CVS repositories via the Internet. If your project uses CVS to manage its source code, you can now allow others to download the latest versions from your repository. Our anonymous CVS service is read-only, so others can connect to the repository and check out code, but will not be able to commit changes. Full access to the code by your own developers is unaffected. If you would like to set up anonymous CVS access to your repository, please contact the helpdesk (helpdesk@jlab.org).

This document is maintained by {helpdesk@jlab.org}