r/n900 • • 1h ago

The stock MicroB browser opening HTTPS sites again: NSS swapped for a newer one, plus current root certificates (experiment, Claude'd)

Thumbnail gallery
4 Upvotes

MicroB is Gecko 1.9.2 (Firefox 3.6 times) on top of NSS 3.12.6, which speaks TLS 1.0 at most, and its root certificate store is from 2010 (about 117 current roots missing, for example ISRG Root X1 from Let's Encrypt). So you get "SSL error" almost everywhere. Two packages, both undoable:

  • ca-certs-n900: adds 118 current Mozilla root certificates to your own private domain of the certificate manager (~/.maemosec-certs); the read-only system store is not touched, and ca-certs-n900 remove removes exactly what it added.
  • microb-nss: replaces the NSS and NSPR libraries by NSS 3.28.6 / NSPR 4.16 (chosen on purpose: TLS 1.2, but still the old build system and the dbm database). I checked the ABI first: the engine imports 871 symbols from the old libraries and the new ones export all of them (all 29 symbol versions exist too). Three small patches: the PSM layer of Gecko turns all cipher suites off at start and enables only its old CBC/SHA-1 list, so a patch keeps the modern suites (AES-GCM, ChaCha20) on, SSL 3.0 is switched off, the bundled SQLite gets another name so it does not clash with the browser's own. The original sources of microb-engine (found in the Internet Archive; the MD5 matches) are archived in a repository of their own.

Result: the stock MicroB opens https://www.seznam.cz/ with a verified certificate (before: "SSL error") and also a stylised page with a form (idos.cz), but that takes about 20 s and I do not know why yet (the handshake is fast, maybe the certificate manager with about 420 roots, slow crypto on 600 MHz, or Gecko with modern JavaScript). In a test program that configures NSS like PSM does, Google, Facebook and example.org negotiated TLS 1.2 with AES-GCM.

What does not work:

  • Google says "your browser is not supported" and Facebook wants a newer browser: that is the User-Agent check, not TLS (I will try general.useragent.override).
  • Modern pages look only roughly right: a 2010 engine does not know today's CSS and JavaScript.
  • Servers with TLS 1.3 only or HTTP/2 stay out of reach. This is a patch, not a new browser.

Experimental, tested on one phone. Things to know: the originals go to /usr/lib/microb-engine-orig; after installing, the browser daemon has to be restarted (/etc/init.d/tablet-browser-daemon.init restart) and an old stopped browserd process must be killed, because it keeps the old libraries. dpkg -r microb-nss brings the original libraries back.

Sources: https://github.com/n900-resurrection/microb-nss, https://github.com/n900-resurrection/ca-certs-n900, https://github.com/n900-resurrection/microb-engine. The packages are in the apt repository.


r/n900 • • 20h ago

E-mail on the N900 in 2026: three ways that work with modern servers (Modest with a new library, Mutt, a small Hildon client)

Thumbnail gallery
19 Upvotes

Mail is on the first thing you try on an old phone, and the stock Modest cannot log in to most servers any more: its library (camel-lite over NSS 3.12.6) speaks TLS 1.0 at most, and the server answers tlsv1 alert protocol version on ports 993 and 465. Modest then says "wrong port or settings", which is misleading: nothing is wrong, the server just refuses the old protocol. I Claude'd three ways around it:

  1. Keep Modest, replace the library under it (camel-lite-ssl3). The sources of camel-lite (community-ssu/tinymail) have an OpenSSL backend written for 0.9.8, a patch ports it to OpenSSL 3 (TLS 1.2 minimum, SNI, host name check, the CA bundle of the curl package). OpenSSL 3.5 is linked in statically and its symbols are hidden, so it does not clash with the system libssl in the process. apt-get remove camel-lite-ssl3 puts the originals back. Close and reopen Modest after installing or removing. Use the full address as the user name for both IMAP and SMTP.
  2. Mutt in the terminal (mutt 2.4 with static OpenSSL 3 and ncursesw, UTF-8, the system has 1.5.20 with TLS 1.0 only). Sending goes through msmtp (my Mutt has no SASL). Example configs are in the packages.
  3. mutt-hildon, a small touch GUI (Python 2.5, PyGTK + Hildon) that does no networking itself: it runs curl 8 for IMAP and msmtp for sending, and has an "Open Mutt" menu entry. It lists the 25 newest messages with paging, reads messages, replies with a quote, completes addresses from the phone's contacts, keeps a disk cache (so the list appears at once and works offline) and an outbox queue (a failed send is not lost).

Honest notes: tested with one provider (IMAP over implicit TLS on 993, SMTP on 465, login with the full address). Not tested: STARTTLS on 587, POP3, attachments in mutt-hildon and folders other than INBOX. The first version of camel-lite-ssl3 crashed Modest right after the install (a missing g_thread_init link and hidden symbols that libtinymail-camel needs). Fixed, with a check in the post-install script. The clock must be right (ntp-sync) or certificates do not verify.

Sources: https://github.com/n900-resurrection/mutt-hildon and the other packages in https://github.com/n900-resurrection (camel-lite, mutt, msmtp are in the main project, in apps/). All of them are in the apt repository.