You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Modern computer programming is too much of a moving target. And, in the name of speed, we sacrifice a lot of security-first principles. https://en.m.wikipedia.org/wiki/Meltdown_(security_vulnerability) … for example. Compare to AS/400 architecture, where CPU are designed less efficiently in order to be secure.
AS/400 isn't a CPU architecture though, it uses machine independent bytecode (like Java, Android dex, LLVM IR in iOS apps, and other similar modern versions). The actual CPUs used by AS/400 have been POWER for a while and certainly are vulnerable to Spectre subsets.
By the way, z/OS and friends are lacking many modern security mitigations. I wrote a CTF for z/OS USS that was a trivial stack overflow, which would've instantly been caught by stack cookies on any modern system, and made harder to exploit by ASLR.
As far as I can tell, any idea that all that big iron stuff is "secure" is a bunch of wishful thinking. Nobody is auditing those systems from the POV of modern exploitation because they're so niche and proprietary, so nobody is pumping out the CVEs. It's security by obscurity.
I thought it used to be? Bsaed on 48-bit System/38 CISC? https://en.wikipedia.org/wiki/IBM_System_i#Hardware … https://itstillworks.com/as400-processor-specifications-7412224.html … the POWER stuff is designed to emulate the AS/400 stuff very closely, down to the timing level even I had thought. (Tracking down references on the web is tough tho)
AIUI it was always bytecode ("TIMI") with ahead of time compilation, that was the whole point of the design. So they switched the backend CPU from that CISC thing to POWER at some point, much like Android compiles the same bytecode to x86 and ARM :-)
Are they still limited to 10 char passwords too?
I think the limit is 128 now, going by something I read about IBM i (the new name for the system derived from AS/400)
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
