11–20 of 42 posts
Earlier quoted context omitted.
Just update packages to the latest, patched version. What so difficult about it?
If this is based on a popular distro, maybe; but if you wanted to loosen up a Linux box, you can build a freak from pieces that no one would find lineage for, much less a repo.
Earlier quoted context omitted.
Just update packages to the latest, patched version. What so difficult about it?
If this is based on a popular distro, maybe; but if you wanted to loosen up a Linux box, you can build a freak from pieces that no one would find lineage for, much less a repo.
He specifically mentions that all the softwares are vulnerable:
"Its developers have spent hours stuffing it with broken, ill-configured, outdated, and exploitable software that makes it vulnerable to attacks."
Just replace them with the latest, patched, default configured version.
Earlier quoted context omitted.
If this is based on a popular distro, maybe; but if you wanted to loosen up a Linux box, you can build a freak from pieces that no one would find lineage for, much less a repo.
There are other ways to update software..
Running a Bastille script on the box would give you a quick TODO list. Pushing it to "production" and getting a few servers up and running, across version incompatibilities, would prove a bit more interesting. Running it under an older 2.4.x or 2.2.x kernel, doubly so.
Securing this beast should serve as a nice training course for any sysadmin; bonus points if you start handing out shell accounts to anonymous people in certain neighborhoods of EFNet.
Just update packages to the latest, patched version. What so difficult about it?
Earlier quoted context omitted.
If this is based on a popular distro, maybe; but if you wanted to loosen up a Linux box, you can build a freak from pieces that no one would find lineage for, much less a repo.
umm no. He specifically mentions that all the softwares are vulnerable: "Its developers have spent hours stuffing it with broken, ill-configured, outdated, and exploitable software that makes it vulnerable to attacks." Just replace them with the latest, patched, default configured version.
Earlier quoted context omitted.
umm no. He specifically mentions that all the softwares are vulnerable: "Its developers have spent hours stuffing it with broken, ill-configured, outdated, and exploitable software that makes it vulnerable to attacks." Just replace them with the latest, patched, default configured version.
What pieces of software do you replace? How do you replace it? Remember that it likely doesn't some with anything like apt to make this easy.
Securing this beast should serve as a nice training course for any sysadmin; bonus points if you start handing out shell accounts to anonymous people in certain neighborhoods of EFNet.
Earlier quoted context omitted.
Technically speaking, how would an OS avoid that issue, without breaking compatibility (unless that is acceptable)?
You can't be bug compatible for things that violate the processor's protection protocol. Access to certain bits of the EFLAGS register is unavailable to unprivileged code. In fact. Just because you were allowed to raid and pillage by Microsoft for a few years doesn't mean it's the norm.
Earlier quoted context omitted.
umm no. He specifically mentions that all the softwares are vulnerable: "Its developers have spent hours stuffing it with broken, ill-configured, outdated, and exploitable software that makes it vulnerable to attacks." Just replace them with the latest, patched, default configured version.
What pieces of software do you replace? How do you replace it? Remember that it likely doesn't some with anything like apt to make this easy.