Adobe Releases Security Updates for Flash Player on Android - Samsung Galaxy Fit GT 5670

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Adobe has released a new version of its Flash Player for Android that fixes some critical security bugs. The new version of Flash, which, incidentally, is also available for Windows, Linux and OS X, fixes security vulnerabilities in Flash Player 11.1.115.6 and earlier versions for Android 4.x, and Flash Player 11.1.111.6 and earlier versions for Android 3.x and 2.x. These vulnerabilities, if exploited, could cause a crash and potentially allow an attacker to take control of the affected phone or tablet.
The update fixes two problems – the first is a memory corruption vulnerability in Matrix3D, a part of Flash which is used to determine the position and orientation of a three-dimensional object, that could lead to unauthorized code execution. The second vulnerability patched is an integer error that can lead to information disclosure.
Don’t Panic
Although these vulnerabilities are seen as critical, Adobe has rated them as “priority 2″ which means that there are currently no known exploits, and, based on previous experience, Adobe does not anticipate that exploits are imminent. As a result, Adobe is recommending users to install the update within the next 30 days.
The new update should be aviliable in the market but all of us know that in the market no adobe flash player for galaxy fit.

Any one upload new arm6 adobe player version ?

Related

[Q] Different Kernels.

Hey all,
I am new to the Android community. I just rooted my Nexus and flashed the Oxygen rom on it. It comes with the Netarchy kernel 1.3.5.(has awesome battery life) On the forums i noticed a lot of people posting about a trinity uv kernel for oxygen. Can anyone explain the difference between the kernels. Will changing the kernel affect my battery life?. And there is a new netarchy, should i update it to the latest version or just use the one which comes with the rom.. I am really a novice here, So any help would be appreciated. .
In computing, the kernel is the main component of most computer operating systems; it is a bridge between applications and the actual data processing done at the hardware level. The kernel's responsibilities include managing the system's resources (the communication between hardware and software components).[1] Usually as a basic component of an operating system, a kernel can provide the lowest-level abstraction layer for the resources (especially processors and I/O devices) that application software must control to perform its function. It typically makes these facilities available to application processes through inter-process communication mechanisms and system calls.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And yes, a new kernel might make your device faster with less battery drain. If you would like to flash a new kernel, then go do it. If you're not happy with the performance then flash a new kernel or revert to the original. But remember to do a NAND backup (full backup of your system/current OS) with ROM Manager before you begin.

[TOOL][ALPHA][DEV] APK List

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What is an APK List?
It's a developers tool. Sometimes I find an app which design I really like but have no idea how it is done. Besides that most of the time my phone isn't rooted (or I'm using some other phone). With all unpack/decompile tools out there the only thing I need is a way to copy APK files from phone memory to SD card for later analysis. Well this tool is just that, it lists all installed apps on any phone and let's you copy all or selected APKs to SD card. Currently there are no settings so destination defaults to "Apks".
Where can I get this app?
Download APK here
Or grab source from https://bitbucket.org/grupatnt/apklist/overview and compile with MonoDevelop or VS2010 (Mono for Android 4.x)
What can I do to help?
Fork hg repository, make fantastic changes and add Pull request.
I've found a bug! What do I do?
Keep calm and report it! You can report it either on this thread or on project Issues tracking register. Bug reports will be taken seriously and fixed when I have the time.
Thanks to _Logie from whom I've copied format for this post
Kudos to Android SDK and Intel teams for releasing VM Accelerated x86 Emulator.
Version 0.0.2 Released
Get it here
Changes
Cancelable progress dialog
Fixed APK Icon sizes
Beautified progress dialogs
Replaced ApkListAdapter with generic FastListAdapter
Mono for Android developers
Take a look at FastListAdapter and ViewHolderBase which implement View Holder pattern in generic way. You only need to implement abstract ViewHolderBase, instantiate new FastListAdapter and assign it to ListView Adapter. You can find example implementation in ApkViewHolder, easy

Samsung Posts Its Own June OTA Security Bulletin With Additional Vulnerabilities Fixe

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
A little earlier today Google posted the Android 6.0.1 security updates for June to the AOSP changelog. Being the responsible Android citizen that it is (well, most of the time), Samsung has immediately followed suit with its own list of code updates. These are the issues that are problems for specific Samsung devices and their related software builds, or at least, the ones that have been addressed since the same security bulletin last month. As usual, they're limited to "major flagship models."
The list contains five items on top of the security patches mentioned by Google's own changelog: an external storage vulnerability, control through a locked device, a minor SIM lock issue, an email encryption configuration error, and a certificate signature bypass check for fingerprint readers. The problems ranged from high severity, allowing malicious app installations or possibly even total device control, to low severity, causing minor bugs and usability issues. Builds from Android 4.4 all the way through 6.0 were affected by different problems.
This bulletin is just documentation of the bugs themselves and the fact that the patches to repair them are ready. It will probably be several weeks or even months before they make it to phones... and it's almost certain that a good number of older devices won't ever be patched. And that's without taking the delay of carrier certification for OTA updates into account.
Source: http://security.samsungmobile.com/smrupdate.html
http://www.androidpolice.com/2016/06/06/samsung-posts-its-own-june-ota-security-bulletin-with-additional-vulnerabilities-fixed/
When are we getting this update to S7 Edge in India?

[APP][4.0+] Simple Password Manager - With full control on encryption method [v2.04]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Simple Password Manager is an easy to use, ad free, Password Manager App which gives you full control over the encryption method and does not require any special permissions.
It has over 7,500 installs on Google Play, as on date, since May 2012, and recently I made some significant changes to the app, releasing version 2.0. You can store multiple username/passwords and only have to remember one strong Master Password. This is used to encrypt the other passwords securely using a key derivation function.
You can choose the number of bits and iterations and the key derivation function as per your security needs and phone processing power. For now, I have only enabled PBKDF2, since it is the best natively supported KDF, and you will get HMAC SHA1 variant till Android 7.1, and with SHA256 AND SHA512 in Android 8. Nevertheless, I can easily enable Blowfish or any other KDF supported on your device, if requested, and play to include Argon 2d in future updates.
I request you to try out the app, rate and review, and generally give me feedback to improve it. Do let me know what you like or dislike. Do you find it easy to use or confusing, etc.
Like app on Facebook!
I just updated this to version 2.05, which makes it much easier to get started with the app and is available in five languages - English, French, Spanish, Chinese (Simplified/Traditional), and Hindi... with Russian on its way.

[DEV] Boot Control

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Boot Control is an Android app that toggles the active boot slot.
Notes
It uses the same HIDL interface as bootctl to read the data and make the change.
Credits
@badabing2003 for the idea and for testing the many builds of both the app and bootctl
Latest Update
2023-06-22 v1.0.0-alpha02
capntrips said:
(...)
Latest Update
2023-06-22 v1.0.0-alpha02
Click to expand...
Click to collapse
BootControl-main.zip = 120 KB
BootControl-v1.0.0-alpha02.apk = 38.8 MB
Why such a drastic difference between SC and APK?
ze7zez said:
Why such a drastic difference between SC and APK?
Click to expand...
Click to collapse
The size of the source code has basically zero bearing on the size of the APK. As for why the APK is so large, I can sum that up with a link to one line in the app's build.gradle file.
The longer explanation is R8 breaks HIDL for some reason. I tried a variety of ProGuard rules with no luck. If I build it with Soong instead of Gradle it works fine, but it can't be installed on older devices. I may have been able to find a workaround for the latter issue, but it's much more convenient to build it with Gradle. Beyond that, the Soong build had issues with the Java HIDL interface, so I had to make a C++ library for HIDL and use JNI to interface with that, making the whole thing a bit more complex.
The broken minified Gradle build is ~8mb and the limited Soong build is ~14mb.
@capntrips
On p6, you need to disable verity (but not verification) in vbmeta on both slots to get Boot Control to switch slots without getting a corruption message.
Can the tool be modified to perform this task?

Categories

Resources