Homework answers / question archive / AIM: To create a peer to peer distributed file system with encryption which should have all the below features satisfied, 1

AIM: To create a peer to peer distributed file system with encryption which should have all the below features satisfied, 1

Computer Science

Share With

AIM: To create a peer to peer distributed file system with encryption which should have all the
below features satisfied,
1. This is a P2P file system. - Show p2p via design doc and code implementation. Here each peer acts as
both client and server. For example, if there are 3 peers in the network during the demo, students will start
the server from any of the 3 different laptops, where each laptop acts as a peer in this case. There can be
many users in this distributed file system who act as clients. They try to access the files for which they
need the port number and IP address of the peer to whom they want to connect to.
Users can create, delete, read, write, restore files. – Show a user create, delete, read, write, restore files
on the primary server.Then show each replica (at least 3 replicas are needed) will maintain the same
updates. During the project demo, a student needs to connect to a server. Then show us the above
process by asking the teammates to open another 3 servers. Show the updates that are processed in
each replica.
For example, If there is a file abc.txt and if we open it in peer1(in this case peer1 is called primary server
and other peers are having its replicas), when made any updates to this file in peer1 the changes to
reflect in all other peers containing the same file.
Also, whenever a user opens a file in a certain peer and is trying to do write operation, and at the same
time another user is trying to access the same file in the same peer the request needs to be queued(with
the help of mutex locks on the file) .
2.A client(user) should always see the latest version of a file, or at least that a client should
never see an older version of a file after there exists a newer one. - Two students need to connect
to their primary server (for example, if one student connects to peer1 and another connects to peer2 or
peer3 ). Then demonstrate what happens when after one client(user- student1 in this case) does a write
on the primary server, the other client can see the update on the other server.
3. Users should be able to set permissions on files and directories. This requires that your file system is
able to name users. -- show this case: one user creates a file. The other user accesses the file
without/with permission. These permissions can be of types- private or public for a file. At the start of the
demo, each user creates an account in this file system and shares the files that he wanted to share with
other users and sets permissions as private or public.
4. File names (and directory names) should be treated as confidential and not visible except to the
authorized person. – for example, when an unregistered user connects to a peer and tries to view the
directories or files in it, these should not be visible.
5. Users should not be able to modify files or directories without being detected unless they are
authorized to do so. – During the demo, show us the case of two users accessing the same directory.
One modifies the file (update file name). The other user should not see any updates. We recommend that
you demonstrate what would happen if an unauthorized user tried to access the file (update, delete).
6. The communication between Peer to Peer should be encrypted. -- Show a user case.
When a user gets a file from a peer, it needs to be encrypted with a public key and the user should be
able to decrypt the file with a private key.
7. A malicious file server should not be able to create or delete files or directories without being detected.
- – - one student works as a server and the other works as a client. Show if it is detected by generating an
error, if the server tries to delete/create a file.