MDX permission details

What are below permissions in Android MDX?

Q. What are Content providersrelate to

A. Content Providers and Services are protected by querying the OS for the calling Package’s Signing Certificate and comparing that to the one used to sign the published app within the XMS/CEM. If the signing certificate matches, then the app is allowed to make the call. If the certificates do not match, then the call to the Content Provider/Service is rejected and a NULL is returned.

Q.What is Android.permission.READ_LOGS?-

A. READ_LOGS permission is used for sending diagnostic information when troubleshooting an application. This allows the app to capture the logs from the Main Console which often provides critical information needed to debug an issue. These logs are saved into a ZIP file and sent to Secure Hub upon request. Secure Hub, in turn, can send those logs to the Enterprise Administrator or IT support for further analysis.

Q. What is android.permission.KIL_BACKGROUND_PROCESSES?

A. KIL_BACKGROUND_PROCESS is only used by an application to terminate its own processes (and not some other application’s). We use this permission when it is necessary to restart an application process and there may exist one or more processes for the app running. Sometimes terminating the app process is necessary to fully support a change to certain policies or to ensure proper behavior of the app under specific instances. This only happens after MDX displays a dialog to the user telling them the app must be restarted (or exited) and for what reasons.


  • No Related Posts

You cannot change the drive label on a layer or a published image

You cannot relabel the C: drive in App Layering, whether it’s in a published image or in a Packaging Machine. We use the drive labels to identify our disks, and we will actively block you from changing it. In a published machine, the drive label will be ULayeredImage. In a packaging machine, it will be UDiskBoot.

You can see exactly when we refuse the volume rename via a line like this in C:Program FilesUnideskUniserviceLogLog0.txt:

[06/11/2018][14:32:20:786] Log Detail Data Length 1 Offset 0x52764 SET_VOLUME_INFORMATION irp denied Status 0xae00

Note, however, we only intercept IRPs when our software is running. There are two circumstances where our drivers and software is not running: when you publish with Elastic Layering set to None, and when you edit an OS layer version. Editing the OS layer is just booting a modified clone of the original Gold VM’s boot disk. You edit that in place, finalize, and we copy the whole disk back. That way you can put things in the OS layer that might not play well without filter driver. You can relabel the C: drive on the OS layer, and you can do it in a published image with Elastic Layering off. Everywhere else, we’ll intercept the IRP and just deny it.

Now, in those circumstances, with our software not running, our software also doesn’t care if you relabel the disk. However, you should still not attempt to relabel the disk when editing the OS layer. It’s possible we would fail a Finalize operation on your modified OS layer – since we can’t find the right disk. But even if we allow you ti finalize that, it won’t change anything in the published image. The volume labels in the published image are set by the ELM, and you must not change them, even if you figure out a way. We use those volume labels to find our disks, and if you manage to modify the label on a published image, we will have problems with that.


Bluemix devops deployment failure

Recently the delivery pipeline that pushes my app to the bluemix server stopped working. The staging log indicates the app would be invalid, in relation to some liberty build pack, see screenshot. Can anyone help me identify the root of this problem? Any help would be much appreciated.
![alt text][1]

[1]: /answers/storage/temp/17085-error.png


Installing custom app failed on QRadar7.3

We have an app originally developed under QRadar 7.2.8 and tried to install it to QRadar 7.3.0. It failed with “Installed with error”.

We checked the /var/log/qradar.log and found logs like this. Since the app installed without problem on 7.2.8. Did we miss anything to make it work on 7.3.0 ?

*May 10 16:23:48 ::ffff:X.X.X.X [hostcontext.hostcontext] [pool-1-thread-2] com.q1labs.configservices.hostcontext.core.tasks.docker.DockerBuildImageTask: [WARN] [NOT:0000004000][X.X.X.X/- -] [-/- -]Could not execute command [/usr/bin/docker build -t qregistry.service.consul:5444/qapp/1006:1.1 beta /tmp/AppFW_1006]. Process returned [false] with the following errors: [[/usr/bin/docker: “build” requires 1 argument., See ‘/usr/bin/docker build –help’., , Usage: docker build [OPTIONS] PATH | URL | -, , Build an image from a Dockerfile]].
May 10 16:23:50 ::ffff:X.X.X.X [tomcat.tomcat] [pool-1-thread-9] [INFO] [NOT:0000006000][X.X.X.X/- -] [-/- -]Following message suppressed 1 times in 300000 milliseconds
May 10 16:23:50 ::ffff:X.X.X.X [tomcat.tomcat] [pool-1-thread-9] [ERROR] [NOT:0000003000][X.X.X.X/- -] [-/- -]An exception occurred while building application asynchronously. Triggering rollback.
May 10 16:23:50 ::ffff:X.X.X.X [tomcat.tomcat] [pool-1-thread-9] com.q1labs.restapi_annotations.content.exceptions.endpointExceptions.ServerProcessingException: An error occurred while building docker image. Task state found to be [EXCEPTION].
May 10 16:23:50 ::ffff:X.X.X.X [tomcat.tomcat] [pool-1-thread-9] at
May 10 16:23:50 ::ffff:X.X.X.X [tomcat.tomcat] [pool-1-thread-9] at
May 10 16:23:50 ::ffff:X.X.X.X [tomcat.tomcat] [pool-1-thread-9] at java.util.concurrent.Executors$
May 10 16:23:50 ::ffff:X.X.X.X [tomcat.tomcat] [pool-1-thread-9] at
May 10 16:23:50 ::ffff:X.X.X.X [tomcat.tomcat] [pool-1-thread-9] at java.util.concurrent.ThreadPoolExecutor.runWorker(
May 10 16:23:50 ::ffff:X.X.X.X [tomcat.tomcat] [pool-1-thread-9] at java.util.concurrent.ThreadPoolExecutor$
May 10 16:23:50 ::ffff:X.X.X.X [tomcat.tomcat] [pool-1-thread-9] at
May 10 16:23:59 qradar730 [QRADAR] [18024] qflow: [INFO] [1494404580] Sent 0 flows on transport connection to X.X.X.X:32010
May 10 16:24:00 qradar730 [QRADAR] [18024] qflow: [INFO] [1494404640] 0 flows (0 OF, 0 SF(0)) 0 bytes, 0 packets; 0 nonaggregatable flows remain*


App Installation and Update Fails

After upgrading 7.2.8 patch 6, we started to get failure messages for app installation and update. We tried updating an existing app and installing a new app that hasn’t been installed before and got failure messages for both operation.
Any ideas?