3 ms·

I was going to check the status of mksh (the Android system shell), but the project page returns: "Unavailable For Legal Reasons - Sorry, no detailled error me

by chasil 2y ago

I was going to check the status of mksh (the Android system shell), but the project page returns: "Unavailable For Legal Reasons - Sorry, no detailled error message available." http://www.mirbsd.org/mksh.htm http://www.mirbsd.org/mksh.htm The Android system shell is now abandoned? This is also in rhel9 basesos.

talideon 2y ago
Fine for me. I just got a HTTP warning and nothing else. ~~I believe Android uses toybox, not mksh.~~ It does use toybox, but toybox doesn't appear to include a shell.
chaosite 2y ago
Looks fine here, maybe they're blocking your IP range for some reason?
kbolino 2y ago
It's blocked for me too, but only on my home Internet (Xfinity), not my phone (Google Fi/T-Mobile).
- chasil 2y ago
  I see it on my T-Mobile device also. Strange.
- torstenvl 2y ago
  Works fine for me on Xfinity Home via WiFi, Xfinity Mobile, T-Mobile, and Visible by Verizon.
  - kbolino 2y ago
    Whatever the issue was, it seems to have been resolved sometime after I last checked.
tux3 2y ago
Works from an EU IP, so whatever it is, it's probably not GDPR?
deleted 2y ago
[deleted]
fragmede 2y ago
What's your browser? The server is using an old TLS version which is no longer supported, and some clients will try https and fail there and not try http.
- chasil 2y ago
  I'm using Edge on my corporate desktop. Edge first tries TLS and comes back with: "SSL handshake error '-1' sslerr='1' sslerrdesc='error:1425F102:SSL routines:ssl_choose_client_version:unsupported protocol' sslerrfunc='607' sslerrreason='258'" Setting to http:// http:// results the the above error, along with "httpd/3.30A Server at www.mirbsd.org Port 80" - I think that the target itself is blocking me.
blueflow 2y ago
> Android system shell This hurt a little.