firefox-ios VS OpenSSL

Users are complaining that the latest Firefox for iOS update has removed the "Dark mode" option from the menu:[1]

> I suffer from Diabetic Retinopathy and hence photophobia. To me, this removal is an Accessability issue.

A forum moderator who's in touch with the developers said days ago that this is an experiment affecting half of the userbase:[2]

> The team is currently doing an experiment. Since March 15, 50% of users no longer see Night Mode switch from the hamburger menu. We're using this experiment to monitor and evaluate the impact of removing, so it'll be hugely valuable to hear your feedback around this feature. Thanks!

However, Mozilla's iOS team manager doesn't know about this huge experiment and think it is a bug:[3]

> Moving Focus into the Firefox repo so it can get more love and support. This happened last release and may be the culprit that broke dark mode. We're looking into this right now.

[1] https://github.com/mozilla-mobile/firefox-ios/issues/19365#issuecomment-2018447405

Yeah, Orion's support for Firefox extensions is a big red flag. These 2 issues on the Firefox-iOS tracker[0,1] around extensions and content blockers have long mentioned Orion, but there's no response from Mozilla.

[0]: https://github.com/mozilla-mobile/firefox-ios/issues/7374

[1]: https://github.com/mozilla-mobile/firefox-ios/issues/9155

If you keep being logged out, open this page and click on New issue.

Follow this bug report: Tabs reload when switching to another tab or app and screen remains blank in Firefox for iOS.

Please file an issue on Bugzilla (Android) or GitHub (iOS).

Please open this page and click on New issue to report bugs affecting Firefox for iOS.

If you have a GitHub account, subscribe to this issue: Extensions support on iOS.

https://github.com/mozilla-mobile/firefox-ios/commit/686d36402c6a956f460abafc8f1fe19a7887a2f3 landed in v38, so it looks like v37 was the last to support iOS 12.

When you use Reader View, Firefox parses the text of the webpage and loads it as a local page. It isn't supposed to show a red slash, though. Reader Mode shows a neutral icon (📄) on the desktop version. Please open this page and click on New Issue to report this to Mozilla, and then share the link with us.

ENV OPENSSL_PREFIX=/opt/openssl ENV SSL_CERT_FILE=/etc/ssl/certs/ca-certificates.crt WORKDIR /tmp RUN git clone --branch OpenSSL_1_0_2n https://github.com/openssl/openssl.git RUN cd openssl RUN ./config shared --prefix=$OPENSSL_PREFIX --openssldir=$OPENSSL_PREFIX/ssl RUN make RUN make install RUN rvm install 2.6.0 -C --with-openssl-dir=$OPENSSL_PREFIX ENV PATH /usr/local/rvm/bin:$PATH RUN rvm --default use ruby-2.6.0 ENV PATH /usr/local/rvm/bin:/usr/local/rvm/rubies/ruby-2.6.0/bin:$PATH ENV GEM_HOME /usr/local/rvm/rubies/ruby-2.6.0/lib/ruby/gems/2.6.0

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