Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Our UNIX systems, including our clusters, require the use of the Secure Shell Protocol (SSH) protocol in order to login. SSH provides a terminal interface so that you can type commands, and interact with the computer, although with additional software and setup you can also run UNIX graphical programs. SSH is intended to provide secure connections, so that you can be sure that it is safe to provide your password, and also so that you can be sure that no one is able to intercept your network traffic and spy on you.

Mostly you should be able to just use SSH without worrying too much about the encryption details. However, you do need to be aware of some issues that might arise when you first connect to the remote system. Each SSH server (the software running on the remote computer) will generate a unique host encryption key which it then uses with your client to transfer a key which will be used for that particular log in session. Until that session key is in place you are vulnerable to a so-called "Man in the Middle Attack" in which an attacker intercepts your packets, and sends them to the remote system. When the remote system responds, the attacker system will take the response, and send it back to your computer. During this time it is able to make copies of the network traffic, and reconstruct the conversation. You would not be aware of this, and SSH will not be able to detect that this has occurred. For this reason, SSH will record the host key for a given system. If the host key changes for some reason, you'll be warned about this and you should not continue logging in without contacting us to see why the key may have changed. Additionally the first time you log in to a system, you will be asked that the host key presented by the server is the actual key for the server. For the maximum amount of security you should confirm that the correct key has been presented, and for this reason the keys of CCBB maintained servers are listed below.


    * ceres:

      openssh md5:  6b:68:2b:d1:58:e2:ed:8a:5a:d1:35:f7:71:bf:79:76
      bubblebabble: xihom-gunag-zuzar-myzor-fifem-myzut-ryper-zinab-humec-gomen-taxyx

    * chencluster:

      openssh md5:  98:b8:7b:5c:80:93:60:97:47:6f:08:75:9b:b1:8c:4c
      bubblebabble: xocor-byrik-kurup-ronub-migom-vamar-cidim-firav-tysef-copyt-suxux

    * dacha:

      openssh md5:  4e:08:9a:de:2f:ab:17:8a:41:73:cd:fb:64:41:2f:cd
      bubblebabble: xocig-cazan-tevab-zalys-dopan-kynef-zobon-syfas-kevad-vysor-haxyx

    *

      files:
      openssh md5:  1a:86:e8:12:a8:65:0f:2d:eb:b7:eb:ca:40:f9:e7:d5
      bubblebabble: xetic-bodep-kupen-pesak-kobik-vacym-dypiz-vusyn-nysab-buted-rexux

    * genomes:

      openssh md5:  55:2d:23:28:9d:36:b7:61:d2:31:9c:87:a9:48:73:b0
      bubblebabble: ximet-susah-mabub-delik-dudyh-lufyg-semaz-zetys-migyg-dydam-vuxax

    * kremlin:

      openssh md5:  22:b3:8a:76:70:39:de:7d:0a:d6:fb:d6:02:da:4f:69
      bubblebabble: xemaf-fecup-tideb-pyzum-gipel-vacad-veles-popar-dimab-kihah-loxox

    * phylocluster:

      openssh md5:  4f:df:26:ca:fb:8d:22:64:db:bf:2a:3a:8a:c7:df:85
      bubblebabble: xobod-hybyz-temup-lasim-tovip-cufed-rimaf-sukud-zebos-hevyk-lixex

Eventually you will want to download a good SSH client for your computer. Some good choices are are Putty for Windows users, and JellyfiSSH for Mac users. Both are available via Bevoware. Until you download a client of your own, you can also use our web based SSH client by clicking on one of the links belo Note that using this applet requires that it be allowed to connect a host other than the webserver which it was downloaded from. Normally

phylocluster

  • No labels