Self-certifying File System
![]() | This article is actively undergoing a major edit for a little while. To help avoid edit conflicts, please do not edit this page while this message is displayed. This page was last edited at 02:34, 23 December 2006 (UTC) (18 years ago) – this estimate is cached, . Please remove this template if this page hasn't been edited for a significant time. If you are the editor who added this template, please be sure to remove it or replace it with {{Under construction}} between editing sessions. |
In computing, Self-certifying File System (SFS) is a global and decentralized, distributed file system, while also providing transparent encryption of communications as well as authentication. The SFS client implements the network file system protocol for communicating with the operating system, and thus can work anywhere where NFS is supported.
The primary motivation behind the file system is to address the shortcomings of hardwired, administratively configured network file systems, and various remote file transfer protocols. For example, one could store all their files on a single remote server, and access the same files transparently from any location as if they were stored locally, without any special privileges or administrative cooperation. The file system will always be found in the same location, and is implicitly authenticated as its path includes the public-key fingerprint of the server. On Unix-like systems, are usually located at /sfs/location:hostID
See also
External links
- [[1]]