Slashdot Mirror

From: ianb@ocf.berkeley.edu (Ian Barkley)
Subject:Compiler says 'Ack'
Date: 23 Feb 92 09:30:04 GMT

ABSOLUTELY UNCHANGED COMPILER RESPONSES
(from a make of umoria 5.4 on an Apollo...)

[monsoon:umoria] 19} make
cc -O -c main.c
Compiler Errors
99 divide by 0 error: can't find source
033 linker attempting to 'duck tape' this 'gerbil' of a program ...

more

Wasn't one or more of the head Engineers of VMS responsible for the mess that is Windows NT/2000?

Maybe there could be a UNI course OS101 how to turn a secure OS into a virus infested shatered mess. Bill can hand out the degrees

have you ever tasted a mouthful of your own semen?

it's not so bad really. if i were a girl i imagine i'd suck lots of dick.

since this is my last post for the day, i figure i'll give a shoutout to neko, for pointing me to exploit code which affected my NetBSD machine until about an hour ago.

oh yeah, haters can orally coax the feces from my leather donut and manually separate the bacteria into alphabetical order.

A small correction, the sniffer tools name is Ettercap, more info about Ettercap can be found on Packet Storm security

Dang it, I was all set to moderate, but this needs a followup instead since Dimwit left something out. Namely that those set commands belong in /etc/system.

And a second followup that the whole thing is moot since that "fix" has been hacked.

as it has already been cracked

Well, I'd say so. 30 seconds of searching on google revealed the exploit with a really good explanation of the problem and solutions to protect yourself. As well as an OpenSSH exploit.

From the file:
HOW TO PROTECT: There are a few ways. If you have a statically linked login, then you are safe. setuid programs ignore LD_PRELOAD so one you have logged in, you cannot subvert the system.

You can patch telnetd to wipe all but a few env variables. There are many widely pieces of available code to demonstrate this.

From information available PPPoE, even though wrapped, is still has a smaller header size than DOCSIS. PPPoE has a header of 24 bytes and a payload of between 0-1492 bytes, while DOCSIS has a header of 31 bytes at minimum ( with a max of 266 bytes ) and a packet size 0-1500 bytes. Which if taken to maximum with maximum packets sizes all the time is 98.4% for PPPoE and between 98.0% and 84.9% percent depending on the header size. (As packet sizes decrease the difference between the two systems INCREASE). This means even with PPPoE DSL lines you are using more bps for real data than on a DOCSIS cable modem system. Of course this analysis assumes that error rates are non-existant for both and that traffic comming from both nodes is at the same level. (The traffic levels is a safe assumption in this case, but error rates of DSL would probably be less than DOCSIS since it's collisions do no occur within the system, but at the head node. DOCSIS occurs at transmission because of contention on the line.) You webserver and mail will probably not perform as well if they were using the full line speed of the cable modem, but this is due to limitations on the upstream speed and not the frame size or frame overhead. If the server isn't being constantly slammed there will be little to no difference. But since you can never tell until you run the system you're millage may vary.

Info about: PPPoE DOCSIS

... and here is a tripwire replacement which looks and feels like tripwire, but never actually gets tripped. Do you believe the FBI isn't clever enough to come up with something like that ?