I used a female skin for Q3A and I definitely get focused on first in a room full of players. When I switched to the boring default it was markedly easier after spawning.
Holy shit. Jesus I got coffee everywhere you dumbfuck. haaahaha... multitasking is overrated, don't read at less than threshold: 2 and drink at the same time.
Read on. There is specific support for the NX flag on pages. If you boot with noexec=on, then stack/heap/data is automatically protected. If the page fault handler sees your thread because of an NX flag violation, the process is killed. Caveats: you can't mprotect it back to execute status, and it breaks some software, especially Mozilla/Java/Ada (just like exec-shield...)
I'm just lucky I never got a Stream call center...
on
Orwellian Tech Support
·
· Score: 1
because otherwise the endpoint of that 1-800 number would have been a smoking crater. I'd be a shame if I accidentally killed you; you seem nice enough.
I've never had any of these supposed problems when calling any computer manufacturer's tech support lines. Is it how I somehow command the attention of the phone monkeys on the other end? Do they somehow become knowledgable or magically able to forward me to tier 2 if it says "Ayanami" on the caller ID?
I highly suspect this is a bogus/fluff article: you know, an amaglamation of a bunch of interviews and war stories about the worst call center conditions imaginable.
NDIS is like iptables one step removed. It's a meta-networking stack. You can install filters into it, and they run with kernel privledges (IIRC).
ZoneAlarm, Personal Firewall, etc. are such filters. Windows ICF and the ICS product are such filters. Keep in mind that the "interface" you see is NOT the firewall itself, but like a configuration tool. The firewall itself is probably encapsulated as a service or driver.
BTW, the Microsoft built-in firewall for XP is just fine. It does exactly what most *nix users do with their firewalls, anyway. It doesn't let you classify packets by operating system type or anything (ala OpenBSD), but it fits the bill.
I tell people not to bother with ZoneAlarm, because although it can tell you when programs are trying to connect out, it doesn't PREVENT you from getting spyware or the like on your computer. It can tell you if you've got it, but by then it's too late.
And the really good viruses and spyware insert themselves directly into the NDIS stack to circumvent all of this.. predicated on a user running something dumb with Administrative rights.
That "gooey" python stuff only lives on the RedHat derived distros as far as I can tell, and it's never stopped me from using the tried and true methods either. I tend to ignore all of that stuff completely as it's superfluous. (I also tend to just not install any of it... the package selector is nice enough to keep them together)
Also, some of the scripts are damn useful. For example, the redhat-printer-conf. And I've looked at that baby, and it is some _hardcore_ python. It can handle like seven different printing systems, and detects which ones you have installed. It even comes with "Print Test Page".
Mint!
Actually, the worst offender is SuSE. YaST will completely take over all your configuration files. And YaST is written in C. OTH, YaST is pretty friggin complete, and it has a well documented plugin system so it's not as bad as it seems. Still, you just don't install it (or install it but don't use it). Problem solved.::shrugs::
Learn how to grok it. Also, there's WBEM (which are probes for SNMP) and the Performance Logging and Alerting stuff.
If your CPU usage spikes mysteriously, or some directory suddenly becomes shared, or a service dies, etc. etc. Windows comes with tools to let you know of this.
Not that I'm a big Windows fans or anything, but all the information is at your fingertips if you look around.
The same is true of Linux really... if you didn't know that/var/log contains a wealth of information that you should be looking at, how would you know where to look?
In my opinion, it's Solaris that sucks in the logging department. Not so much that it doesn't have the right capabilities, but that by default it logs close to nothing. This is very annoying.
by default... it's not so eager to proffer up these vulnerable services to the outside world in a default install because Apple _knows_ people who don't know any better want none of this!
Microsoft can't say the same, they have to turn on more remote access stuff to appease those corporate customers who hire a monkey to install it on a bunch of new equipment, and then they remotely tie them in and administer them.
Fortunately it's (MacOSX's) user-space is not targetted so much by online nogoodnicks, because it's no more secure than other Unixes by default... so clicking on a script you downloaded can still hose your home directory, etc.
Nothing can "fix" user stupidity. At least an platform gap seperates Apple users from stupid PC pwn4ge tricks.
Well that was hard. Obfuscated and no variables in the stacktrace, nor non-public function names.
The parent was implying that the deobfuscation is code de-tangling (trying to recreate essential branch control structures out of the purposefully complicated bytecode or object code). He wasn't implying you get variable names back or anything like that.
But I mean, do you have to know that:
int * unknown_function1(int param[], int param2[]) {
int * auto_int_p = malloc(12);
auto_int_p[0] = param[2]*param2[1] - param[1]*param2[2];
auto_int_p[1] = param[2]*param2[0] - param[0]*param2[2];
auto_int_p[2] = param[1]*param2[0] - param[0]*param2[1];
return auto_int_p; }
was originally was called cross_product? There are only so many ways to write certain things.
Even inside a firewall, that's just begging for someone to step in and install another distributed.net node to their team.
It's trivial to get a remote root shell with rexec if it's running out of inetd (which I'm sure it is in your case). It's not quite as trivial if your rhosts is set correctly, but it's really easy if you have access to a laptop and a network drop in the appropriate location.
Slashdot Mirror
What are you, living in the Stone Age!?!?!
I used a female skin for Q3A and I definitely get focused on first in a room full of players. When I switched to the boring default it was markedly easier after spawning.
Holy shit. Jesus I got coffee everywhere you dumbfuck.
haaahaha... multitasking is overrated, don't read at less than threshold: 2 and drink at the same time.
pWn4g3
Some days I pWn, other days I am pWn3d.
(I'd like to think I have more days of the former rather than the latter!)
Read on. There is specific support for the NX flag on pages. If you boot with noexec=on, then stack/heap/data is automatically protected. If the page fault handler sees your thread because of an NX flag violation, the process is killed.
Caveats: you can't mprotect it back to execute status, and it breaks some software, especially Mozilla/Java/Ada (just like exec-shield...)
because otherwise the endpoint of that 1-800 number would have been a smoking crater. I'd be a shame if I accidentally killed you; you seem nice enough.
I did that _on purpose_ and it took me awhile. Let me shake this idiot's hand!
It looks like somebody has a case of the Mondays.
I've never had any of these supposed problems when calling any computer manufacturer's tech support lines. Is it how I somehow command the attention of the phone monkeys on the other end? Do they somehow become knowledgable or magically able to forward me to tier 2 if it says "Ayanami" on the caller ID?
I highly suspect this is a bogus/fluff article: you know, an amaglamation of a bunch of interviews and war stories about the worst call center conditions imaginable.
salesca@aceonsource.com They really want to sell you computers
salesusa@aceonsource.com Even if you live in the United States and have bad credit
support@aceonsource.com So get in touch with the Support Hotline
hosting@aceonsource.com Free Webhosting
design@aceonsource.com Website Design for cheap
e-commerce@aceonsource.com and E-Commerce, shopping carts, merchant accounts
Oops, I forgot the spam armor. Ah well.
slashdotcomment8349878@nervalhi.net
NDIS is like iptables one step removed. It's a meta-networking stack. You can install filters into it, and they run with kernel privledges (IIRC).
ZoneAlarm, Personal Firewall, etc. are such filters. Windows ICF and the ICS product are such filters. Keep in mind that the "interface" you see is NOT the firewall itself, but like a configuration tool. The firewall itself is probably encapsulated as a service or driver.
BTW, the Microsoft built-in firewall for XP is just fine. It does exactly what most *nix users do with their firewalls, anyway. It doesn't let you classify packets by operating system type or anything (ala OpenBSD), but it fits the bill.
I tell people not to bother with ZoneAlarm, because although it can tell you when programs are trying to connect out, it doesn't PREVENT you from getting spyware or the like on your computer. It can tell you if you've got it, but by then it's too late.
And the really good viruses and spyware insert themselves directly into the NDIS stack to circumvent all of this.. predicated on a user running something dumb with Administrative rights.
Sigh.
That "gooey" python stuff only lives on the RedHat derived distros as far as I can tell, and it's never stopped me from using the tried and true methods either. I tend to ignore all of that stuff completely as it's superfluous. (I also tend to just not install any of it... the package selector is nice enough to keep them together)
::shrugs::
Also, some of the scripts are damn useful. For example, the redhat-printer-conf. And I've looked at that baby, and it is some _hardcore_ python. It can handle like seven different printing systems, and detects which ones you have installed. It even comes with "Print Test Page".
Mint!
Actually, the worst offender is SuSE. YaST will completely take over all your configuration files. And YaST is written in C. OTH, YaST is pretty friggin complete, and it has a well documented plugin system so it's not as bad as it seems. Still, you just don't install it (or install it but don't use it). Problem solved.
CIFS, NFS, these all have the same issues. Lots of RPC going on channeled through a single port... lots of security issues historically.
Only do it behind a firewall, that's for sure.
Learn how to grok it.
/var/log contains a wealth of information that you should be looking at, how would you know where to look?
Also, there's WBEM (which are probes for SNMP) and the Performance Logging and Alerting stuff.
If your CPU usage spikes mysteriously, or some directory suddenly becomes shared, or a service dies, etc. etc. Windows comes with tools to let you know of this.
Not that I'm a big Windows fans or anything, but all the information is at your fingertips if you look around.
The same is true of Linux really... if you didn't know that
In my opinion, it's Solaris that sucks in the logging department. Not so much that it doesn't have the right capabilities, but that by default it logs close to nothing. This is very annoying.
by default... it's not so eager to proffer up these vulnerable services to the outside world in a default install because Apple _knows_ people who don't know any better want none of this!
Microsoft can't say the same, they have to turn on more remote access stuff to appease those corporate customers who hire a monkey to install it on a bunch of new equipment, and then they remotely tie them in and administer them.
Fortunately it's (MacOSX's) user-space is not targetted so much by online nogoodnicks, because it's no more secure than other Unixes by default... so clicking on a script you downloaded can still hose your home directory, etc.
Nothing can "fix" user stupidity. At least an platform gap seperates Apple users from stupid PC pwn4ge tricks.
Save that manuvering for the logged in post. Sounds cool. But does it have "29 dimensions of compatibility"?
:p
Pay attention to me!!!!!!!!
::jumping::
I said I would reply to your last post, remember?
You are gay. Die.
This wasn't clear to me having read the reviews of Solaris 10 (which keep mentioning "Solaris Express").
.NETish marketing thing, where the moniker gets stuck on everything.
I thought it was some kinda
Well that was hard. Obfuscated and no variables in the stacktrace, nor non-public function names.
The parent was implying that the deobfuscation is code de-tangling (trying to recreate essential branch control structures out of the purposefully complicated bytecode or object code). He wasn't implying you get variable names back or anything like that.
But I mean, do you have to know that:
int * unknown_function1(int param[], int param2[]) {
int * auto_int_p = malloc(12);
auto_int_p[0] = param[2]*param2[1] - param[1]*param2[2];
auto_int_p[1] = param[2]*param2[0] - param[0]*param2[2];
auto_int_p[2] = param[1]*param2[0] - param[0]*param2[1];
return auto_int_p;
}
was originally was called cross_product? There are only so many ways to write certain things.
your company's non-free software on slashdot.
We have to deal with that in the articles, we don't need the sales pitch in the comments too.
Even inside a firewall, that's just begging for someone to step in and install another distributed.net node to their team.
It's trivial to get a remote root shell with rexec if it's running out of inetd (which I'm sure it is in your case). It's not quite as trivial if your rhosts is set correctly, but it's really easy if you have access to a laptop and a network drop in the appropriate location.
Really. It's like they wanted to get that "XP" sound in there. I'm calling it "10", or "gay" to anyone who insists on calling it "Express".
Christ. And what will they do when they get to SunOS 6.0?