MESSAGE
| DATE | 2014-09-19 |
| FROM | Ruben Safir
|
| SUBJECT | Re: [NYLXS - HANGOUT] Apache Security tips
|
On 09/17/2014 12:29 AM, Paul Robert Marino wrote:
> Rubin
>
Ruben
Ruben
or if you want Reuvain
<module independently you don't need to recompile all of apache. Further
more I don't know of a distro which doesn't include mod_rewrite its just
your custom compiled version that has this issue, and you can fix it
easily.>>
I said that. I don't want to use it apache mod_rewrite, but for others,
the article is a good security lesson. For me, learning rewrite is just
learning another programming jaargon that I don't need.
>
> Finally the reason you are ripping out all of this stuff is you still
> caught in a very UNIX design way of thinking.
After reading your criticism, frankly, I still don't get it, but more
importantly it doesn't really concern me. We are of different
generations, but I'm not of the Unix generation either. Most of those
people are about 10 years older than I am. My experience was mostly
with TSR80's and I can certainly not be categorized as having my brain
soaked in commercial Unix experiences. To my knowledge, FWIW, I've
never used Unix. My philosophy on computers is simple. I like
computers and systems that let me control my box to my liking. That
implies that things should be as simple as possible and as easy to
adjust and hack as possible. The means when I save files, they go where
I tell them to on the file system, that config files are to be self
explanatory and easy to read, and the system should mostly say the fuck
out of my way. I don't want to compete with an artificial intelligence
written by someone else as to how I want my routing and DNS to work. I
adapt tools as they are useful, and find no reason to have things
change, just because someone else is bored and need to make a name for
themselves.
I like systems based on genuine math and the science of human interface
design. I expect them to function for the humans who use them, to
expect that the humans are reasonable intelligent and be educated as to
the basics of computer science and design, and that the systems
shouldn't work against them, and obfuscate the systems function and
workings. Most of all, KISS KISS KISS.
Anything that doesn't conform to the above axioms as computer bugs.
As for the Unix design, Unix was largely a product of academic computer
science principles. Starting with Mutics, until ATT's research
department, especially researchers like Ken Thompson
, Dennis Ritchie
, Doug McIlroy
, and Joe Ossanna
, who reworked it from
scratch based on their experience. They added things based on strong
comp/sci mathmatics, such as creating a hierarchical database for the
file system which was theorized at the time. It wasn't so obvious in
those days to have file systems with this structure. They were kicking
around the idea of relational and network systems of the file system
database. They also developed the concept of computing processes as
distrinct components, which was valid mathematical and scientifically
approach. Up until that time was not implemented. They atomized every
computer function to its most indivisible aspect, and created a
structure to define these aspects and stitch them together into the
unified system. These included theoretical aspects such as devices,
files, users, semiphores, programs, functions etc.
They centered the computer system on communications, breaking through
with text editing and font creation, developed a core of text based
programming tools for human communication to include, VI, SED, GREP, ED,
and publishing breaktroughs with ROFF and TROFF.. They pioneers
computer communications defining communications through atomics like
sockets, and pipes.
The redesigned the core of programming languages to move them off the
launchpad of machine based programming with the invention and
development of C, essentially unlocking programming to the masses. C
Programming was based on the mathematical model of type theory that was
invented by Bertrand Russell
in the early twentieth
century to respond to problems in set theory paradigms.
None of this was obvious in the mid-20th century and certainly none of
it was implemented into a unified computing system until Unix. Unix
literally brought order to chaos. Unix might well be the last research
driven, mathematically valid construction of an OS. The derivation of
GNU systems from Unix was more than an accident, as Richard likes to
imply (It has these little parts and we can make them talk to each other
and so this was good).
There may come a day when the Unix based computer design might well be
replaced with something more useful. But that is not likely in either
of our lifetimes. Quantum computing might require different
paradigms...or maybe not. Whenever someone tells you they're crap is a
new way of looking at computers and your stuck in the old ways, they are
full of shit. Unix preceded my computing career, and it will far
outlive me as the bases for digital communications in the world. They
are trying to put one over on you and sell you some difficult to use,
impossible to configure slaveware. The first thing is to ask them is
always "where the file system is." If you can't get to a file system,
man for are fucked.
|
|
