OpenSSL VS Telegram-iOS

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.

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?

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

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

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

hi, i downloaded telegram ipa from [github releasase](https://github.com/TelegramMessenger/Telegram-iOS/releases/tag/build-25780), and sideloaded it to iPhone XR, when i open it on iPhone, it will show a blank screen then a black screen and still.

Telegrams’ app is a good bit of swift: https://github.com/TelegramMessenger/Telegram-iOS

I've tried again and again to engage Telegram in a variety of places. If I don't catch a bug when it's in beta, I can't even discuss it in the beta group. But oh wait, I can't catch it on the beta because I got kicked off the beta. The GitHub thread started in 2020 hasn't received any meaningful responses in a long time--arguably ever. Issues on the bug tracker get ignored and go into a black hole if they don't get enough upvotes.

https://github.com/TelegramMessenger/Telegram-iOS/actions/ru...

(uses this script: https://github.com/TelegramMessenger/Telegram-iOS/blob/maste...)

And here are few recent examples of them helping people to solve build issues:

The Telegram app is native: https://github.com/TelegramMessenger/Telegram-iOS

From GitHub https://github.com/TelegramMessenger/Telegram-iOS/releases/tag/build-23987

Same issue here. You should open an issue on https://github.com/TelegramMessenger/Telegram-iOS, I'll upvote it

Source

You can literally download and compile it yourself right now.

Telegram is open source. You can see the implementation of the share controller here.