Results 31 to 40 of 67

Thread: Let the finger pointing begin

Threaded View

  1. #13
    Senior Member gore's Avatar
    Join Date
    Oct 2002
    Location
    Michigan
    Posts
    7,177
    Tiger Shark is a guy who lives a few miles from me and used to hang with me here, and a certain hurricane hormones saw us playing one day on AO and took it as "me being arrogant" and for some reason he left. Then I saw the reason and realized it was hippo critical of him to "take his ball and go home" after the years of how much more mature he was then the rest of us.

    As for Reverse engineering a Windows box to make it do what Unix has done for 30 years.... Again, would you REALLY trust your life to a machine someone reverse engineered to get working?

    And MLF, STFU, I didn't say they caused an oil spill, and I've yet to see that hardware was the actual reason. So saying "Hardware is the only reason not Microsoft".... You're getting obnoxious, you're no better than I am except you're doing it for the start menu where I'm doing it for Unix. You're the same arrogant **** I am just on the other side.

    You know I see some cars have Windows installed... I wonder how long before the manual says "If your car crashes, hold the Car Door handle and pull three times and then grab the antennae to make it start up again". And how much longer it would take before people like you to not only accept this as normal, but defend it against all odds.

    What rating did NT Server get back then? Lol, without a network Cable making the server portion of it totally un-usable? Heh.

    Again, I'll ask again since for the third reply you've danced around the question:

    Everyone can feel free to answer but this is the third time I've asked this and been ignored:

    If you're life depended on a machine running and staying stable, would you REALLY trust Windows? If Windows was running a computer that your life depended on, would you REALLY trust it? Remember, if the screen turns blue, so do you.

    I can see if now "Windows has encountered an error" and "Illegal Operation" would take on new meaning. Lol.

    I'm waiting for a third time but it's OK, not once has someone ever answered yes, and you defending them can take a back seat until I hear your answer and why.



    EDIT:

    If this is a thread where you don't want someone talking about Windows and the possibility that all those blue screens we've seen over the last decade or two MIGHT be an issue, why did you post this in OSs? Windows is an OS, and this is the OS forum, so.... Where is the issue? Anyway, still waiting to see how much longer that question will be danced around. I'd LOVE to hear why if anyone answers yes. Unless of course they are named "Dr. Jack Kevorkian". Who also lives around here I might add.

    Instead of half assed reverse engineering feats that would probably end in disaster, I'd like to see THIS replicated in Windows:

    http://codeidol.com/unix/bsd/Securin...ip-the-Kernel/

    Also, I'm having trouble finding the exact thing I was looking for, but, here is how it works, since I know ONE person who can do it:

    You install Unix / Linux / BSD on a machine that is to be a highly secured Server. The machine can be a Web Server for the example:

    You open the source code for the Kernel, and basically remove EVERYTHING not required to make the hardware work, and some network, which is enough to run a Web Server.

    The Web Server itself is "hacked into the Kernel" so that it doesn't need anything else. The Kernel is the only thing actually running, no applications are installed, and the Kernel itself, drops ALL incoming packets that aren't basic port 80 Web Traffic, which basically ends up being the most secure OS and Server on the planet, and it does cost a lot to have done, but really, it's SERIOUSLY Locked. You can't get into it because there is nothing to get into. Even if they managed to find a Kernel exploit, or something similar, even THAT doesn't matter, because if it's not basic web traffic, the packets are dropped.

    There is NO machine I've EVER heard of, that has had this done, and had a break in of any kind. The machine literally can be ran for years without anything happening to it, because, as I said, with nothing but a Kernel, what is someone going to break into? They can't get root on the machine because there is no user shell to issue commands. There is no port listening to anything except 80, and if it's not normal web based traffic, it drops the packet anyway.

    The REASON this is not possible in Windows, is that you don't and won't, get sources for Windows where you can configure a custom Kernel, and then recompile it and install it, and it wouldn't work even then because you'd hav to write an interface for Windows without the GUI, which, too, takes resources no one needs on a headless server anyway.

    I'm really having trouble finding the exact info I needed, and so I can' give a direct link, and you can find tons of Kernel lock down info, but for some reason, THIS process is not there much. But anyway, the whole thing is bare bones. There is nothing to break into, there is no interpreter to execute commands remotely, and, basically, even if there was, they wouldn't get through the Kernel.

    That is why Unix is better than Windows. There's no Windows way of shutting off and recompiling everything, and Unix can. Like I said, even a Kernel exploit that gave the user exploiting ROOT, would do nothing, as there is no root, there are no users, nothing. The Kernel would drop the exploit before it hit the machine in the first place. That's as secure as I can think of.
    Last edited by gore; August 7th, 2010 at 12:04 AM.

Similar Threads

  1. how to finger a user via telnet
    By ai0070 in forum Miscellaneous Security Discussions
    Replies: 6
    Last Post: October 18th, 2004, 11:21 PM
  2. Finger Questions
    By JCHostingAdmin in forum AntiOnline's General Chit Chat
    Replies: 9
    Last Post: July 22nd, 2002, 06:03 PM
  3. Finger
    By Dr Toker in forum Newbie Security Questions
    Replies: 12
    Last Post: June 17th, 2002, 11:48 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •