99:. For example, with SFS, one could store all their files on a single remote server, and access the same files securely and transparently from any location as if they were stored locally, without any special privileges or administrative cooperation (other than running the SFS client daemon). Available file systems will be found at the same path regardless of physical location, and are implicitly authenticated by their path names — as they include the
110:
clients have to rely on the server for file system security policies, and NFS servers have to rely on the client computer for authentication. This often complicates security, as one compromised computer could breach the security of the entire organization. The NFS and SMB protocols also do not by
40:. It aims to be the universal distributed file system by providing uniform access to any available server, however, the usefulness of SFS is limited by the low deployment of SFS clients. It was developed in the June 2000 doctoral thesis of
71:. The client manages connections to remote file systems as necessary, acting as a kind of protocol translation layer. The SFS server works similarly to other distributed file system servers, by exposing an existing
95:, administratively configured distributed file systems in larger organizations, and various remote file transfer protocols. It is designed to operate securely between separate
106:
In addition to the new perspective, SFS also addresses some commonly raised limitations of other distributed file systems. For example, NFS and
83:. When an SFS file system is first accessed through this path, a connection to the server is made and the directory is created ("automounted").
236:
325:
320:
160:
60:
315:
56:
268:
25:
100:
96:
155:
143:
139:
263:
107:
223:
170:
165:
131:
127:
53:
219:
135:
116:
68:
239:
SIGOPS European workshop: Support for composing distributed applications. Sintra, Portugal:
72:
64:
112:
191:
37:
309:
281:
91:
The primary motivation behind the file system is to address the shortcomings of
41:
230:
92:
33:
76:
29:
119:
from other computers on the network, without encapsulation layers such as
67:, and thus can work on any operating system that supports NFS, including
225:
Escaping the Evils of
Centralized Control with self-certifying pathnames
272:
138:
of remote files and thus is more dependent on network reliability,
120:
292:
240:
198:
103:
of the server (hence why it is called "self-certifying").
192:"Self-Certifying File System Implementation for Windows"
75:
over the network, over the specific SFS protocol. On
32:
operating systems, while also providing transparent
79:systems, SFS file systems can usually be found at
264:archive of SFS official web site (archive.org)
8:
63:(NFS) protocol for communicating with the
182:
7:
269:"Self-certifying File System: FAQ"
14:
24:) is a global and decentralized,
161:Network File System (protocol)
1:
282:"Self-certifying File System"
190:David Euresti (August 2002).
134:, SFS does not provide local
36:of communications as well as
280:David Mazières (May 2000).
18:Self-certifying File System
342:
235:. Proceedings of the 8th
326:Distributed data storage
26:distributed file system
321:Userspace file systems
101:public-key fingerprint
156:Clustered file system
97:administrative realms
59:implements the Sun's
316:Network file systems
81:/sfs/hostname:hostID
111:themselves provide
61:Network File System
222:(September 1998).
171:Andrew File System
166:Coda (file system)
275:on July 25, 2008.
220:M. Frans Kaashoek
117:tamper resistance
333:
302:
300:
299:
286:
276:
271:. Archived from
251:
250:
248:
247:
234:
218:David Mazières,
215:
209:
208:
206:
205:
196:
187:
115:(encryption) or
82:
73:disk file system
65:operating system
341:
340:
336:
335:
334:
332:
331:
330:
306:
305:
297:
295:
284:
279:
267:
260:
255:
254:
245:
243:
228:
217:
216:
212:
203:
201:
194:
189:
188:
184:
179:
152:
113:confidentiality
89:
80:
50:
12:
11:
5:
339:
337:
329:
328:
323:
318:
308:
307:
304:
303:
277:
259:
258:External links
256:
253:
252:
210:
181:
180:
178:
175:
174:
173:
168:
163:
158:
151:
148:
88:
85:
49:
48:Implementation
46:
42:David Mazières
38:authentication
16:In computing,
13:
10:
9:
6:
4:
3:
2:
338:
327:
324:
322:
319:
317:
314:
313:
311:
294:
290:
283:
278:
274:
270:
265:
262:
261:
257:
242:
238:
232:
227:
226:
221:
214:
211:
200:
193:
186:
183:
176:
172:
169:
167:
164:
162:
159:
157:
154:
153:
149:
147:
145:
141:
137:
133:
129:
124:
122:
118:
114:
109:
104:
102:
98:
94:
86:
84:
78:
74:
70:
66:
62:
58:
55:
47:
45:
43:
39:
35:
31:
27:
23:
19:
296:. Retrieved
288:
285:(PostScript)
273:the original
244:. Retrieved
224:
213:
202:. Retrieved
195:(PostScript)
185:
125:
105:
90:
51:
21:
17:
15:
87:Differences
310:Categories
298:2012-01-16
289:PhD Thesis
246:2006-12-23
231:PostScript
204:2006-12-23
177:References
34:encryption
144:bandwidth
93:hardwired
77:Unix-like
30:Unix-like
150:See also
52:The SFS
140:latency
136:caching
126:Unlike
69:Windows
57:daemon
54:client
121:IPsec
142:and
130:and
128:Coda
28:for
293:MIT
241:MIT
237:ACM
199:MIT
132:AFS
108:SMB
22:SFS
312::
291:.
287:.
266:*
197:.
146:.
123:.
44:.
301:.
249:.
233:)
229:(
207:.
20:(
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.