WingNews logo WingNews GitHub [2]

w0000t's comments

w0000t | 10 years ago | on: How security flaws work: the buffer overflow

What!? Size of the array is always known to the programmer in C. In fact, if the programmer wants to get rid of that information, he/she must deliberately do so. Once one does that, the array becomes useless.

You also haven't explained how would that size information, which we already have, magically solve the problem.

w0000t | 10 years ago | on: Fix Windows 10

Just a note. The quote Eiriksmal posted is from the section: Why would I NOT want to use Arch?

w0000t | 10 years ago | on: Fix Windows 10

In my opinion, if those privacy issues bother you, the first step should be an overview of non-Microsoft operating systems.

w0000t | 10 years ago | on: C++ Hints

Yep, C doesn't define that uintptr_t can be modified and converted back to a pointer. It is only for storage.

w0000t | 10 years ago | on: Interview with Dennis Ritchie, Bjarne Stroustrup, and James Gosling (2000)

All ASCII characters are easily accessible. Your suggestion is a strawman, most coding is in plain text form and is typed.

I did a quick calculation a while back. I don't want to repeat it, since I lost the source, but the conclusion was that typing speed doesn't matter for programmers, since most of the time they actually think, not type. I.e. the bottleneck is information no the input of it.

w0000t | 10 years ago | on: The Manual One-Time Pad

And prevent learning?

No, what you need to do, is to learn whatever you enjoy, as much as you want in any direction, but recognize your limited knowledge in the field and act accordingly.

w0000t | 10 years ago | on: Cat purr generator

So the sound is completely artificial, constructed by you?

( It is very convincing. )

w0000t | 10 years ago | on: Where should the “6” key be?

Actually 'b' is at a completely wrong position( on a ordinary keyboard ). It is inaccessible for both hand, without moving your wrist which causes strain.

I have globally remapped 'b' to the right of 'l'. It feels much better. The old 'b' key is now unused.

w0000t | 10 years ago | on: Errors and Exceptions

Yes, I did. But so far I haven't been regularly checking printf return value. :-( I wonder if checking the result of every printf or asserting it, depending on the circumstances, would reduce the amount of time spent on writing+debugging the code on the long run.

w0000t | 10 years ago | on: Errors and Exceptions

That sort of thing is actually a completely valid approach.

You made a small mistake, since fprintf and printf call the same underlying code, the error handling should be either log the error in any way still available, and then depending on the design of the whole program, exit or continue. If printf fails you know exactly what is going on or have to exit. ( And printf would be wrapped in a function if you plan to use it repeatedly. )

w0000t | 10 years ago | on: Petition UK government to not ban encryption

That is not what OP is talking about. You cannot get different information out of the same chunk of encrypted data. That would basically make infinite compression.

What the methods you mentioned are doing, is hiding information in places which are marked as: random data no information here. But in reality there is information there. You then need to have dummy information somewhere else.

page 1
more