Firebase support bounty
This is a bounty to promote development interest and find a solution to the many apps that fail because of the migration from GCM (Google Cloud Messaging) to FCM (Firebase Cloud Messaging)
https://www.bountysource.com/issues/51518216-gcm-fcm-update-needed-for-push-messaging
Follow the conversation in the latest pages of MicroG XDA thread and on GitHub:
https://forum.xda-developers.com/android/apps-games/app-microg-gmscore-floss-play-services-t3217616
https://github.com/microg
The Deprecation of GCM for FCM
by @ Shadow53
https://shadow53.com/post/whats-new-pussycat/#the-deprecation-of-gcm-for-fcm
"Users of MicroG on Android Oreo will notice that their apps using Google for notifications are no longer receiving them. This is because of Google pushing Firebase Cloud Messaging (FCM) as a replacement for Google Cloud Messaging (GCM) for notifications. MicroG currently only has support for the older GCM protocol, so apps using the newer FCM cannot register for notifications.
Some people have found that installing older versions of the app will cause it to register via GCM, then an update will continue using GCM. The problem of lacking support for FCM still remains.
A solution to this problem is to just not use apps that require Play Services at all, and request that developers of apps you use requiring Play Services implement an alternate method of pushing notifications.
This doesn’t work if you need a certain app that still requires Play Services, and certainly won’t work if trying to convince someone to switch to using MicroG. So, we need to get FCM implemented. Open Source enthusiasts will suggest that I do it if I think it needs to be done - I would, and I may in the future, but not any time soon. I have too many projects already that need to be worked on. So here’s hoping someone else is able to get something working…"
#bounty #firebase #fcm
This is a bounty to promote development interest and find a solution to the many apps that fail because of the migration from GCM (Google Cloud Messaging) to FCM (Firebase Cloud Messaging)
https://www.bountysource.com/issues/51518216-gcm-fcm-update-needed-for-push-messaging
Follow the conversation in the latest pages of MicroG XDA thread and on GitHub:
https://forum.xda-developers.com/android/apps-games/app-microg-gmscore-floss-play-services-t3217616
https://github.com/microg
The Deprecation of GCM for FCM
by @ Shadow53
https://shadow53.com/post/whats-new-pussycat/#the-deprecation-of-gcm-for-fcm
"Users of MicroG on Android Oreo will notice that their apps using Google for notifications are no longer receiving them. This is because of Google pushing Firebase Cloud Messaging (FCM) as a replacement for Google Cloud Messaging (GCM) for notifications. MicroG currently only has support for the older GCM protocol, so apps using the newer FCM cannot register for notifications.
Some people have found that installing older versions of the app will cause it to register via GCM, then an update will continue using GCM. The problem of lacking support for FCM still remains.
A solution to this problem is to just not use apps that require Play Services at all, and request that developers of apps you use requiring Play Services implement an alternate method of pushing notifications.
This doesn’t work if you need a certain app that still requires Play Services, and certainly won’t work if trying to convince someone to switch to using MicroG. So, we need to get FCM implemented. Open Source enthusiasts will suggest that I do it if I think it needs to be done - I would, and I may in the future, but not any time soon. I have too many projects already that need to be worked on. So here’s hoping someone else is able to get something working…"
#bounty #firebase #fcm
Bountysource
A $623 Bounty has been paid out for microg/GmsCore
GCM -> FCM Update needed for push messaging [$623 PAID] [$623 awarded]
Media is too big
VIEW IN TELEGRAM
The Most Dangerous Codec in the World: Finding and Exploiting Vulnerabilities in H.264 Decoders
Modern video encoding standards such as H.264 are a marvel of hidden complexity. But with hidden complexity comes hidden #security risk. #Decoding video today involves interacting with dedicated #hardware accelerators and the #proprietary, privileged software components used to drive (#driver) them. The video #decoder ecosystem is obscure, opaque, diverse, highly privileged, largely untested, and highly exposed -- a dangerous combination.
We introduce H26Forge, a framework that carefully crafts #video files to expose edge cases in H.264 decoders....
By: Stephen Checkoway , Hovav Shacham , Willy Vasquez
Full Abstract and Presentation Materials
#VideoEncoding #Vulnerabilities #Security #Codec #H264 #Exploit
Modern video encoding standards such as H.264 are a marvel of hidden complexity. But with hidden complexity comes hidden #security risk. #Decoding video today involves interacting with dedicated #hardware accelerators and the #proprietary, privileged software components used to drive (#driver) them. The video #decoder ecosystem is obscure, opaque, diverse, highly privileged, largely untested, and highly exposed -- a dangerous combination.
We introduce H26Forge, a framework that carefully crafts #video files to expose edge cases in H.264 decoders....
By: Stephen Checkoway , Hovav Shacham , Willy Vasquez
Full Abstract and Presentation Materials
#VideoEncoding #Vulnerabilities #Security #Codec #H264 #Exploit