1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
|
- sendfile can send any file at any size reliable, secure and effecient
from any user A to any user B on the Internet.
- sendfile uses a (gzip or bzip2) compressed link for transfers.
- sendfile can automaticly guess the correct file type (binary, source,
text) and will translate EOL markers and the character set, e.g. German
Umlauts.
- sendfile has an integrated resend facility: if a transfer has been
interrupted by any reason, the next transfer will continue at the last
sent byte.
- sendfile can transfer whole directory trees.
- sendfile has integrated pgp support for signing and encryption.
- sendfile can delete previous sent files (as long as they are in the
recipient's spool)
- sendfile can truly send asynchronous, you don't need a permanent
internet connection. A special sendfile spool daemon will retry every xx
minutes to deliver the files.
- With the fetchfile/O-SAFT extension you can retrieve files from a
remote host. This is similar to POP-mail, but with secure pgp
authentification.
- You can annotate the files you send with a comment.
- With the addon program sendmsg you can send short messages directly to
the recipients terminal, this works like write(1), but net-wide.
- You can bounce (forward) files directly from the spool.
- You can set up a forward address. Unless like mail, this means that
new files will not sent first to you, but directly to the forward address.
- The receive program warns you for dangerous files, like .rhosts.
- The sendfile daemon has various configuration possibilities to prevent a
denial of service attack: max # of files, min free disk space, "kill
files", expire dates, log all transactions, refuse all non-signed files etc.
- The administrator can deny SAFT services for certain users or do the
inverse: allow it only for special users.
- sendfile has NFS and AFS support.
- SAFT supports Unicode.
- sendfile runs so far on AIX, BSDI, Convex-OS, Digital Unix,
FreeBSD, HP-UX, IRIX, Linux, NeXTstep/Mach, OSF/1, SunOS 4, SunOS 5
(Solaris-2) and Ultrix. Implementations for Windows NT and OS/2 will be
released in the next future.
- SAFT uses the tcp port 487, which has been reserved by the IANA
(Internet Assigned Numbers Authority). An SAFT-RFC is in preparation
phase.
|
