Demo Data from VLDB 2026 / reviewers in the wild / expert
Chirag Todarka
dblp:150/9183
· DBLP profile ↗
1ranked-venue papers
0as first author
0since 2021 · last 2014
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 1
Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.
| Network and information security
1 paper |
Web and mobile security · 67% Systems and software security · 33% | |
| Software engineering, system software, and programming languages
1 paper |
Program analysis · 100% |
Topics — the 5 heaviest of 5, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Web and mobile security › mobile security
android permission system |
0.2 | 1 | 2014 | Information flows as a permission mechanism · ASE 2014 |
Systems and software security › information flow control
information flow analysis |
0.2 | 1 | 2014 | Information flows as a permission mechanism · ASE 2014 |
Web and mobile security
mobile security |
0.2 | 1 | 2014 | Information flows as a permission mechanism · ASE 2014 |
Program analysis › static analysis
information flow analysis |
0.1 | 1 | 2014 | Information flows as a permission mechanism · ASE 2014 |
Program analysis
static analysis |
0.1 | 1 | 2014 | Information flows as a permission mechanism · ASE 2014 |
Methods — techniques the papers use, named apart from their topics
static analysis · 0.4
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2014 | Information flows as a permission mechanismabstractThis paper proposes Flow Permissions, an extension to the Android permission mechanism. Unlike the existing permission mechanism, our permission mechanism contains semantic information based on information flows. Flow Permissions allow users to examine and grant per-app information flows within an application e.g., a permission for reading the phone number and sending it over the network) as well as cross-app information flows across multiple applications e.g., a permission for reading the phone number and sending it to another application already installed on the user's phone). Our goal with Flow Permissions is to provide visibility into the holistic behavior of the applications installed on a user's phone. In order to support Flow Permissions on Android, we have developed a static analysis engine that detects flows within an Android application. We have also modified Android's existing permission mechanism and installation procedure to support Flow Permissions. We evaluate our prototype with 2,992 popular applications and 1,047 malicious applications and show that our design is practical and effective in deriving Flow Permissions. We validate our cross-app flow generation and installation procedure on a Galaxy Nexus smartphone. Namita Vishnubhotla, Chirag Todarka, Mohit Arora, Babu Dhandapani, Eric John Lehner, Steven Y. Ko, Lukasz Ziarek |
ASE | 3 |