Showing posts with label application. Show all posts
Showing posts with label application. Show all posts
Sunday, September 24, 2017
Download Rikomagic Remote Control application APK
Download Rikomagic Remote Control application APK
Rikomagic Remote Control is a nice application which let you use your Android phone or tablet as a remote control for one of these little sticks while it�s plugged into your TV. The Rikomagic application is also easy to use and pretty versatile. The first time you fire it up the app will scan your network looking for a compatible device. Just choose your device from the list and you�re on your way.
From there you can use your phone or tablet as a touchpad to move a mouse cursor across your TV screen. You can also bring up a keyboard to start typing, or turn your phone into a touchscreen controller � allowing you to pinch to zoom, scroll through websites, or even play games on your TV. You can also use your phone or tablet�s gyroscopic sensor for motion-based input.
There�s a Control tab that brings up a more traditional remote control-style interface, with direction buttons, home, back, menu, and search buttons, and more. This view also has a power button. Pressing it once disables the display on the TV just as if you�d tapped the power button on a tablet. Or you can completely shut down your device by pressing and holding the power icon until a pop-up asks if you�d like to power off. Once you do that, though, the only way to turn your mini PC back on is to unplug and reconnect the power source.
You can download it from here, here or here.
The pack contains:
- MK802II client
- Mobile Control for Android 4.1
- Mobile Control for Android 4.2
download file now
Thursday, September 21, 2017
The Python application TwitterCroatia
The Python application TwitterCroatia
During the winter semester I have been developing a Python application.
Since the Twitter API only allows 150 requests per hour, and Twitter does not generally allow users access to tweets older than a week or sometimes even less, the purpose of the code was to create a database of tweets for later analysis. And so, using the Python wrapper for the Twitter API, I created a set of modules, the most important of which I will now elaborate:
Also, with the csvToData module I have enabled integration with the CSV format (which Twitter recently offered its users for downloading their entire tweet history, and as of 2013, available in Croatia as well)
The next steps are:
Since the Twitter API only allows 150 requests per hour, and Twitter does not generally allow users access to tweets older than a week or sometimes even less, the purpose of the code was to create a database of tweets for later analysis. And so, using the Python wrapper for the Twitter API, I created a set of modules, the most important of which I will now elaborate:
- The first and easiest to explain is the twitterDB module. It stores and retrieves data from files using pickle. Its main functions are addTweet, addUser, getTweets and getUsers. It can also fetch single or multiple tweets from a specified user or check if a file contains a user id, which are functions mostly used to avoid duplicates being needlessly stored in a file.
- The module twitterCommunication is the module which communicates with the Twitter API using the python-twitter wrapper. Its functions mostly mimic those enabled by the wrapper itself, only with implemented error handling for most common errors (such as network malfunctions and exceeded rate limits) but the biggest advantage is the automated cursor handling. When a large enough amount of data is requested, the Twitter API breaks it up in pieces and sends only the first piece along with the cursor which is a reference to the next piece. The functions in this module expect this and call the API recursively until all pieces are delivered. It should be noted that this means that one call to a function may mean more than one request to the API.
- The third module getAllFollowersAsObjects uses the aforementioned two modules to create a more complex functionality - download all user objects who follow a specified user using twitterCommunication and store them in a specified file using twitterDB.
- The last module uses all the other modules, and was the end purpose of my code. It is currently called twitterCroatia although the name is not abstract enough and might be misleading, and so might change. It is the only module which has an infinitely long while loop, its function being the continuous collection of data. It starts by requesting a single user object, and then requesting its timeline and its followers, and proceeds to do the same for each of the followers, if there are any, ad infinitum. It is conceivable for the loop to be in fact finite, for example in a closed circle of friends who follow each other and nobody else, but this is unlikely to happen.
Also, with the csvToData module I have enabled integration with the CSV format (which Twitter recently offered its users for downloading their entire tweet history, and as of 2013, available in Croatia as well)
The next steps are:
- moving from pickle and data serialization to an SQLite database.
- utilizing tools that might prove useful in future development such as the Python Graph Tool and Natural Language Toolkit.
download file now
Thursday, September 7, 2017
Thoughts about enhancing application permission control
Thoughts about enhancing application permission control
It occurred to me and (a lot of other people, as will be shown) that with Android applications, it may be useful to extend permission management for installed applications to enable logging/auditing or finer grained control. I remembered seeing some application which provided some of that functionality, but was unsure of exact details. Since this area of Android just might be suitable for me to try some enhancements, it seemed appropriate to explore the following points:
- What existing solutions or ideas are available for extending Androids permission system? What are their principles of operation?
- How does the Android system enforce Application permissions, and where is the relevant component in its source code?
- What can malware do with regard to application permissions
The existing application / modification and how these work
It turns out that there have been a couple of similar attempts to enhance permissions on android, below listed in no particular order:- PDroid, made by xda-developers.com community members. Consists of Android source patches and controlling user application. The patches modify system services which provide data for telephony, location and similar API calls (TelephonyManager, LocationManager, ...), creating wrappers for these components. The wrapper components check for application-set rules for handling permissions or logging. Patches (source) available, but application is closed-source.
- Cyanogenmod had modifications in the system components and application (UI) for revoking specific permissions to applications. Applications behaved as though the permission was not requested at install time by the application, and may crash. Theese extensions are no longer present in newer versions (since they caused applications to misbehave, become incompatible, etc.)
- papers Android Permissions Demystified, APEX, and a few other referenced therein. These enhancements have different approaches, goals or implementations which are described well in the respective papers, but do not have source code available.
- a few proprietary or commercial tools such as LBE Privacy Guard
Identifying components in Android system which grant permissions when application does an action which requires permission
Androids developer documentation on permissions outlines general situations when permissions are necessary: API calls for activity or services, accepting data from other applications (receiving broadcasts) or providing it (content providers).The documentation also shows actual permissions required for calls to certain parts of the API. A somewhat useful representation of this is the permission map which was created from the API as part of the Android Permissions Demystified project mentioned above.
The aforementioned papers Android Permissions Demystified and APEX provide a description of how the permissions are checked, around page 3, or pages 5, 6, section 4, for the two papers respectively. A summary of this follows. When an application calls an API method, the call is propagated through Androids inter-process communication to the system service which can service the API request (example: LocationManagerService provides location). The system component classes must check for permissions regarding to the action, using methods such as checkPermission, enforcePermission from Context (be it Activity, Service or other context). The actual decision is done in the PackageManagerService which grants or denies permissions depending on those requested at install time.
How simple malware might be done, relating to permission management
Some permissions in the Android system are broad, while others are fine-grained. An example of broad permission is the INTERNET permission, which allows any socket access. Malicious applications might claim to be using the permissions for some legitimate and benign task, while in reality that permission allows it to do additional malicious functionality.download file now
Subscribe to:
Posts (Atom)