On Fri, 15 Nov 2002, Eran Tromer wrote: > Having peeked at the TCFS sourcecode and scanned their 95-slides > presentation > (http://www.tcfs.it/docs/linux-expo-2001/Diapositiva1.JPG.html): > > TCFS encrypts at the file block level, and the protocol for sending file > blocks back and forth is plain NFS, so an eavesdropper knows which block > of which file you access in each operation. The filenames aren't > visible, but their lengths, and sizes and directory hierarchy are. In > many cases, this would leave little room for imagination.
1. does this system allow easy abuses of ip spoofing? (as in the case of NFS?) 2. Another thing to consider: network throughput: the more content encryption there is, the more garbage is transmitted on the network. This reduces the actual throuput of the transfer (I ignore the cpu time spent on encryption/decryption). -- Tzafrir Cohen mailto:[EMAIL PROTECTED] http://www.technion.ac.il/~tzafrir ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
