![]() ![]() Once installed on the victim machine, we can do whatever we want to their system by sending out commands to it. Metasploit's flagship product, the Meterpreter, is very powerful and an all-purpose payload. Hi guys, I'm here again with my second tutorial, as I promised. It's Keystore Explorer for me.UPDATE: This post is outdated, the latest version with the correct links and updated instructions can be found at my blog, here. I'm not going to use the command prompt for this solution. I don't know how to make a "certificate chain" or have B4a reference a private key that Google is supposed to be generating itself under the new scheme? I've also got the deployment_r file provided on the same App Integrity page that I don't even know the purpose of this certificate or how to use it. The keystore I'm using in this test is empty then with KeyStore Explorer I Import Trusted Certificate (upload_r provided by Google on the App Integrity page). b4a must reference a valid KeyStore key entry containing a private key and corresponding public key certificate chain. Jarsigner: Certificate chain not found for: b4a. ObfuscatorMap.txt file created in Objects folder.Ĭonvert byte code - optimized dex. My problem at this minute is: Upon building the app bundle B4A is reporting: Also, if you see "Releases Signed by Google" you are Not good to go automatically. The forum thread is far from being straight forward. Only my ex superior with no development background and only business oriented mindset think that a solution can appear like a snap of fingers in seconds.Īre you still looking for help or give up? As a programmer, we should understand that solutions some times may took some effort. No one is forced to pay for paid support. Sometimes answers are already there, we just need some time to search and try one by one. It is easier to get answer than some where else. Fortunately here in B4X community I feel like at home. Big giants like Google, Java, Microsoft come out with new technologies now and then but I know if I want to continue in this field, I need to adapt to it. The software technology market is very disappointing to me too. As a “younger” programmer than some seniors, I understand my path. We all volunteer ourself to help others as a token of appreciation from the help with got from others. B4X forum is a wonderful place to get help. I saw that option if a developer has lost his key that went with an existing app.Ĭlick to expand.What else you are looking for? I am not sure. ![]() Perhaps I need to request Google to reset my key. The tutorial above seems to be for a new app. Yes, I'm still learning a few things which is why I am asking here in the forums. I've tried using Keystore Explorer to create a new keystore with no luck. My issue is that the certificates and keys that Google generated for me when I switched to the new app format can't be imported into the B4A IDE that I'm aware of. ![]() Yes, I switched to the new bundle format by my own choice even though yes, I'm aware that it's not necessary. It's an existing app I've had in the Play Store for years. Of course Google rejects my app update (existing app) no matter what I try using the Keystore Explorer which I thought would be better than issuing direct commands. Nothing in the latest B4A mentions anything about an upload key or has a place to enter it. I've switched to the new package scheme for a reason. To make matters worse, there are no real explanations in the forums, but mostly the same key/certificate/private/public jibberish all out of order. I paid for this before it was free, so please don't say "it's free - get over it". I now have an older APK app that has been removed by Google due to "non compliance" because I can't get B4X to generate what Google needs. I cannot believe I've been sitting here for 3 days googling how to do all of this and all I find is "keytool" examples and CLI commands that nobody on this planet could have figured out on their own in a short time. I want to keep using B4A but B4A needs to keep up with the times! Generate keys for us, save them whereever you like, but sign my app from the IDE automatically with whatever Google Play EXPECTS. If the B4A IDE isn't helping me any, then I'll have no choice but to migrate completely to the dreaded but much used Android Studio. I've been a coder for 35 years and I have to admit that this private/public/key/certificate crap is a nightmare. Google apparently signs the app using our upload key, certificate or whatever they want to call it, but I don't have it, I don't know how to generate one, etc. The B4A IDE needs to automate all steps to creating an "upload key" for the Google Play Console where we upload our packages (now called Bundles). This pertains to the new >August 2021 Google Play app signing scheme that you can opt into, which I did. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |