qw3rty01

15 ms·

121.
by qw3rty01 6y ago
This seems to be a review of several different studies on analyzing brain activity and isn't just about the first study shown, so while the original title is a little sensationalist, I think the edited title is pretty accurate to what
122.
by qw3rty01 6y ago
Those ads support the people who created the videos; if you don't subscribe to ads "as a concept", then that's even more a reason to buy youtube premium--the content creators are losing out by your adblockers, not youtub
123.
by qw3rty01 6y ago
This just reads like a godot advertisement...it only has good things to say about godot and only bad things to say about any other library. It's really hard to take the article seriously with so much blatant bias. It also seems to lea
124.
Published Docker ports bypass input filter rules(github.com)
1 points by qw3rty01 6y ago|0 comments
125.
by qw3rty01 7y ago
.dev isn't an rfc2606 reserved TLD, so it shouldn't have been used for internal domains in the first place
126.
by qw3rty01 7y ago
This seems pretty low, can't we apply Bayes' theorem here? let F = transaction being fraud let D = detected as fraud P(F) = 492/284807 = .17% P(D|F) = 80% P(~F) = 1-P(F) = 99.83% P(D|~F) = 13% P(F|D) = (
127.
by qw3rty01 7y ago
I really wish this was included in the article, his conclusion makes a lot more sense in that context (though I still disagree with it).
128.
by qw3rty01 7y ago
Calling out an article for being misleading is not the same as misrepresenting it.
129.
by qw3rty01 7y ago
The article implied he wasn't the only one they talked with. There isn't anything he said that was explicitly incorrect (unlike some of the other unnamed security researchers), but he must not have much experience with credential
130.
by qw3rty01 7y ago
The Amazon spokesperson directly said it was credential stuffing--the article was trying to argue that it was more than that in an extremely misleading way.
131.
by qw3rty01 7y ago
All of that information is extremely common when it comes to aggregated information sold/shared for credential stuffing, there's nothing that sticks out as odd or out of place in any of this. It can all be pulled through scripts,
132.
by qw3rty01 7y ago
After reading the article, it's pretty clear that it was credential stuffing and that the writer didn't take the time to understand how it worked. Not sure what security experts they talked to, but credential stuffing absolutely c
133.
by qw3rty01 7y ago
Even if it was the official article title, "Data Leak" is extremely misleading; the attack is called credential stuffing and is unrelated to any sort of breach on Ring's end. Edit: finished reading the article, and the entire
134.
by qw3rty01 7y ago
You're saying we shouldn't spend time to make sure the algorithm is mathematically sound...because the implementation will have side channels? Using your metaphor, that's like saying we should never bother designing a secure
135.
by qw3rty01 7y ago
That's because...they can. Because the behavior of the statement is undefined.
136.
by qw3rty01 7y ago
It says everything. Even if undefined behavior works one way on all platforms today, it could work differently tomorrow in a way that introduces bugs. It's nonsensical to blame the compiler for conforming to the standard in a way that
137.
by qw3rty01 7y ago
There is no guarantee it would work if it relies on undefined behavior--that's what undefined means, and also the reason the optimizer acted the way it did. In that case, adding flags that defines what happens when particular undefined
138.
by qw3rty01 7y ago
A better title would be security flaws caused by relying on undefined behavior.