the screen was blue, internet explorer had died. blue screen of death. maybe the error wasn't as severe as when nt *really* blows up, but who cares, you pedantic faggot?
if you choose to 'show window contents when dragging' from display properties then this problem will go away. if that box isn't ticked then windows assumes you've got a low spec machine and doesn't waste the processor cycles drawing updates until you've moved the window.
I purchase Windows 2000 Server, Exchange Server, and the recommended hardware to run it on, and when it fails at half the advertised max load, Microsoft will gladly bill me for a support incident to tell me I need better hardware!
everybody lies with performance figures. you should be fired for not evaluating your purchases properly.
good windows admins are hard to find too. a windows admin job is easy to busk even when you don't know what your doing, hence all the mediocre fucktards flooding the market and giving windows admins in general a bad reputation.
wow. just press f8 within an allotted time window and you too can be as 1337 as me. all your fkeys are belong to us. you are on the way to destruction.
next time just spot the joke and save me the hassle of having to reply.
ERT Advisory CA-2002-01 Exploitation of Vulnerability in CDE Subprocess
Control Service
Original release date: January 14, 2002
Last revised: --
Source: CERT/CC
A complete revision history can be found at the end of this file.
Systems Affected
* Systems running CDE
Overview
The CERT/CC has received credible reports of scanning and exploitation
of Solaris systems running the CDE Subprocess Control Service buffer
overflow vulnerability identified in CA-2001-31 and discussed in
VU#172583.
Reports from places like cert and bugtraq show that there are just as many exploits out there for *nix based systems.
Network security of this nature is clearly not working when being applied at the OS or software levels, and a more flexible solution than the standard firewall is needed.
What would your opinion be of a 'mini-firewall' included as standard on all new network cards. The firewall would have packet filtering rules filtering out 'generic suspicious traffic' (such as bar an IP address for a day if something containing default.ida and a hell of a lot of 'N's comes through). The rules would be held on a flash ROM, which could be updated when necessary with software from a trusted source such as CERT and digitally signed by a non-trusted one such as Verisign.
Software could also be written to instruct the card to open certain ports and update the rules so that safe traffic for that software can pass through.
Unfortunately, the extra $20-30(?) would probably sink it dead in the water, not to mention the hassle of having to reprogram all network software to work with it. How does the idea stand in theory, though?
wut exactly. i completely fail to see how the lindows developers can fight any changes to the windows api. if they want to carry on with this project then they are forever doomed to play catch-up with microsoft deciding the rules.
Slashdot Mirror
> I hate page wideners! so do i, but that link is fucked.
STFW
no it fucking doesn't. it runs under its own account.
ok, i'll go back in my box now.
blue - it was blue, alright
screen - it was on a screen, too
of - reduntant
death - the error took out internet explorer. it died. dead. death
now grow up and stop playing the 'my bsod is more dead than yours' game. it's not funny, and it sure as hell ain't clever. you spastic.
the screen was blue, internet explorer had died. blue screen of death. maybe the error wasn't as severe as when nt *really* blows up, but who cares, you pedantic faggot?
cool. it kicks off a couple of bsod's and then returns you to the desktop with ie dead.
we've had that for years. it's called terminal services.
well, at the very least one of those goddamn monkeys would finally come up with the complete works of shakespeare.
i believe that if you hold down alt+f4 you can activate the 'infinite modpoints' cheat.
if you choose to 'show window contents when dragging' from display properties then this problem will go away. if that box isn't ticked then windows assumes you've got a low spec machine and doesn't waste the processor cycles drawing updates until you've moved the window.
maybe this could be the start of a beautiful friendship.
i can only assume that all the mirror sites have complied.
everybody lies with performance figures. you should be fired for not evaluating your purchases properly.
good windows admins are hard to find too. a windows admin job is easy to busk even when you don't know what your doing, hence all the mediocre fucktards flooding the market and giving windows admins in general a bad reputation.
update comments set karma=-1, reason="offtopic" where sid=26315
wow. just press f8 within an allotted time window and you too can be as 1337 as me. all your fkeys are belong to us. you are on the way to destruction. next time just spot the joke and save me the hassle of having to reply.
there's a page that mentions it here, but i'm still none the wiser ;)
press f8 while it's loading and choose 'command prompt only'.
no problem, i can't stand to see a troll in difficulty. that bit in simon the sorceror damn near broke my heart.
and in the very next issue of pc format it was reported that microsoft had given up on the idea...
i think your asp problems are probably due to the fact that intBrwID is treated as a local variable in the process sub.
Reports from places like cert and bugtraq show that there are just as many exploits out there for *nix based systems.
Network security of this nature is clearly not working when being applied at the OS or software levels, and a more flexible solution than the standard firewall is needed.
What would your opinion be of a 'mini-firewall' included as standard on all new network cards. The firewall would have packet filtering rules filtering out 'generic suspicious traffic' (such as bar an IP address for a day if something containing default.ida and a hell of a lot of 'N's comes through). The rules would be held on a flash ROM, which could be updated when necessary with software from a trusted source such as CERT and digitally signed by a non-trusted one such as Verisign.
Software could also be written to instruct the card to open certain ports and update the rules so that safe traffic for that software can pass through.
Unfortunately, the extra $20-30(?) would probably sink it dead in the water, not to mention the hassle of having to reprogram all network software to work with it. How does the idea stand in theory, though?
rather heavy? you weak fucking pussy!
wut exactly. i completely fail to see how the lindows developers can fight any changes to the windows api. if they want to carry on with this project then they are forever doomed to play catch-up with microsoft deciding the rules.