The proxy itself uses a combination of TCP and UDP. TCP is used server->proxy, and UDP is used proxy->client. The data sent via UDP is standard quakeworld client protocols, and in it's basic form is compatable with any quakeworld client available. The TCP server->proxy stream carrays an MVD stream. This is the same format of stream that is stored in the MVD (multi-view demo) created by certain quakeworld servers such as MVDSV and FTE. The proxy itself uses a combination of TCP and UDP.

I upgraded to OpenSSH 3.1 and X11 forwarding stopped working. Starting with OpenSSH 3.1, the sshd x11 forwarding server listens on localhost by default; see the sshd X11UseLocalhost option to revert to prior behaviour if your older X11 clients do not function with this configuration. In general, X11 clients using X11 R6 should work with the default setting. Some vendors, including HP, ship X11 clients with R6 and R5 libs, so some clients will work, and others will not work.

A lot! Almost all variants of TCP, several forms of multicast, wired networking, several ad hoc routing protocols and propagation models (but not cellular phones), data diffusion, satellite, and other stuff. See the documentation (described above) for details, or download ns and look.

Chord communicates with peers using standard RPCs. The specific protocols are defined using XDR and can be viewed via our WebCVS interface at http://cvs.pdos.lcs.mit.edu/cvs/sfsnet/svc/. However, these definitions do not specify the semantics in detail --- if you want to implement Chord, you may be better off doing it without seeking compatibility with our implementation.

Yes! ssh (secure shell) is available on Nyx1, Nyx2 and Nyx3 for all validated users. Nyx and nyx10 cannot currently withstand the load of users using ssh. So ssh is restricted to administrators. Yes, this means Nyx is awfully busy (if it takes more than a minute to search through a 200k file, that's a slooooow system). Think of it as a built in limit to how busy Nyx gets -- it refuses to let other people on to make it even busier.

For answers to questions about your specific situation or for other technical assistance, please see our Support page.

The IRBs main concern is the protection of human participants. Therefore, we are concerned about recruitment methods, study procedures as it relates to the participants, confidentiality, the consent procedure, and the benefits of the study to the participants and to generalizable knowledge (risk-benefit ratio). For more information, please see the section "Informed Consent".

SSH 2.3 and earlier versions contain a flaw in their HMAC implementation. Their code was not supplying the full data block output from the digest, and instead always provided 128 bits. For longer digests, this caused SSH 2.3 to not interoperate with OpenSSH. OpenSSH 2.2.0 detects that SSH 2.3 has this flaw. Recent versions of SSH will have this bug fixed. Or you can add the following to SSH 2.3 sshd2_config.

When Sun did its initial review of the options available there were two primary reasons why the HTTPS direction was selected: The long term goal is to EOL FTP as a transport mechanism. Until FTP is EOL'd, FTP and HTTPS will coexist and customers will have the option of choosing the method they prefer. SSL-FTP is not yet an accepted standard by the Internet Engineering Task Force (ietf.org) as it is still a draft specification.

SNMP uses 161/udp for general purpose (request/response) communications, and 162/udp for traps. Additionally, the SNMP multiplexing protocol (smux, defined in RFC1227 http://www.ietf.org/rfc/rfc1227.txt) uses 199/tcp. Another SNMP extension, the AgentX protocol (RFC2741, http://www.ietf.org/rfc/rfc2741.txt) uses 705/tcp.

Our server/switch supports G711 and G729 codecs. We run on SIP protocol, and support T-38 for faxing.

SSH and Telnet are "shell" interfaces for your account. They allow you to manage the files on your account using a command-shell environment, where commands are typed. For example, 'ls' produces a directory listing.

You may use any SSH client you wish. Use of SSH is certainly not restricted to our recommended software. There are dozens of high quality SSH clients to choose from, all of which have their benefits and downsides.

Ssh has been freely available in the Unix environment, and almost certainly will remain to be so in future. Tatu Ylönen, the original author of ssh, has started a company, SSH Communications Security Oy, that will provide commercial support and licenses for ssh. This company is working together with Data Fellows, who are the sole contact for licensing ssh. More information can be found at http://www.europe.datafellows.com/ and http://www.ssh.fi/ .

Stock rdist 6.1.0 does not work together with ssh, due to bugs in it. The 6.1.1 versions of rdist and later versions are believed to work. If you use rdist, don't forget to compile the path to ssh into it. Alternatively, you may specify the -P option so rdist uses ssh, and not rsh. If you use password authentication with rdist 6.1.2 or 6.1.3, you will need to apply the following patch to rdist to make it work: --- src/rshrcmd.c.orig Tue Jun 11 16:51:21 1996 +++ src/rshrcmd.

The Java CoG Kit abstractions have an SSH provider. This allows ssh-enabled remote job executions and scp-enabled file transfers. The SSH provider supports two modes of security: PublicKey authentication and Password authentication.

If you are a new or returning user, and need assistance downloading files using SSH, click here. For further assistance, please contact the SCD Technical Consulting Group . When contacting the SCD consultants, ensure that your subject line says something like "moving files to a remote site."