Building secure file systems out of Byzantine storage. Mazières, D. & Shasha, D. 07/2002 2002.
Paper doi abstract bibtex This paper shows how to implement a trusted network file system on an untrusted server. While cryptographic storage techniques exist that allow users to keep data secret from untrusted servers, this work concentrates on the detection of tampering attacks and stale data. Ideally, users of an untrusted storage server would immediately and unconditionally notice any misbehavior on the part of the server. This ideal is unfortunately not achievable. However, we define a notion of data integrity called fork consistency in which, if the server delays just one user from seeing even a single change by another, the two users will never again see one another\textquoterights changes–-a failure easily detectable with on-line communication. We give a practical protocol for a multi-user network file system called SUNDR, and prove that SUNDR offers fork consistency whether or not the server obeys the protocol.
@conference {Mazieres:2002:BSF:571825.571840,
title = {Building secure file systems out of Byzantine storage},
booktitle = {PODC{\textquoteright}02 - Proceedings of the 21st Annual Symposium on Principles of Distributed Computing},
series = {PODC {\textquoteright}02},
year = {2002},
month = {07/2002},
pages = {108{\textendash}117},
publisher = {ACM},
organization = {ACM},
address = {Monterey, CA, USA},
abstract = {This paper shows how to implement a trusted network file system on an untrusted server. While cryptographic storage techniques exist that allow users to keep data secret from untrusted servers, this work concentrates on the detection of tampering attacks and stale data. Ideally, users of an untrusted storage server would immediately and unconditionally notice any misbehavior on the part of the server. This ideal is unfortunately not achievable. However, we define a notion of data integrity called fork consistency in which, if the server delays just one user from seeing even a single change by another, the two users will never again see one another{\textquoteright}s changes---a failure easily detectable with on-line communication. We give a practical protocol for a multi-user network file system called SUNDR, and prove that SUNDR offers fork consistency whether or not the server obeys the protocol.},
keywords = {Byzantine storage, detection, secure file system, stale data, tampering attack, trusted network, untrusted server},
isbn = {1-58113-485-1},
doi = {http://doi.acm.org/10.1145/571825.571840},
url = {http://doi.acm.org/10.1145/571825.571840},
author = {David Mazi{\`e}res and Shasha, Dennis}
}
Downloads: 0
{"_id":"twEhWnXfhZwXu4fqd","bibbaseid":"mazires-shasha-buildingsecurefilesystemsoutofbyzantinestorage-2002","downloads":0,"creationDate":"2018-07-03T04:50:29.440Z","title":"Building secure file systems out of Byzantine storage","author_short":["Mazières, D.","Shasha, D."],"year":2002,"bibtype":"conference","biburl":"https://gnunet.org/bibliography/export/bibtex","bibdata":{"bibtype":"conference","type":"conference","title":"Building secure file systems out of Byzantine storage","booktitle":"PODC\\textquoteright02 - Proceedings of the 21st Annual Symposium on Principles of Distributed Computing","series":"PODC \\textquoteright02","year":"2002","month":"07/2002","pages":"108\\textendash117","publisher":"ACM","organization":"ACM","address":"Monterey, CA, USA","abstract":"This paper shows how to implement a trusted network file system on an untrusted server. While cryptographic storage techniques exist that allow users to keep data secret from untrusted servers, this work concentrates on the detection of tampering attacks and stale data. Ideally, users of an untrusted storage server would immediately and unconditionally notice any misbehavior on the part of the server. This ideal is unfortunately not achievable. However, we define a notion of data integrity called fork consistency in which, if the server delays just one user from seeing even a single change by another, the two users will never again see one another\\textquoterights changes–-a failure easily detectable with on-line communication. We give a practical protocol for a multi-user network file system called SUNDR, and prove that SUNDR offers fork consistency whether or not the server obeys the protocol.","keywords":"Byzantine storage, detection, secure file system, stale data, tampering attack, trusted network, untrusted server","isbn":"1-58113-485-1","doi":"http://doi.acm.org/10.1145/571825.571840","url":"http://doi.acm.org/10.1145/571825.571840","author":[{"firstnames":["David"],"propositions":[],"lastnames":["Mazières"],"suffixes":[]},{"propositions":[],"lastnames":["Shasha"],"firstnames":["Dennis"],"suffixes":[]}],"bibtex":"@conference {Mazieres:2002:BSF:571825.571840,\n\ttitle = {Building secure file systems out of Byzantine storage},\n\tbooktitle = {PODC{\\textquoteright}02 - Proceedings of the 21st Annual Symposium on Principles of Distributed Computing},\n\tseries = {PODC {\\textquoteright}02},\n\tyear = {2002},\n\tmonth = {07/2002},\n\tpages = {108{\\textendash}117},\n\tpublisher = {ACM},\n\torganization = {ACM},\n\taddress = {Monterey, CA, USA},\n\tabstract = {This paper shows how to implement a trusted network file system on an untrusted server. While cryptographic storage techniques exist that allow users to keep data secret from untrusted servers, this work concentrates on the detection of tampering attacks and stale data. Ideally, users of an untrusted storage server would immediately and unconditionally notice any misbehavior on the part of the server. This ideal is unfortunately not achievable. However, we define a notion of data integrity called fork consistency in which, if the server delays just one user from seeing even a single change by another, the two users will never again see one another{\\textquoteright}s changes---a failure easily detectable with on-line communication. We give a practical protocol for a multi-user network file system called SUNDR, and prove that SUNDR offers fork consistency whether or not the server obeys the protocol.},\n\tkeywords = {Byzantine storage, detection, secure file system, stale data, tampering attack, trusted network, untrusted server},\n\tisbn = {1-58113-485-1},\n\tdoi = {http://doi.acm.org/10.1145/571825.571840},\n\turl = {http://doi.acm.org/10.1145/571825.571840},\n\tauthor = {David Mazi{\\`e}res and Shasha, Dennis}\n}\n","author_short":["Mazières, D.","Shasha, D."],"key":"Mazieres:2002:BSF:571825.571840","id":"Mazieres:2002:BSF:571825.571840","bibbaseid":"mazires-shasha-buildingsecurefilesystemsoutofbyzantinestorage-2002","role":"author","urls":{"Paper":"http://doi.acm.org/10.1145/571825.571840"},"keyword":["Byzantine storage","detection","secure file system","stale data","tampering attack","trusted network","untrusted server"],"downloads":0},"search_terms":["building","secure","file","systems","out","byzantine","storage","mazières","shasha"],"keywords":["byzantine storage","detection","secure file system","stale data","tampering attack","trusted network","untrusted server"],"authorIDs":[],"dataSources":["FWsPTwsmjtrBtRS3B"]}