Qonversion - Mobile app subscription analytics
OpenSSL
Our great sponsors
Qonversion - Mobile app subscription analytics | OpenSSL | |
---|---|---|
8 | 149 | |
281 | 24,142 | |
0.7% | 1.5% | |
8.4 | 9.9 | |
about 22 hours ago | 6 days ago | |
Objective-C | C | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Qonversion - Mobile app subscription analytics
-
WWDC22 overview: how to integrate and migrate in-app purchases to App Store Server API
If you still have any questions about the logic behind these updates, please feel free to reach out to us. Qonversion provides a complete cross-platform infrastructure that allows you to make and restore purchases, validate receipts, and provide your app with an accurate subscription status without the need to build your server.
-
What’s new with in-app purchases: WWDC 2022 overview
We know a thing or two about in-app purchases as Qonversion provides a complete cross-platform infrastructure that allows you to create and restore purchases, validate receipts, and provide your app with an accurate subscription status without the need to build your server. So, If you’d like to learn more about it or have any questions, feel free to ping me in comments here.
-
The new App Transaction API, Enhancements to StoreKit 2 and other WWDC22 updates for in-app purchases
Once you’ve implemented in-app purchases, don’t forget to use the analytics tools to measure how much revenue each of your products brings. Qonversion provides a complete infrastructure for in-app purchases and allows you to create and restore purchases, validate receipts, and provide your app with an accurate subscription status without a need to build your own server. If you’d like to learn more on how to set up and analyze in-app purchases and subscriptions, please read our documentation or message us here.
-
The Ultimate Guide to Subscription Testing on Android
We hope you successfully tested your subscriptions and didn’t find any bugs. But even if you did, it’s great news to find them before publishing your app. Implementation of subscriptions has never been easy and requires tremendous resources for developing access management logic — there are so many scenarios and use cases. Qonversion significantly simplifies this process by providing you with ready-to-go solutions so you can use purchase, restore and checkPermissions methods and manage your subscriptions without any issues. In any case, whether you use an in-house solution or Qonversion, please do your testing — it is a must. Remember: It is better to be safe than sorry; the trust of your users is everything.
-
Setting Up Consumable and Non-consumable In-App Purchases
Before we get started with the creation of consumable and non-consumable purchases, make sure that you already have a Qonversion account and have created your project and register the app.
-
Apphud VS Qonversion - Mobile app subscription analytics - a user suggested alternative
2 projects | 23 Sep 2021
-
Adapty VS Qonversion - Mobile app subscription analytics - a user suggested alternative
2 projects | 23 Sep 2021
-
purchases-ios VS Qonversion - Mobile app subscription analytics - a user suggested alternative
2 projects | 23 Sep 2021
OpenSSL
-
Heartbleed and XZ Backdoor Learnings: Open Source Infrastructure Can Be Improved Efficiently With Moderate Funding
Today, April 7th, 2024, marks the 10-year anniversary since CVE-2014-0160 was published. This security vulnerability known as "Heartbleed" was a flaw in the OpenSSL cryptography software, the most popular option to implement Transport Layer Security (TLS). In more layman's terms, if you type https:// in your browser address bar, chances are high that you are interacting with OpenSSL.
-
Ask HN: How does the xz backdoor replace RSA_public_decrypt?
At this point I pretty much understand the entire process on how the xz backdoor came to be: its execution stages, extraction from binary "test" files etc. But one thing puzzles me: how can the ifunc mechanism be used to replace something like RSA_public_decrypt? Granted this probably stems from my lack of understanding of ifunc, but I was under the impression that in order for the ifunc mechanism to work in your code, you have to explicitly mark specific function with multiple implementations with __attribute__ ((ifunc ("the_resolver_function"))). Looking at the source code of the RSA function in question, ifunc attribute isn't present:
https://github.com/openssl/openssl/blob/master/crypto/rsa/rsa_crpt.c#L51
So how does the backdoor actually replace the call? Does this means that the ifunc mechanism can be used to override pretty much anything on the system?
-
Use of HTTPS Resource Records
OpenSSL and Go crypt/tls has no support yet, so none of the webservers that depend on them support it. Apache, Nginx, and Caddy, they all need upstream ECH support first.
- https://github.com/openssl/openssl/issues/7482
- https://github.com/openssl/openssl/pull/22938
- https://github.com/golang/go/issues/63369
- openssl-3.2.0 released
- Large performance degradation in OpenSSL 3
- OpenSSL 3.2 Alpha 2
-
Encrypted Client Hello – the last puzzle piece to privacy
If I'm understanding the draft correctly, I think the webserver you're hosting your sites on would need it implemented as it requires private keys and ECH configuration. In the example of nginx since it uses openssl, openssl would need to implement it. I found an issue on their Github but it's still open: https://github.com/openssl/openssl/issues/7482
- eBPF Practical Tutorial: Capturing SSL/TLS Plain Text Data Using uprobe
-
OpenSSL Versions... whats the plan here
I confirmed that the systm was on 1.1.1f with openssl version command. Hmm...... I check the openssl version in the repo with apt list... LOL package names wernt helpful. finally went to the repo pages and found that its still on 1.1.1f, https://launchpad.net/ubuntu/+source/openssl. Meenwhile I looked up the version history on https://www.openssl.org/ and saw that 1.1.1v was released at the beginning of this month... ok. I can understand it it was out less then 30 days. I looked up when f came out, end of MARCH 2020. NEARLY 3-1/2 YEARS
- I am looking for a troubled/bad open source codebase
What are some alternatives?
Bugsnag - BugSnag error monitoring & exception reporter for iOS, macOS, tvOS and watchOS
GnuTLS - GnuTLS
MOCA Analytics - MOCA Proximity and Analytics SDK for iOS
Crypto++ - free C++ class library of cryptographic schemes
Smartlook iOS SDK
mbedTLS - An open source, portable, easy to use, readable and flexible TLS library, and reference implementation of the PSA Cryptography API. Releases are on a varying cadence, typically around 3 - 6 months between releases.
Countly - Countly Product Analytics iOS SDK with macOS, watchOS and tvOS support.
libsodium - A modern, portable, easy to use crypto library.
Liquid Analytics - Liquid SDK (iOS)
LibreSSL - LibreSSL Portable itself. This includes the build scaffold and compatibility layer that builds portable LibreSSL from the OpenBSD source code. Pull requests or patches sent to [email protected] are welcome.
GTrack
cfssl - CFSSL: Cloudflare's PKI and TLS toolkit