SafeTP operates by installing a transparent proxy in the Windows networking stack which detects outgoing FTP connections from any Windows FTP client, and silently secures them using modern cryptographic techniques (the server must also support SafeTP in order for a secure connection to be succesfully established). SafeTP is 100% compatible with existing (insecure) FTP servers, and will operate in an insecure mode if the server does not yet support the SafeTP protocol. One key feature of the SafeTP client proxy is that it was designed to be completely transparent to the client FTP application. This way, users can reap the benefits of FTP security, while continuing to use their existing FTP software.
You can find information about using the various SafeTP products on their respective product pages, linked from the main page.
Information about SafeTP:
- Detailed system diagram
- How is SafeTP better than existing systems?
- MD5 checksums for SafeTP software releases
- Known problems/issues in the client and server
- Troubleshooting SafeTP
- SafeTP client FAQ
- SafeTP and Firewalls
- Over-the-wire protocol and cryptographic info: X-SafeTP1 (Also see RFC 2228.)
- White Paper: Bonachea, Dan and McPeak, Scott. "SafeTP: Transparently Securing FTP Network Services", UCB Tech Report CSD-01-1152, February 2001. pdf (100 KB)
- White Paper: Bonachea, Dan and McPeak, Scott. "SafeTP: Secure, Transparent, Interoperable FTP", 1998 (unpublished) ps (800 KB) pdf (1.7 MB)
- Poster: SafeTP: Securing File Transfer Using Transparent Proxies ps (80 KB)
Related Links:
- Winsock 2 SPI Developer's Kit
- RFC 959, the specification for FTP
-
RFC 2228, FTP Security Extensions specification
- Mark Horowitz's page on FTP Security Extensions
- Our internet draft concerning updates to RFC 2228
