ESPOONERBAC_{{ERBAC}}: Enforcing Security Policies In Outsourced Environments

Data outsourcing is a growing business model offering services to individuals and enterprises for processing and storing a huge amount of data. It is not only economical but also promises higher availability, scalability, and more effective quality of service than in-house solutions. Despite all its benefits, data outsourcing raises serious security concerns for preserving data confidentiality. There are solutions for preserving confidentiality of data while supporting search on the data stored in outsourced environments. However, such solutions do not support access policies to regulate access to a particular subset of the stored data. For complex user management, large enterprises employ Role-Based Access Controls (RBAC) models for making access decisions based on the role in which a user is active in. However, RBAC models cannot be deployed in outsourced environments as they rely on trusted infrastructure in order to regulate access to the data. The deployment of RBAC models may reveal private information about sensitive data they aim to protect. In this paper, we aim at filling this gap by proposing \textbf{$\mathit{ESPOON_{ERBAC}}$} for enforcing RBAC policies in outsourced environments. $\mathit{ESPOON_{ERBAC}}$ enforces RBAC policies in an encrypted manner where a curious service provider may learn a very limited information about RBAC policies. We have implemented $\mathit{ESPOON_{ERBAC}}$ and provided its performance evaluation showing a limited overhead, thus confirming viability of our approach.Comment: The final version of this paper has been accepted for publication in Elsevier Computers & Security 2013. arXiv admin note: text overlap with arXiv:1306.482

Context-dependent motor skill and the role of practice

Research has shown that retrieval of learned information is better when the original learning context is reinstated during testing than when this context is changed. Recently, such contextual dependencies have also been found for perceptual-motor behavior. The current study investigated the nature of context-dependent learning in the discrete sequence production task, and in addition examined whether the amount of practice affects the extent to which sequences are sensitive to contextual alterations. It was found that changing contextual cues—but not the removal of such cues—had a detrimental effect on performance. Moreover, this effect was observed only after limited practice, but not after extensive practice. Our findings support the notion of a novel type of context-dependent learning during initial motor skill acquisition and demonstrate that this context-dependence reduces with practice. It is proposed that a gradual development with practice from stimulus-driven to representation-driven sequence execution underlies this practice effect

Persistent Contextual Values as Inter-Process Layers

Mobile applications today often fail to be context aware when they also need to be customizable and efficient at run-time. Context-oriented programming allows programmers to develop applications that are more context aware. Its central construct, the so-called layer, however, is not customizable. We propose to use novel persistent contextual values for mobile development. Persistent contextual values automatically adapt their value to the context. Furthermore they provide access without overhead. Key-value configuration files contain the specification of contextual values and the persisted contextual values themselves. By modifying the configuration files, the contextual values can easily be customized for every context. From the specification, we generate code to simplify development. Our implementation, called Elektra, permits development in several languages including C++ and Java. In a benchmark we compare layer activations between threads and between applications. In a case study involving a web-server on a mobile embedded device the performance overhead is minimal, even with many context switches.Comment: 8 pages Mobile! 16, October 31, 2016, Amsterdam, Netherland

Contextualism, Moral Disagreement, and Proposition Clouds

According to contextualist theories in metaethics, when you use a moral term in a context, the context plays an ineliminable part in determining what natural property will be the semantic value of the term. Furthermore, on subjectivist and relativist versions of these views, it is either the speaker's own moral code or her moral community's moral code that constitutes the reference-fixing context. One standard objection to views of this type is that they fail to enable us to disagree in ordinary conversations. In this chapter, I develop a new response to this objection on the basis of Kai von Fintel and Anthony Gillies' notion of proposition clouds. I argue that, because we live in a multicultural society, the conversational contexts we face will fail to disambiguate between all the things we could mean. This is why we can at best put into play proposition clouds when we make moral utterances. All the propositions in such clouds are then available for rejection and acceptance on the behalf of our audiences. The norms of conversation then guide us to make informative contributions to the conversation - accept and reject propositions in a way that leads to co-ordination of action and choice

How to do things with modals

Mind &Language, Volume 35, Issue 1, Page 115-138, February 2020

A Generic Storage API

We present a generic API suitable for provision of highly generic storage facilities that can be tailored to produce various individually customised storage infrastructures. The paper identifies a candidate set of minimal storage system building blocks, which are sufficiently simple to avoid encapsulating policy where it cannot be customised by applications, and composable to build highly flexible storage architectures. Four main generic components are defined: the store, the namer, the caster and the interpreter. It is hypothesised that these are sufficiently general that they could act as building blocks for any information storage and retrieval system. The essential characteristics of each are defined by an interface, which may be implemented by multiple implementing classes.Comment: Submitted to ACSC 200