2019-03-30 10:49:29 +00:00
|
|
|
#pragma once
|
2017-04-14 19:23:09 +00:00
|
|
|
|
2017-04-15 18:42:24 +00:00
|
|
|
#include <pthread.h>
|
2017-11-27 07:37:28 +00:00
|
|
|
#include <sys/un.h>
|
2017-12-18 07:46:18 +00:00
|
|
|
#include <sys/socket.h>
|
2019-02-16 01:45:05 +00:00
|
|
|
#include <string>
|
|
|
|
#include <vector>
|
2017-04-15 18:42:24 +00:00
|
|
|
|
2017-04-08 23:25:10 +00:00
|
|
|
// Commands require connecting to daemon
|
2018-02-11 09:23:36 +00:00
|
|
|
enum {
|
2017-05-05 08:13:26 +00:00
|
|
|
DO_NOTHING = 0,
|
2017-04-08 23:25:10 +00:00
|
|
|
SUPERUSER,
|
2017-04-14 19:23:09 +00:00
|
|
|
CHECK_VERSION,
|
|
|
|
CHECK_VERSION_CODE,
|
2017-04-15 11:02:07 +00:00
|
|
|
POST_FS_DATA,
|
2017-04-15 18:42:24 +00:00
|
|
|
LATE_START,
|
2018-08-09 06:52:44 +00:00
|
|
|
BOOT_COMPLETE,
|
2018-11-01 18:08:33 +00:00
|
|
|
MAGISKHIDE,
|
2018-11-16 08:20:30 +00:00
|
|
|
SQLITE_CMD,
|
2019-05-13 09:01:10 +00:00
|
|
|
BROADCAST_ACK,
|
2019-09-13 07:14:21 +00:00
|
|
|
REMOVE_MODULES,
|
Introduce component agnostic communication
Usually, the communication between native and the app is done via
sending intents to either broadcast or activity. These communication
channels are for launching root requests dialogs, sending root request
notifications (the toast you see when an app gained root access), and
root request logging.
Sending intents by am (activity manager) usually requires specifying
the component name in the format of <pkg>/<class name>. This means parts
of Magisk Manager cannot be randomized or else the native daemon is
unable to know where to send data to the app.
On modern Android (not sure which API is it introduced), it is possible
to send broadcasts to a package, not a specific component. Which
component will receive the intent depends on the intent filter declared
in AndroidManifest.xml. Since we already have a mechanism in native code
to keep track of the package name of Magisk Manager, this makes it
perfect to pass intents to Magisk Manager that have components being
randomly obfuscated (stub APKs).
There are a few caveats though. Although this broadcasting method works
perfectly fine on AOSP and most systems, there are OEMs out there
shipping ROMs blocking broadcasts unexpectedly. In order to make sure
Magisk works in all kinds of scenarios, we run actual tests every boot
to determine which communication method should be used.
We have 3 methods in total, ordered in preference:
1. Broadcasting to a package
2. Broadcasting to a specific component
3. Starting a specific activity component
Method 3 will always work on any device, but the downside is anytime
a communication happens, Magisk Manager will steal foreground focus
regardless of whether UI is drawn. Method 1 is the only way to support
obfuscated stub APKs. The communication test will test method 1 and 2,
and if Magisk Manager is able to receive the messages, it will then
update the daemon configuration to use whichever is preferable. If none
of the broadcasts can be delivered, then the fallback method 3 will be
used.
2019-10-21 17:59:04 +00:00
|
|
|
BROADCAST_TEST,
|
2018-02-11 09:23:36 +00:00
|
|
|
};
|
2017-04-08 23:25:10 +00:00
|
|
|
|
2017-05-05 08:13:26 +00:00
|
|
|
// Return codes for daemon
|
2018-02-11 09:23:36 +00:00
|
|
|
enum {
|
2017-05-05 08:13:26 +00:00
|
|
|
DAEMON_ERROR = -1,
|
|
|
|
DAEMON_SUCCESS = 0,
|
|
|
|
ROOT_REQUIRED,
|
2018-11-01 18:08:33 +00:00
|
|
|
DAEMON_LAST
|
2018-02-11 09:23:36 +00:00
|
|
|
};
|
2017-05-05 08:13:26 +00:00
|
|
|
|
2017-04-08 23:25:10 +00:00
|
|
|
// daemon.c
|
|
|
|
|
2019-03-04 21:45:18 +00:00
|
|
|
int connect_daemon(bool create = false);
|
2018-11-13 07:07:02 +00:00
|
|
|
int switch_mnt_ns(int pid);
|
2019-09-13 07:14:21 +00:00
|
|
|
void reboot();
|
2017-11-27 07:37:28 +00:00
|
|
|
|
|
|
|
// socket.c
|
|
|
|
|
2018-10-12 04:50:47 +00:00
|
|
|
socklen_t setup_sockaddr(struct sockaddr_un *sun, const char *name);
|
2018-09-16 08:16:18 +00:00
|
|
|
int create_rand_socket(struct sockaddr_un *sun);
|
2018-10-04 08:59:51 +00:00
|
|
|
int socket_accept(int sockfd, int timeout);
|
2019-02-09 20:02:46 +00:00
|
|
|
void get_client_cred(int fd, struct ucred *cred);
|
2017-04-07 23:37:43 +00:00
|
|
|
int recv_fd(int sockfd);
|
|
|
|
void send_fd(int sockfd, int fd);
|
|
|
|
int read_int(int fd);
|
2018-09-16 08:16:18 +00:00
|
|
|
int read_int_be(int fd);
|
2017-04-07 23:37:43 +00:00
|
|
|
void write_int(int fd, int val);
|
2018-09-16 08:16:18 +00:00
|
|
|
void write_int_be(int fd, int val);
|
|
|
|
char *read_string(int fd);
|
|
|
|
char *read_string_be(int fd);
|
|
|
|
void write_string(int fd, const char *val);
|
|
|
|
void write_string_be(int fd, const char *val);
|
|
|
|
void write_key_value(int fd, const char *key, const char *val);
|
|
|
|
void write_key_token(int fd, const char *key, int tok);
|
2017-04-14 19:23:09 +00:00
|
|
|
|
2017-04-15 18:42:24 +00:00
|
|
|
/***************
|
|
|
|
* Boot Stages *
|
|
|
|
***************/
|
|
|
|
|
2018-10-13 01:46:09 +00:00
|
|
|
void unlock_blocks();
|
2017-04-15 18:42:24 +00:00
|
|
|
void post_fs_data(int client);
|
|
|
|
void late_start(int client);
|
2018-08-09 06:52:44 +00:00
|
|
|
void boot_complete(int client);
|
2017-04-15 11:02:07 +00:00
|
|
|
|
2019-02-16 01:45:05 +00:00
|
|
|
/*************
|
|
|
|
* Scripting *
|
|
|
|
*************/
|
|
|
|
|
2019-03-23 07:50:55 +00:00
|
|
|
void exec_script(const char *script);
|
2019-02-16 01:45:05 +00:00
|
|
|
void exec_common_script(const char *stage);
|
|
|
|
void exec_module_script(const char *stage, const std::vector<std::string> &module_list);
|
|
|
|
void migrate_img(const char *img);
|
|
|
|
void install_apk(const char *apk);
|
|
|
|
|
2017-04-15 11:02:07 +00:00
|
|
|
/**************
|
|
|
|
* MagiskHide *
|
|
|
|
**************/
|
|
|
|
|
2018-11-01 18:08:33 +00:00
|
|
|
void magiskhide_handler(int client);
|
2017-04-15 11:02:07 +00:00
|
|
|
|
|
|
|
/*************
|
|
|
|
* Superuser *
|
|
|
|
*************/
|
|
|
|
|
2018-10-04 08:59:51 +00:00
|
|
|
void su_daemon_handler(int client, struct ucred *credential);
|
Introduce component agnostic communication
Usually, the communication between native and the app is done via
sending intents to either broadcast or activity. These communication
channels are for launching root requests dialogs, sending root request
notifications (the toast you see when an app gained root access), and
root request logging.
Sending intents by am (activity manager) usually requires specifying
the component name in the format of <pkg>/<class name>. This means parts
of Magisk Manager cannot be randomized or else the native daemon is
unable to know where to send data to the app.
On modern Android (not sure which API is it introduced), it is possible
to send broadcasts to a package, not a specific component. Which
component will receive the intent depends on the intent filter declared
in AndroidManifest.xml. Since we already have a mechanism in native code
to keep track of the package name of Magisk Manager, this makes it
perfect to pass intents to Magisk Manager that have components being
randomly obfuscated (stub APKs).
There are a few caveats though. Although this broadcasting method works
perfectly fine on AOSP and most systems, there are OEMs out there
shipping ROMs blocking broadcasts unexpectedly. In order to make sure
Magisk works in all kinds of scenarios, we run actual tests every boot
to determine which communication method should be used.
We have 3 methods in total, ordered in preference:
1. Broadcasting to a package
2. Broadcasting to a specific component
3. Starting a specific activity component
Method 3 will always work on any device, but the downside is anytime
a communication happens, Magisk Manager will steal foreground focus
regardless of whether UI is drawn. Method 1 is the only way to support
obfuscated stub APKs. The communication test will test method 1 and 2,
and if Magisk Manager is able to receive the messages, it will then
update the daemon configuration to use whichever is preferable. If none
of the broadcasts can be delivered, then the fallback method 3 will be
used.
2019-10-21 17:59:04 +00:00
|
|
|
void broadcast_test(int client = -1);
|
|
|
|
void broadcast_ack(int client);
|
|
|
|
|
|
|
|
/*********************
|
|
|
|
* Daemon Global Vars
|
|
|
|
*********************/
|
2017-04-15 11:02:07 +00:00
|
|
|
|
2019-03-30 10:49:29 +00:00
|
|
|
extern int SDK_INT;
|
|
|
|
extern bool RECOVERY_MODE;
|
2019-06-04 06:32:49 +00:00
|
|
|
#define APP_DATA_DIR (SDK_INT >= 24 ? "/data/user_de" : "/data/user")
|