cautious_int
Joined 11 years ago
Karma
73
Submissions
47
Member since
Aug 2
Recent submissions
Comment · 11 years ago
Comment · 11 years ago
This is a lose-lose scenario. If you don't trust a closed operating system in the first place, why would you then, after performing these steps, trust the system that it really does what it says it does. The point is that you don't know, and you can never be sure. The solution is to either trust or not, switch or stay, there is no middle path, because any middle path implies some amount of non-trust.
Comment · 11 years ago
The Sun is the center of the Universe. Interesting.
Comment · 11 years ago
Transmission like this looks really good in a simulation, but I wonder how much lubrication would this require to operate in the real world.
Comment · 11 years ago
Mill processors? Aren't they still in research stage, only using emulation and no hardware.
Comment · 11 years ago
Why not put it into a Faraday cage?
Comment · 11 years ago
I was talking about the same line.
Apparently new is a "special" operator, or there is a bug in the compiler. I also can't get a warning with g++.
The problem seems to be that, as I said, [] takes any integer expression, it is there where the value gets truncated when operator sizeof or new is applied on it since they either return or take a size_t value.
Comment · 11 years ago
Because no truncation happens. In this case [] operator doesn't specify any type, only that the expression inside is an integer expression. While normally the type size_t is used for object and array sizes, [] takes any integer expression and the compiler won't complain.
Comment · 11 years ago
This is a common problem in C. Integer types are inherently type unsafe and are silently promoted with many different rules which are hard to remember and understand. As is seen in this case, even the ( borderline paranoid ) flag -Wconversion would not catch the bug.
I think this problem in C would be solved with a single flag: -Wwarn-if-using-integers-of-different-types-in-an-operation , forcing you to cast the integer if the types don't match in a arithmetic operation, or an assignment.
Comment · 11 years ago
Because unsigned overflow will not happen in C, and will instead wrap the value. The variables in question were unsigned.
This is defined and perfectly normal.
However signed integers will cause undefined behavior on overflow and there is a common flag in most compilers to trap on overflow.
Comment · 11 years ago
Can you also fake/spoof the appropriate signatures/headers? Otherwise separating that data is going to be very easy. Unless you do it on a higher level like emulating input, but then you won't have a very useful machine.
Comment · 11 years ago
Why?
Comment · 11 years ago
Windows 10 seems to transmit information to the server even when OneDrive is disabled and logins are using a local account that isn't connected to a Microsoft Account.
Well there you go. If you ever wondered whether this is happening only on the Microsoft Account(tm).
Don't put words in my mouth please.
I reject the thesis that trust is binary. Were I to accept it, I trust nobody - everyone is vulnerable to being subverted by blackmail, intimidation, making mistakes, etc.
You seem to be using a different definition of the word trust than I did. Everyone is vulnerable, does that mean you cannot trust anyone? No, you certainly can, that is the whole point of trust.