Do you often use VeraCrypt on a company-managed device? I'm sure if you do then it's with the knowledge and consent of your IT department and they'll be responsible for managing any consequences of the VeraCrypt issue according to their official policy as well.
Yeah, I read through those... and found that while it described a vulnerability, it was still light on actual exploit details.
Did they compromise the inward facing web interface, or an outward web interface? Did they do it through social engineering, or through malware running on devices on the internal network? Was the malware persistent or was it a drive-by instance running a portscanner in a browser instance?
Basically, the question I have is - would flashing say, openWRT on these devices been enough to prevent network intrusion, or were they already inside the gates to begin with?
The linked articles are remarkably light on details of how the routers were compromised. Were they breached from the internet side due to backdoors or poorly implemented services? Was it some sort of configuration default for remote administration that was just bulk abused? Or were the routers compromised from inside the network by malware running locally on machines, or on malware compromised pages? Was it due to remote code execution or was it due to default admin credentials or easily guessable passwords?
Kind of hard to defend against a threat if they won't tell you how the deed was done.
That would defeat the entire purpose of keeping that machine alive.
Wasn't there an 80186? That literally nobody built anything with? Like, it was almost a proof of concept?
Just today I noted that GIMP 3.2.2 (an application, not an OS) has dropped support for 32-bit x86.
You are welcome to continue development on support for the 486 if you need continued support for it. The kernel is open source and you can easily clone yourself a local repo and continue 486 support maintenance while merging in new features as time goes on.
My very first linux box, which I still have and is still running today, is still on RedHat 3.0.3 that I got on a CD in a book from the Media Play in Poughkeepsie NY in 1996. Granted it is completely useless except as a samba server sharing the 1.6GB hard disk that is still in it (and still works). But, I keep it for posterity, and because I like having a monitor with xearth on it.
I could probably put a newer distribution on it but with only 24MB of RAM, the newer stuff would choke out on it.
What's more, you really have to know what you're doing to coax it into re-using code, rather than rewriting the same functionality with each prompt.
Can it clone proprietary software and turn it into an open source project?
If so, then I think the tradeoff is fair.
JavaScript is actually a pretty interesting, powerful language, but one with quite a few problems. (I recommend the book JavaScript: The Good Parts by Douglas Crockford if you want to learn more about that.) TypeScript solves some, but by no means all, of those problems. From what I've heard, it's increasingly popular.
It was pity stayed his hand. "Pity I don't have any more bullets," thought Frito. -- _Bored_of_the_Rings_, a Harvard Lampoon parody of Tolkein
