Tuesday, May 24, 2016

What Up

Long time no post.

pstate-frequency was updated to version 3.3.3 (.3.3.3.3.3.3) which brings support (again) for acpi-cpufreq. It wasn't that hard to support the older driver, although I did run into some bugs from releasing without adequate testing, but they should hopefully be fixed now. If there are bugs, or something doesn't quite work the way you expect, file a GitHub issue.

steam-wrapper was updated to version 0.2.6, which brings some new behavior. By default it will not remove any of the outdated steam runtime libraries, but rather will override the LD_PRELOAD path to point to the newer libraries instead. The older destructive functionality still exists by passing the -d | --delete-stale flag to steam-wrapper if that's more your thing. The linking of the flash 32 bit library will be removed in the next version, user be warned.

update-hosts got updated (haha.) to a new version whose number escapes me at the moment, but it adds in hosts file sources from the disconnect project as well as a new list from the malwaredomains tracking site, the zeus project, and a ransomware tracker. So hopefully more things will be caught. That being said, I don't want to block too many things, as this may end up breaking legitimate sites as well. I have tried to maintain the whitelist to mirror the uBlock Origin Unbreak list, but seeing as we are dealing with a very binary all-or-nothing style of filtering hosts, it is obviously not as robust. It is also updated by hand, meaning I will miss things along the way. Open a GitHub issue if you see anything that I have missed.

PadLock will get a small update that filters out all window events for only those that come from Activity instances. This should clean up the actual LockService code and hopefully make locking more reliable. I will also be adding an option (off by default) that will check for a lock entry every time the activity class changes. This is to combat a potential security issue where, if the main entry point of the Application (usually launcher activity) is left unlocked, then the entire application is potentially view-able as long as the currently observed package does not change. Check the source, while I have not actually tried to produce the bug, it is theoretically possible. The reason that the option is left off by default is due to the fact that when the application is "properly" locked, causing a new lock request on each activity change only makes things more annoying.

Finally work has begun on re-working basically all of SoftGlow as I am curious to see how it will perform in a more modern Android environment. Of course, with the announced changes to how background services are being restricted in the future Android versions, I will need to go back to the drawing board regarding how the application actually works.

More to come.

========================
Follow pyamsoft around the Web for updates and announcements about the newest applications!
Like what I do?

Send me an email at: pyam.soft@gmail.com
Or find me online at: https://pyamsoft.blogspot.com

Follow my FaceBook Page
Follow my Google+ Page
=========================