DCKing

111 ms·

871.
by DCKing 12y ago
> yes and no. Standard white paper Diffie-Hellman yes. But implementations can fix that. As you point out. Well, there we have it. I happen to have worked on a project where plain Diffie-Hellman was used not long ago. The active attacke
872.
by DCKing 12y ago
The weakness of JS Crypto is that you cannot authenticate the source of your crypto library so you cannot make sure it works properly. The problems are equivalent. All your ranting against what I'm saying is also directly applicable to
873.
by DCKing 12y ago
1. The weakness of plain Diffie-Hellman is that the data you receive (the other part of the key exchange) can be from someone you can't trust. You shouldn't use plain Diffie-Hellman if your attack model includes active attackers o
874.
by DCKing 12y ago
Sure, TLS probably covers many use cases. But if protection against overzealous public Wifi spots is your goal, or uploading encrypted files to something like Mega over HTTP, there are still uses that TLS cannot cover. Again, I am not adv
875.
by DCKing 12y ago
Diffie-Hellman also isn't secure against determined and active attackers (with power on the network). What you say about cryptology is utter nonsense. > Your goal isn't crypto, but stopping casual and passive eavesdroppers. So
876.
by DCKing 12y ago
JavaScript crypto is simply not a protection against that attack model. It is protection against the attack model of the passive eavesdropper. That's all I'm saying. I completely agree with what you say. Whether you view that at
877.
by DCKing 12y ago
All attacks against JS crypto addressed assume a somewhat determined and active attacker. Although this is definitely the big problem to be concerned about, that does not mean that there is no place for JavaScript cryptography as protecti
878.
by DCKing 12y ago
> @acqq Don't hang me up on a figure of speech. It's frustratingly rude. I do understand how memory management relates to fluid applications. I don't understand how that point relates to Swift's innovativity, and you
879.
by DCKing 12y ago
You're showing some incredible arrogance here by not addressing my other points. You fail to address the point how specifically the Swift language (not the Swift runtime ) is so innovative that it enables fast apps on resource constra
880.
by DCKing 12y ago
How is memory usage relevant to creating fluid/responsive applications? How is JavaScript DOM management even comparable to native UIs where the UI thread runs with realtime priority in native unmanaged code? And when did we stop talki
881.
by DCKing 12y ago
You're talking incredible nonsense. I can create fast non-stuttering GUI applications on phones with minimal resources (talking <$100 phones here) using F#. F# is far more feature rich than Swift is or ever will be. I have been able
882.
by DCKing 12y ago
It is somewhat unfair to dismiss Rust as an unfinished beta in comments on an article that demonstrates how the Swift compiler isn't even up to beta standards. Swift is a nice language for sure. It picks up nicest features of many ot
883.
by DCKing 12y ago
It appears the compiler optimizes out bounds checking if and only if it can tell during compile time that the index is correct [1]. Arrays of dynamic size or with dynamic references are bound checked. In dynamic cases you should be writing
884.
by DCKing 12y ago
I've never said that freedom is about consistency. Opinions should be consistent if they are to be taken seriously. This guy wants to intentionally leave software exploitable, ready to be unknowingly hacked by criminals or government
885.
by DCKing 12y ago
Rust has memory safety by default. However , it can do memory unsafe things in special blocks[1]. So it can do everything low level that C can, including controlling memory hardware [2]. It does unsafe things only in special blocks that
886.
by DCKing 12y ago
So what do you think about the NSA's capabilities to easily rootkit your "free" exploitable device? I don't think this is a consistent worldview.
887.
by DCKing 12y ago
I'm baffled by that opinion. The fact that memory-unsafe software keeps on being produced in C/C++ is a good thing? The capabilities of criminals to run local (or remote!) root exploits on many devices is offset by the fact that
888.
by DCKing 12y ago
I think the reason many people are rooting for Rust is because it's got comprehensively better features than competing languages. I'm not talking just about memory safety, but also its adoption of functional language features. I
889.
by DCKing 12y ago
D is absolutely a viable alternative to C++ and probably C. There's no argument there. D is not a viable threat to C/C++ (this is what I said!), as noone is really thinking that D will actively displace the use of C/C++ in
890.
by DCKing 12y ago
Yes, it's far too early to tell. The good thing to take away is that, at the moment, the answer to "is Rust a viable threat to C/C++?" does not seem to be a categorical no. The same cannot be said for other languages i
891.
by DCKing 12y ago
I was already secretly imagining a future where Rust will completely replace C as the low level language for everything. Even the Linux kernel rewritten in it eventually. It'd be a much better world with no #ifdefs, strong type safety
892.
by DCKing 12y ago
What do you mean by "compatible with the JVM"? Android is compatible with the JVM. Android's dx tool converts the JVM bytecode in your JAR files to Dalvik/ART compatible DEX files. You probably mean that is not compati
893.
by DCKing 12y ago
Please don't get angry with other people for your own failures in comprehension. Come on.
894.
by DCKing 12y ago
You only need to register "in" one of these countries. Spotify works everywhere with an internet connection after that.
895.
by DCKing 12y ago
My argument was also about familiarity. The imperative subset of Scala is really familiar to Swift, you're absolutely right (+1 for posting that comparison). However, real-world Scala is different. With powerful trait-based OO programm
896.
by DCKing 12y ago
Java's problem on Android is that your code quickly fills up with annotations and inner callback classes. Java 8's first class functions should be a big improvement, but you're still left with a lot of terseness, still so-so
897.
by DCKing 12y ago
Although I love Scala, I don't think it will work as a primary language for an app platform such as Android. Idiomatic Scala is just too alien for most people to comprehend quickly. The beauty of both Swift and Dart is that they are
898.
It's time: bring Dart to Android(grobmeier.de)
33 points by DCKing 12y ago|84 comments
899.
by DCKing 12y ago
Ugh, the 'NSA sysadmin'. Snowden himself addressed this point that this is a framing move on the part of the US government to downplay his knowledge of what the NSA was really up to. He actually did participate in spying activitie
900.
by DCKing 12y ago
Forgive me for asking (not usually a programmer of anything that goes directly to machine code), but is single step debugging as relevant for a language such as Go which has far fewer ambiguities and undefined behaviour? Isn't single s

More ›