readme.txt

伯克利做的SFTP安全文件传输协议

readme.txt
Readme for SafeTP

What is SafeTP?

  SafeTP is a secure alternative to normal FTP (File Transfer
  Protocol).  FTP is insecure, because usernames and passwords are
  transmitted in the clear over the network.  Anyone between you and
  the server can read get your password.

  SafeTP improves the situation by encrypting (among other things)
  your username and password, before they are transmitted over the
  network.  You can optionally also encrypt the data you're sending.

How to use SafeTP on Windows?

  See the web page: http://safetp.cs.berkeley.edu

How to use SafeTP on Unix?

  Assuming your network administrator has already installed the server
  daemon (see install.txt):

    % sftpc hostname [port]

  Inside sftpc, you can get help via the "help" command.

How to use SafeTP on Mac?

  There is no Mac port right now.  :(

Who made this thing?

  Dan Bonachea and Scott McPeak wrote the initial SafeTP prototype
  in conjunction with Computer Science 262, at U.C. Berkeley, Fall
  1998, taught by Prof. Eric Brewer.  Since then, Dan and Scott have
  continued to work on and improve SafeTP.

More info?

  Web page: http://safetp.cs.berkeley.edu

  Command documentation:
    sftpc: http://safetp.cs.berkeley.edu/sftpc.html
    sftpd: http://safetp.cs.berkeley.edu/sftpd.html

  Useful documentation in source tree
    compile.txt   - instructions for compiling
    install.txt   - server installation
    readme.txt    - this file
    trouble.txt   - troubleshooting tips
    warnings.txt  - expected compile warnings (g++)

  Less-useful docs
    bugs.txt      - known bugs
    hclnotes.txt  - few notes on using with Hummingbird Inetd
    holes.txt     - blurbs of known security holes
    modules.txt   - module-by-module description (somewhat dated)
    patches.txt   - some OS header changes (only the HP-UX one is critical)
    ports.txt     - summary of relevant port numbers
    protocol.txt  - the over-the-wire protocol

  Scripts in 'sc' directory of source tree
    basictests    - post-compile tests I run
    copybins      - copy binares from build dir
    copycheck     - verify copyright and terms-of-use string
    copycheckmany - foreach loop for copycheck
    hup.inetd     - send HUP to inetd
    install       - primary installation script
    mkpubkeytxt   - create public.key.txt
    prepend       - prepend a line of text to a file
    psall         - list all processes
    runsftpd      - run sftpd as non-root on unprivileged port
    runtests      - run several of the test programs
    uninstall     - uninstall script