So capture the network traffic being sent to Napster and send it from gnapster. Classic replay attack. If worst comes to worst, you can extract the key from the client --- after all, if it encrypts something, it needs to have something to encrypt it with.
Encryption is *not* a pancea, it does not magically make everything unbreakable. Like any other tool, it is useful in places, but it's just that, a tool. It has limitations. Encryption does not allow you to trust the client --- *NOTHING* does.
Actually, while the largest satellite operator worldwide is indeed located in Europe, ground stations are spread around the world. And, strangely enough, most signal losses are actually not due to atmospheric conditions, but rather to the fact that the average Microsoft PC cannot keep up with the high transfer rates from satellite, and so has to occasionnally drop a packet or two!
This is utter bullshit. Even a modest computer (like a 486 or slow Pentium) can completely saturate a 10mbit connection, and satellite ISPs are *not* that fast. An "Average" PC these days, with a PCI network card and decent processor, can *easily* handle 100mbit of bandwidth.
I've seen many types of bugs in my own code. Some of them include:
Stupidly using variable++ instead of ++variable in array references, or vice versa.
Decreasing the reference count of an object temporarily, then increasing it again after performing some action. Usually when I'm "pretty sure" that it will have a reference count of >1, it's annoying to see it segfault when it tries to increase the reference count back to 1.
Ignoring structure padding
Off-by-one (fencepost) errors with sizes of dynamically allocated memory locations
A variaty of strlen()+malloc() problems, e.g., where I meant malloc(strlen(foo)+1), I could use
malloc(strlen(foo+1));/* Two short, and a segfault if strlen() == 0 */
malloc(strlen(foo));/* Usually due to sleep deprivation */
malloc(strlen(foo)-1);/* It actually happened once */
I think off-by-one errors are the second main source of C program bugs. They can occur in programs which use no dynamic memory allocation at all, and are extremely difficult to detect. ALL HAIL ELECTRICFENCE!
Another common problem is using something like this:
if(foo) {
do_something();
do_something2();
}
else
do_elsething();
do_elsething2();/* Added later, not realizing that more braces are needed */
Of course, an editor with automatic, syntax-based indentation will help with the above problem and ones like it.
Macros that evaluate their arguments twice are also prime suspects. Imagine something like this, where trace evaluates its argument twice.
Starting Emacs for every document is like starting apache anew for each web page view. A far better way is to use gnuclient or gnudoit to open a file in a new window instead --- treat it more as a daemon and less like vi, and you'll be much happier.
Bleh. It's easy --- I have junkbuster set up at home. All I need to do is to use that proxy and voila, no more blocking! Apparently, my school only cares about port 80 --- I was half expecting Bess to filter the standard HTTP proxy ports as well, but, to my delight, it did not.
Problem is that I had to use some social engineering with the network administrator to disable the security on a computer --- damnedable fortress program. I'm a programmer, dammit, not a h4x0r.
Get a bunch of lawyers together and write nasty letters. You can't actually sue them, unfortunately, since, IIRC (and IANAL), a lawsuit must be brought by an "interested party," i.e., ID. The players of the game might qualify, though --- I don't know.
It's not a problem --- All you'd need to do is to use one of the better GTK+ Aqua themes. Same situation on windows, where default GTK looks nothing like default Windows.
No. Use an environment variable. Environment variable names arn't nearly as constrained as switches, and it would be easy to find one that isn't used already.
Not to mention that you only need to set env variables once, whereas you'd need to specify the switch every time.
Again, that's like saying anything compiled with gcc is a derived work of gcc. Merely using something does to create something else does not create a derived work, no more than a house is a derived work of a hammer!
Think about it --- it *is* an 8-bit grayscale, with predefined gray levels. Each character is a different number of lit pixels, and, when used *as* pixels, can be used to simulate gray levels. That's why advanced (i.e., non-linedrawing) ascii art works.
Re:Looks a little fishy...
on
The ASCII Cam
·
· Score: 1
Slashdot Mirror
So capture the network traffic being sent to Napster and send it from gnapster. Classic replay attack. If worst comes to worst, you can extract the key from the client --- after all, if it encrypts something, it needs to have something to encrypt it with.
Encryption is *not* a pancea, it does not magically make everything unbreakable. Like any other tool, it is useful in places, but it's just that, a tool. It has limitations. Encryption does not allow you to trust the client --- *NOTHING* does.
Patch for GNapster:
-send_to_server("type=gnapster");
+send_to_server("type=BigBronapster");
I've seen many types of bugs in my own code. Some of them include:
/* Two short, and a segfault if strlen() == 0 */
/* Usually due to sleep deprivation */
/* It actually happened once */
/* Added later, not realizing that more braces are needed */
Stupidly using variable++ instead of ++variable in array references, or vice versa.
Decreasing the reference count of an object temporarily, then increasing it again after performing some action. Usually when I'm "pretty sure" that it will have a reference count of >1, it's annoying to see it segfault when it tries to increase the reference count back to 1.
Ignoring structure padding
Off-by-one (fencepost) errors with sizes of dynamically allocated memory locations
A variaty of strlen()+malloc() problems, e.g., where I meant malloc(strlen(foo)+1), I could use
malloc(strlen(foo+1));
malloc(strlen(foo));
malloc(strlen(foo)-1);
I think off-by-one errors are the second main source of C program bugs. They can occur in programs which use no dynamic memory allocation at all, and are extremely difficult to detect. ALL HAIL ELECTRICFENCE!
Another common problem is using something like this:
if(foo) {
do_something();
do_something2();
}
else
do_elsething();
do_elsething2();
Of course, an editor with automatic, syntax-based indentation will help with the above problem and ones like it.
Macros that evaluate their arguments twice are also prime suspects. Imagine something like this, where trace evaluates its argument twice.
trace("unref return val: %d", object_unref(object));
Oops, you just destroyed your object if it had a reference count of 2.
Starting Emacs for every document is like starting apache anew for each web page view. A far better way is to use gnuclient or gnudoit to open a file in a new window instead --- treat it more as a daemon and less like vi, and you'll be much happier.
Bleh. It's easy --- I have junkbuster set up at home. All I need to do is to use that proxy and voila, no more blocking! Apparently, my school only cares about port 80 --- I was half expecting Bess to filter the standard HTTP proxy ports as well, but, to my delight, it did not.
Problem is that I had to use some social engineering with the network administrator to disable the security on a computer --- damnedable fortress program. I'm a programmer, dammit, not a h4x0r.
Get a bunch of lawyers together and write nasty letters. You can't actually sue them, unfortunately, since, IIRC (and IANAL), a lawsuit must be brought by an "interested party," i.e., ID. The players of the game might qualify, though --- I don't know.
No free unix can be a unix as far as The Open Group is concerned, since they must include CDE, and CDE is commercial software.
One word: Trojan
Yes, dammit. Why the hell can't people get it right and realize that the object must be *singular* for it to work?
Besides, your information is old.
glibc version problems are of far, far less importance than windows DLL problems.
Besides, recent glibc versions are supposed to be binary-compatible with older 2.x ones, no?
Threads on Linux are just fine. Did you actually use a pthreads library based on clone, or did you use one of the crappy userspace thread libraries?
Also, which "open standards" do "Real Unix" operating systems support that Linux does not?
What makes something a "real unix" anyway? Costing money? Is BSD Unix?
It's not a problem --- All you'd need to do is to use one of the better GTK+ Aqua themes. Same situation on windows, where default GTK looks nothing like default Windows.
Static arrays in general suck and are bug-ridden anyway. Most programs just use chunks of dynamically-allocated (malloc or alloca) anyway.
And it would use file descriptor 3, right? You can't do that --- it's already used by other programs.
No. Use an environment variable. Environment variable names arn't nearly as constrained as switches, and it would be easy to find one that isn't used already.
Not to mention that you only need to set env variables once, whereas you'd need to specify the switch every time.
wvware (AFAIK) isn't by Microsoft, and the docs for the word format were 1) Incomplete and 2) Pulled from MSDN soon after they were put up
Again, that's like saying anything compiled with gcc is a derived work of gcc. Merely using something does to create something else does not create a derived work, no more than a house is a derived work of a hammer!
How, exactly, does one remove, use, and then insert a cd into a package without opening it? That would be a nice trick.
Bullshit. Royalties are given for using copyrighted works --- if the work is entirely your own, no royalties are needed.
That would like be like a paper company demanding payment for a book printed on its paper (in addition to the cost of the paper itself)
Please. It's not MSCE bashing, it's high-school-student bashing.
Think about it --- it *is* an 8-bit grayscale, with predefined gray levels. Each character is a different number of lit pixels, and, when used *as* pixels, can be used to simulate gray levels. That's why advanced (i.e., non-linedrawing) ascii art works.
Which characters specifically?
All continents are islands.