Best ieee projects - Towards shared ownership in the cloud

Mini project centers in chennai, storage platforms promise a convenient way for users to share files and engage in collaborations, yet they require all files to have a single owner who unilaterally makes access control decisions(embedded project centers in chennai). Existing clouds are, thus, agnostic to the notion of shared ownership. This can be significant limitation in much collaboration because, for example, one owner can delete files and revoke access without consulting the other collaborators. In this paper, we first formally define a notion of shared ownership within a file access control model(arduino project centers in chennai). We then propose two possible instantiations of our proposed shared ownership model. Our first solution, called Commune, relies on secure file dispersal and collusion resistant secret sharing to ensure that all access grants in the cloud require the support of an agreed threshold of owners(embedded project centers in chennai). As such, Commune can be used in existing clouds without modifications to the platforms. Our second solution, dubbed Comrade, leverages the block chain technology in order to reach consensus on access control decision. Unlike Commune, Comrade requires that the cloud is able to translate access control decisions that reach consensus in the block chain into storage access control rules, thus requiring minor modifications to existing clouds. We analyze the security of our proposals and compare/evaluate their performance through implementations using Amazon S3(arduino mini project centers in chennai).

CONTRIBUTION:-
To access a file, a client establishes a TLS connection to the PDP using its registered public key inside a client certificate. The PDP identifies the client based on the key and makes the access control decision by locally evaluating a function of the owner contract. Similar to Commune, our Comrade prototype breaks units up into pieces.

SYSTEM ANALYSIS:-
If all participants contribute their research efforts to the project, then they may want to share the ownership over the collaboration files so that all access decisions are agreed upon among the owners. There are two main arguments why this may be preferred to individual ownership. First, a sole owner can abuse his rights by unilaterally making access control decisions. The community features a number of anecdotes where users revoke access to shared files from other collaborators. Second, even if owners are willing to elect and trust one of them to make access control decisions, the elected owner may not want to be held accountable for collecting and correctly evaluating other owners’ policies. For example, incorrect evaluations may incur negative reputation or financial penalties. In short, they are agnostic to the concept of shared ownership. Furthermore, state-of-the-art trust management systems that can support shared ownership policies (e.g., SecPAL [1], KeyNote [2], Delegation Lo gic [3]) make all access decisions using a centralized Policy Decision Point (PDP).

DISADVANTAGES:-
This is not suitable for enforcing our shared ownership model, because the user who administrates the PDP can arbitrarily change the policy rules set by the owners and enforce his own policies
However, the individual ownership is not suitable for numerous cloud-based applications and collaborations

PROPOSED SYSTEM:-
In this paper, we address the problem of distributed enforcement of shared ownership within cloud storage providers. By distributed enforcement, we mean enforcement where access to files in a shared repository is granted if and only if t out of n owners separately supports the grant decision. Therefore, we introduce the Shared- Ownership file access control Model (SOM) to define our notion of shared ownership, and to formally state the given enforcement problem. We then propose two instantiations of the SOM model to enforce shared ownership policies in a distributed fashion. We also propose a new instantiation of the SOM model, Comrade, which leverages functionality from the block chain in order to reach consensus on access control decisions eee projects in chennai, matlab projects in chennai.

ADVANTAGES
We formalize the notion of shared ownership within a file access control model named SOM, and use it to define a novel access control problem of distributed enforcement of shared ownership in existing clouds
Comrade improves the performance of Commune, but requires that the cloud is able to translate access control decisions that reached consensus in the block chain into storage access control rules, thus requiring minor modifications of existing clouds(matlab mini project centers in chennai)

Even though existing cloud platforms are used as shared repositories, they do not support any notion of shared ownership. We consider this a severe limitation because contributing parties cannot jointly decide how their resources are used. In this paper, we introduced a novel concept of shared ownership and we described it through a formal access control model, called SOM(embedded projects in chennai). We then propose two possible instantiations of our proposed shared ownership model. Our first solution, called Commune, relies on secure file dispersal and collusion-resistant secret sharing to ensure that all access grants in the cloud require the support of an agreed threshold of owners(eee mini projects in chennai). As such, Commune can be used in existing agnostic clouds without modifications to the platforms. Our second solution, dubbed Comrade, leverages the block chain technology in order to reach consensus on access control decision(ug projects in chennai). Unlike Commune, Comrade requires that the cloud is able to translate access control decisions that achieved consensus in the block chain into storage access control rules. Comrade, however, shows better performance than Commune.